It's not so much an issue of gestures that may be impossible to recognize on certain screens but more that the API exposes functionality that is broken on all screens at the moment. Especially the coordinate flipping/confusion is something that can't be solved according to Dianne. And it is exactly this functionality (just tracking two fingers that are not close to each other on the screen) that is needed by us game developers to create more elaborate input schemes. It's kind of sad really :/
On 15 Feb., 10:22, Sean Hodges <[email protected]> wrote: > The Nexus One uses the Synaptics ClearPad 2000 > series:http://www.synaptics.com/about/press/press-releases/synaptics-clearpa... > > According to this > reference:http://www.synaptics.com/solutions/products/clearpad#benefits-2000 > this model has support for a maximum of 2 simultaneous touches, the > 3000 series supports up to 10. The Synaptics site also describes some > of the gestures that are possible with its > products:http://www.synaptics.com/solutions/technology/gestures/touchpad. > > The touchscreen technology is very diverse across handsets, some of > the more complex gestures are going to be limited or impossible on > certain devices (e.g. ones that have obtrusive dead-zones or > singletouchonly). For this reason, I don't believe the interface can be > normalised to be compatible with all devices, primarily because you > will cripple the devices with the superior functionality (we'd > losemulti-touchfor a start, to support handsets like the HTC Magic / > Dream). I think you just have to be conservative about the complexity > of the gestures you require in your app, and provide alternative > methods of control for the devices that can't support those gestures. > The Dolphin Browser is a good example of this in action. > > On Sun, Feb 14, 2010 at 7:14 PM, Dianne Hackborn <[email protected]> wrote: > > G1, myTouch, and Passion use a Synaptics screen. Droid uses one from > > another company (I can't recall). > > Even for a particular company, there are a wide variety of screens you will > > encounter. For example here is what I found for Synaptics: > >http://www.synaptics.com/solutions/products/clearpad > > > On Sat, Feb 13, 2010 at 9:11 PM, Kevin Duffey <[email protected]> wrote: > > >> So are they all using the same company for the screen? > > >> On Sat, Feb 13, 2010 at 5:10 PM, Lance Nanek <[email protected]> wrote: > > >>> A more capable multitouch screen probably costs more. If that is the > >>> case, it isn't really surprising that multiple manufacturers would go > >>> with a cheaper, less capable one. > > >>> On Feb 13, 6:51 pm, Kevin Duffey <[email protected]> wrote: > >>> > So Robert.. is this a platform issue in your mind.. being that it > >>> > happens on > >>> > all android devices currently regardless of manufacturer? Or is it a > >>> > driver > >>> > issue for each hand set and just oddly happens to be coincidental that > >>> > various manufacturers have the exact same issue withmulti-touch? I am > >>> > sure > >>> > what Diane says is accurate... but yet it seems odd that different > >>> > manufacturers have the same problem. > > >>> > On a slightly different note.. what is the stance of the Android > >>> > platform > >>> > team as a whole towards game developers? By this I mean, if this is > >>> > indeed > >>> > an issue on different manufacturer's handsets.. is it important enough > >>> > that > >>> > game developers, which for sure will be a large segment of popularity > >>> > for > >>> > android as it is on iPhone.. can get this escalated enough to get some > >>> > platform/driver developers looking into it and if possible, tap the > >>> > community (such as Robert) to help, so we can figure out exactly what > >>> > is > >>> > going on? It just seems too crucial of an issue to overlook being that > >>> > it > >>> > directly makes it impossible as of now for game developers to really > >>> > utilize > >>> >multitouch. > > >>> > Robert (et all)... an app I want to eventually get around doing is a > >>> > drum > >>> > machine app.. with multiple drum pads. On the iPhone, an app called > >>> > BeatMaker allows for 5 pads at once to be touched. Would this issue > >>> > possibly > >>> > make an app like this not work? I don't even know if Android can handle > >>> > more > >>> > than two touches at once.. but there are plenty of apps out there that > >>> > will > >>> > use more than two simultaneous touches at once. > > >>> > On Fri, Feb 12, 2010 at 4:20 PM, Robert Green <[email protected]> > >>> > wrote: > >>> > > Ok if you guys want to see what I'm talking about, check out the app > >>> > > I > >>> > > just published called "Multitouch Visible Test." Play around with > >>> > > that and you'll see the problems. If you're interested in developing > >>> > > a > >>> > > multitouch app, check that out first so that you know the limitations > >>> > > of the data you'll be working with. > > >>> > > On Feb 12, 4:55 pm, Robert Green <[email protected]> wrote: > >>> > > > Luke's code cleans up some basic stuff like gestures involving > >>> > > > pinching but it can not fix the two independent point problem. > >>> > > > Currently, even with his code which filters out some noise, it is > >>> > > > impossible to have a reliable control system involving two > >>> > > > independent > >>> > > > virtual joysticks placed along the same axis. So many iPhone games > >>> > > > have that and I was actually planning it for my new release but > >>> > > > unfortunately it will not work. I'm talking about the controls > >>> > > > where > >>> > > > you've got a touchable joystick on the bottom left and another one > >>> > > > on > >>> > > > the bottom right. It's very common but currently impossible on > >>> > > > Android because of the hardware (though I'd really like to see some > >>> > > > raw data because looking through the core service classes, there is > >>> > > > a > >>> > > > LOT of difficult-to-read code that seems to hack up the values > >>> > > > quite a > >>> > > > bit). > > >>> > > > I'll wrote a littlemultitouchvisualizer kind of like Luke's but > >>> > > > aimed more at showing what you can and can't do with a game control > >>> > > > system. I'll post the APK so everyone can see what I'm talking > >>> > > > about. > > >>> > > > Multitouchdefinitely works better on the Droid than on the HTC > >>> > > > screens but I saw many similar issues involving interactions > >>> > > > between > >>> > > > the two touched spots. It doesn't seem to flip axis as much as the > >>> > > > HTC screens, though. > > >>> > > > This really is unfortunate for the platform as a whole that the > >>> > > > screens are so weak with this feature. I guess us game guys will > >>> > > > just > >>> > > > have to get a little more creative with our designs. > > >>> > > > On Feb 12, 2:30 pm, Kevin Duffey <[email protected]> wrote: > > >>> > > > > Ok.. thanks for the pointer Sean. So question for you and > >>> > > > > Dianne.. > >>> > > being on > >>> > > > > the platform team.. if his code works so well.. supposedly better > >>> > > > > than > >>> > > the > >>> > > > > OTA updates for Nexus.. why not just replace what is in Android.. > >>> > > > > or > >>> > > add it > >>> > > > > some how so that all of us developers can have this corrected > >>> > > > > data? > >>> > > Maybe I > >>> > > > > read incorrectly, but from what you and Dianne are saying, the > >>> > > > > issues > >>> > > the > >>> > > > > rest of the guys talk about.. where by touching one place, then a > >>> > > > > 2nd.. > >>> > > then > >>> > > > > lifting one finger, thentouchagain and the wrong data being > >>> > > > > sent.. > >>> > > this > >>> > > > > has to do with the massive events being sent and the confusion > >>> > > > > lies in > >>> > > that > >>> > > > > the MotionEvent is reporting incorrect data..but somewhere in > >>> > > > > there is > >>> > > the > >>> > > > > correct data.. and from what it looks like, Lukehutch's code > >>> > > > > resolves > >>> > > that > >>> > > > > issue? > > >>> > > > > If that is correct, great.. maybe Robert Green and others can > >>> > > > > take that > >>> > > > > class of his and retrofit it and report back on this thread if it > >>> > > works. But > >>> > > > > if so, why not put that into the core of the framework for all to > >>> > > benefit? > >>> > > > > Clearly this has been a problem for the likes of Robert and > >>> > > > > others who > >>> > > have > >>> > > > > done great work with game development and are complaining that > >>> > > > > it's > >>> > > ruining > >>> > > > > the ability to develop comparable (at least inmulti-touch) games > >>> > > > > as > >>> > > > > iPhone.. so why not provide the corrected data within Android > >>> > > > > itself? > >>> > > Or.. > >>> > > > > why not require that alltouchmanufacturers.. devices.. report > >>> > > > > the > >>> > > right > >>> > > > > data in some specific way such that the framework provides > >>> > > > > accurate > >>> > > > >multi-touchcompletely? This really seems to be more complex than > >>> > > > > it > >>> > > should > >>> > > > > be for us developers wanting to utilizemulti-touch. > > >>> > > > > On Fri, Feb 12, 2010 at 11:42 AM, Dianne Hackborn > >>> > > > > <[email protected] > >>> > > >wrote: > > >>> > > > > > Sorry I meant exactly what I said: this is how thetouchscreen > >>> > > hardware on > >>> > > > > > the Nexus One works (which is essentially the same screen as on > >>> > > > > > the > >>> > > G1 and > >>> > > > > > myTouch). The Droid has a sensor from a different > >>> > > > > > manufacturer, with > >>> > > > > > different behavior. Other phones will likewise have different > >>> > > sensors. > > >>> > > > > > This has nothing to do with the Android platform. Please do > >>> > > > > > not file > >>> > > bugs > >>> > > > > > about it. Android is just reporting what the hardware is > >>> > > > > > capable of > >>> > > > > > reporting. There is no "normalization" for games or such, > >>> > > > > > there is > >>> > > just the > >>> > > > > > data the screen provides. (Though there is some special code > >>> > > > > > in the > >>> > > current > >>> > > > > > framework for cleaning up the data from the Droid screen; > >>> > > > > > arguably > >>> > > this > >>> > > > > > should be in the driver or firmware for it, since this is > >>> > > > > > really > >>> > > screen and > >>> > > > > > hardware specific kind of stuff. At any rate, it is not > >>> > > > > > applicable > >>> > > to basic > >>> > > > > > screen capabilities like here.) > > >>> > > > > > There is a good analysis of the G1 classtouchscreen here: > > >>> > > >http://lukehutch.wordpress.com/2009/01/10/full-working-multitouch-on-... > > >>> > > > > > On Fri, Feb 12, 2010 at 4:39 AM, Sean Hodges < > > ... > > Erfahren Sie mehr » -- 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
