Changes between Initial Version and Version 1 of Ticket #10525, comment 3
- Timestamp:
- 05/17/18 09:39:52 (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #10525, comment 3
initial v1 5 5 bgK, I assume the mouse leave event refers to moving the cursor away from the button. If that's the case, then you seem to be under the impression that the button release gfx update isn't currently possible from the mouse click. It actually is, but it's tied to the mouse up component (mouse up event?) of the down/up action of a mouse click. 6 6 7 To clarify this, keeping the cursor over the button, press & hold the mouse down (the cursor will disappear & the sound plays), wait for the cursor to reappear, then release the mouse (the sound button will return to the up position).7 To clarify this, keeping the cursor over the button, press & hold the mouse down (the cursor will disappear, the button depresses & the sound plays), wait for the cursor to reappear, then release the mouse (the sound button will return to the up position). 8 8 9 9 The problem is that the down/up action of an uninterrupted complete mouse click currently coincides with the hide & show actions of the cursor, or specifically, the hard coded delay of 500ms that separates the cursor's actions. As long as the mouse up event of the mouse click occurs after this delay, then the sound button will return to the up position.