> > What are you trying to do with it? I'm curious what it is > > good for (in practice). > > I was wondering that myself.
Well - it kinda depends... If you have multiple pointers you could play that out two ways: 1) 1 pointer bound (in some way TBD) to each app, and run multiple apps at once. This then entails some mechanism for handling focus, such that many apps can have focus at the same time... 2) All pointers bound to the app that has the focus. (There is a third option - some pointers bound to some apps, but that's the "worst case" so let's not do that...) Of these, (1) requires a lot of changes in X (or whatever windowing system) but (2) might be feasible with limited changes, IF the app is multi-cursor aware. That is, the app sorts out the multi-cursor issues for itself, rather than having the WM do it for you. Any app that doesn't know multi-cursor stuff simply gets the "primary" cursor and works as "normal". Any app that is multi-cursor aware handles the multiple cursors for itself, and can then sort out the multi-touch and gestures and all that sort of malarkey internally. Well, that's what I did for an experiment, but I have seen articles elsewhere discussing the same approach, so it seems to be a well-trodden path to getting multi-touch into your app whilst we wait for all the various windowing system to catch up... I guess that's what the OP is trying to do too - introduce some multi-touch/gesture interface into their touchscreen app. But who knows. Still, I think it could be interesting... The whole issue of *where* gestures in general, and multi-touch gestures in particular, should be interpreted (i.e. in the app or in the WM) is an interesting debate. And if gestures are interpreted on the "app-side", should the GUI framework (e.g. fltk) be implementing that, or should it be in the app code itself? I don't know... -- Ian SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
