> We will think about, but we think to patch like i've described
> because we surely would not intruduce bugs with the this code.

I wasn't suggesting there was anything wrong with your patch (although
it might change the ABI, but I think not.)

Rather, it was just that, from our experience with touch screens, the
"user experience" is greatly enhanced if you avoid anything that
involves double-clicking, as it generally doesn't work very well.

In the early days, we did tailor the code to support double-clicks on
the panels, but then found there was huge variation between different
users, and different makes of panels, and finding a combination that
suited all the combinations reliably, whilst not introducing any
spurious behaviour (in some cases the click separation distance had to
be set so large that it affected single-clicks on small adjacent
widgets... Small adjacent widgets are another thing we try not to do
anymore!)

YMMV, of course, but I really think that the correct solution for
touch-screens is to design for single-clicks, and fairly large widget
separation distances, or the "user experience" suffers a lot. It's fine
for users who are familiar with the quirks of the touch-screen, but
others can find it a very negative experience if it is not done right.
-- 
Ian



SELEX Sensors and Airborne Systems Limited
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-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to