BbiKkuMi / adosbox

Automatically exported from code.google.com/p/adosbox
0 stars 0 forks source link

multitouch version incorrect and please upload last version build. #22

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. I have xt720(motoroi, proyo version and 854x480 display) and aDosBox 
multitouch version.
execute is successed. but mouse touch is only correct in horizontal area.

-------------------------------------------------------------
-   can"t touch this row area                     -
-            can                                          -
-            touch                                         -
-            this                                           -
-            area                                          -
-   can"t touch this row area                     -
-------------------------------------------------------------

2. display touch is only mouse move. not click
if want mouse touch. i always move one display touch with another multitouch.
that is very hard thing.

3. please build and upload WVGA last version please : )

What is the expected output? What do you see instead?
1. can touch any location excetly.

2. display touch == mouse click that point
   display long touch == mouse right click that point
   display touch move == mouse move

What version of the product are you using? On what operating system?
aDosBox_mulittouch_patched.apk. don't know version number.

Please provide any additional information below.

sorry. i can not write english well.:)

Original issue reported on code.google.com by rustfaith@gmail.com on 30 Dec 2010 at 2:10

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
or please. let me know. how can make last source version build for WVGA.

i download all source and build in eclipse with android.
but result apk file (4MB) can not install in device.

Original comment by rustfaith@gmail.com on 30 Dec 2010 at 2:14

GoogleCodeExporter commented 9 years ago
These bugs are related to v0.1beta and no longer valid

Original comment by grea...@gmail.com on 24 Apr 2011 at 7:27