|
If you were logged in you would be able to see more operations.
|
|
|
Frankenstein
Created: 29/Jun/07 02:20 AM
Updated: 29/Jun/07 07:25 AM
|
|
| Component/s: |
Playback
|
| Affects Version/s: |
0.7,
0.7.5
|
| Fix Version/s: |
0.8
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
I was using Linux, but I think the problem may be platform-independent
|
|
|
When a double_click_tree event starts, eventually frankenstein posts the events mousePressed, mouseReleased and mouseClicked events with click count 1 and 2 respectively and listens to mouseReleased without actually looking for click count. So it notifies by thinking mouseReleased happened. But actually mouseReleased with click count 1 happened, but not the second one.
|
|
Description
|
When a double_click_tree event starts, eventually frankenstein posts the events mousePressed, mouseReleased and mouseClicked events with click count 1 and 2 respectively and listens to mouseReleased without actually looking for click count. So it notifies by thinking mouseReleased happened. But actually mouseReleased with click count 1 happened, but not the second one. |
Show » |
|
Bug
Resolved
Minor
DoubleClickAction hanldes 'waiting for the mouseReleased action' wrong way