On 29.11.2010, at 10:29, MacArthur, Ian (SELEX GALILEO, UK) wrote: > >>> What are you trying to do with it? I'm curious what it is >>> good for (in practice). >> >> I was wondering that myself. > > 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 have seen 3D apps where one mouse would be used in the conventional way and a second mouse was used to position and rotate the 3D scene. They would also provide support for Spaceball type devices, etc. . Quite specific stuff. In these days, Multitouch is probably the thing that is needed, mostly for gestures. I was pondering an optional FLTK extension (run-time linakable would be great), name FLTK touch, that would handle multiple cursors, gestures, and other typical touch input. It would also change widgets for touch usage (text widgets open a keyboard, no visual focus, menus open differently, assuming a hand covers the bottom right (or left) of the display, etc.). One more reason to wrap up 1.3.0 ;-) - Matthias _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
