On Mon, Jul 05, 2010 at 02:55:25PM -0400, Chase Douglas wrote: > If you fix tk to understand multitouch (at least to translate MT events > into a single pointer), then you should be able to just drop the new tk > dynamic library onto your system and everything should work. > > If they statically built in tk, then that's really their problem, and > there's nothing you can do to fx it. > > I don't think fixing toolkits for this will be very difficult. > > I think Qt has already started. They will translate Qt touch into > traditional Qt pointer events by default unless the application specifies > otherwise. I think that's what I read somewhere recently, I could be > wrong.
Motif, Tcl/Tk, wxWindows, AWT, Swing, Xt, fltk, ... > > I also work with academic tools, which were started in the early/mid 90's > > that > > are written in xlib. As yes its nice to examine route by tapping the wires > > to > > follow a path. While I could rewrite that code, its a pretty simple user > > interface that's actually well written. Switching to a tk would probably > > result > > in larger and more complex code. > > I don't mean to be a bear, but at some point you just can't expect > things written 15 years ago to *just work* with the latest technology > paradigms. if the priniciple is essentially the same, then you can. multitouch is different. single touch isn't. single touch is a subset of multitouch and we've supported it for years, we will continue to do so. Cheers, Peter _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
