Changes between Initial Version and Version 1 of Ticket #1458, comment 38


Ignore:
Timestamp:
05/04/14 19:49:27 (4 years ago)
Author:
renatosilva
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1458, comment 38

    initial v1  
    1 As phroggie said, a double click timeout for single click callback could be annoying as well. However, when both events are handled, single click should not disturb a possible double click event (for example focusing a GUI control), which is not possible for this bug. Therefore, responding to a single-click while ignoring next {{{WM_LBUTTONUP}}} messages within next {{{GetDoubleClickTime()}}} milliseconds, just like original patch, is the way to go.
     1As phroggie said, a double click timeout for single click callback could be annoying as well. Also, when both events are handled, single click should not disturb a possible double click event (for example focusing a GUI control), which is not possible for this bug. Therefore, responding to a single-click while ignoring next {{{WM_LBUTTONUP}}} messages within next {{{GetDoubleClickTime()}}} milliseconds, just like original patch, is the way to go.
    22
    33This is the kind of thing that is only as irrelevant as dumb.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!