Changes between Initial Version and Version 1 of Ticket #15133, comment 5


Ignore:
Timestamp:
Apr 13, 2012, 2:09:08 AM (8 years ago)
Author:
bill
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #15133, comment 5

    initial v1  
    11Hmm.   I see the problem you are talking about, but it seems like a grid issue, so I filed #15167.
    22
    3 The 0ms timeout is intentional.   It's for when a user clicks on a non-focusable button (or image, or whatever) in order to trigger a Dialog.    When the user closse the Dialog, the Dialog tries to restore focus to wherever it was previously, which means that we want to notice that the mousedown on the non-focusable button/image cleared the focus before the mouseup causes the Dialog to appear.    (Actually, this is what requires 0ms timeout for the curNode, not for the widget stack, but it seems like they should both have the same timeout.)
     3The 0ms timeout is intentional.   It's for when a user clicks on a non-focusable button (or image, or whatever) in order to trigger a Dialog.    When the user closex the Dialog, the Dialog tries to restore focus to wherever it was previously, which means that we want to notice that the mousedown on the non-focusable button/image cleared the focus before the mouseup causes the Dialog to appear.    (Actually, this is what requires 0ms timeout for the curNode, not for the widget stack, but it seems like they should both have the same timeout.)