MacArthur, Ian (SELEX GALILEO, UK) schrieb: >> What I forgot to mention is that I have a touchscreen (respectively >> didn't want to confuse with this, because it is the same than with a >> mouse. But maybe this is a necessary detail...) > > Ah, yes. I remember that you told us this before... I had forgotten. > > Actually, I do think it is a relevant detail - we have done a fair bit > of work here with touchscreens, and I have a few observations and > questions; > > Questions first - > > - how big is the screen? Are we talking about a handheld device, or a > "tablet" device, or a "kiosk" style touchscreen? This makes a big > difference in what the sensible way to lay things out is (screen real > estate, parallax angles, proximity and so forth.) > > - is it stylus or finger touch, or both? Again, that makes a difference, > as stylus touches are better localised on the display... > > Observations - > > A touchscreen is not like a mouse. > We learned that the hard way, our initial touchscreen GUI's were based > on mouse-driven ones, and they were basically unusable. It is actually a > very different idiom, it just looks superficially similar. > To make a credible touchscreen interface, you need to unlearn a lot of > what you thought was valid in a GUI design. > > On a "tablet" device and to some extent on a "kiosk", particularly if > using a stylus, you can make a "mouse style" interface that works. > On a finger driven device, and most small handheld devices, "mouse > style" thinking gives rise to UI's that are not very usable in practice > (though users can learn, with perseverance - as examples compare the > iPod GUI with early Windows Mobile devices...) > > In particular, drop down menus don't work well at all, anything that > needs an accurate double-click pretty much will not work, click regions > need to be very large, precise positioning basically will not work. > > For you interface, I'd suggest that you drop the Fl_Choice altogether > and simply make your own chooser widget that pops a modal dialog (with > no border) filled with nice chunky, easy to click, buttons for each > entry... Clicking on one of those buttons selects the item and dismisses > the dialog (and triggers any callback actions.) > > If screen real-estate is an issue, consider whether the buttons are laid > out in a grid on in a column or etc... > > > So - that is what my experience with touchscreens would suggest. > You may have a different view of course! > > Hope that helps,
Did some little changes in Fl_Menu.cxx. Now it works. Removed the check for DRAG events (approx. line 680) and also removed the check for !Fl::event_is_click() (approx. in line 729). For you this might be tinkered, but for us it's OK, because we are sure that our GUI is almost finished (and will need almost no chagnes) an we will never need the drag function. I allready did the trick you mentioned with the modal dialog and it worked fine... And also many thanks for your tips regarding touch-screens! I will keep them in mind in future! Regards! Michael _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
