OK, I found the problem with running the controller on Android-2.1, and updated the code in the android-multitouch-controller project linked above. If somebody could please test on 2.1 and/or 2.0.x I would greatly appreciate it, I only have an Android-2.2 device. Thanks!
On Jun 9, 7:47 am, luke <[email protected]> wrote: > OK, the first review of MultiTouch Visualizer 2 on the Market says > that the app only shows one touch point on the HTC Incredible. It > works fine on the Nexus One. Can anybody please test this on an > Incredible for me, or even better, can anyone with an Incredible > please put a few Log.i() statements in the code and see how the second > touch point is getting lost on the Incredible? The code for the > visualizer (and the controller, you'll need both) is here: > > http://code.google.com/p/android-multitouch-vizualizerhttp://code.google.com/p/android-multitouch-controller > > There's really no reason this should work on the Nexus One and not at > all on the Incredible. > > On Jun 9, 7:11 am, luke <[email protected]> wrote: > > > > > I should add that I uploaded a significantly updated "MultiTouch > > Visualizer 2" to the Market that uses this controller. It now > > supports 3+ touch points, and numbers all the touch points according > > to their pointer indices. It also shows the diagonal pinch diameter > > so that you can see how the pinch diameter doesn't get affected much > > when dual-touch operations snap together in X or Y on Synaptics > > devices like the G1 or the Nexus One. > > > I hear the EVO 4G can support some large number of touch points, can > > somebody please test this? > > > (...I had to change the package name of MultiTouch Visualizer, because > > I managed to lose the keystore password, so the old version is not > > there anymore and version 2 is a separate download :-) ...) > > > On Jun 9, 7:00 am, luke <[email protected]> wrote: > > > > If anybody is creating multi-touch apps for Android, you may have > > > noticed the MotionEvent class is getting more and more complicated > > > over time. Additionally you may have discovered your code has > > > different quirky behavior on different devices (e.g. on Synaptics > > > devices, touch-down / touch-up can cause sudden jumps in pointer > > > position before the down/up event is received). > > > > I have written a class to simplify the process of writing multi-touch > > > applications for Android, and just updated it to Android 2.2 (and to > > > handle 3+ touch points on true 2D multi-touch sensors, as present on > > > the HTC Incredible and HTC EVO 4G), and moved the project to Google > > > Code hosting: > > > >http://code.google.com/p/android-multitouch-controller/ > > > > There are numerous advantages to using this controller over trying to > > > reinvent the wheel yourself, including simplicity and automatic device- > > > space / object-space coordinate conversion for pinch-zoom. This also > > > correctly centers the zoom of a pinch operation on the center of the > > > pinch rather than the center of the screen, and supports simultaneous > > > pinch-and-drag for more realistic pinching :-) -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
