Anonymous | Login | 04-11-2021 16:18 UTC |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||||
0002994 | [tweak] Any | minor | always | 02-21-06 09:58 | 07-07-06 09:50 | ||||||||
Reporter | bernd | View Status | public | ||||||||||
Assigned To | bert | ||||||||||||
Priority | normal | Resolution | duplicate | Platform | |||||||||
Status | resolved | OS | |||||||||||
Projection | none | OS Version | |||||||||||
ETA | none | Product Build | |||||||||||
Summary | 0002994: mouseclick event order | ||||||||||||
Description |
when registering eventhandlers for #mouseClick and #mouseDoubleClick, they are signalized in wrong order when double clicking. so after the doubleclick-event another click event is signalized, that may destroy the work, done by the doubleclick handler. solution: first signal #mouseClick then #mouseDoubleClick in a doubleclicking situation |
||||||||||||
Steps To Reproduce | |||||||||||||
Additional Information | |||||||||||||
Attached Files | |||||||||||||
|
Mantis 1.0.8[^]
Copyright © 2000 - 2007 Mantis Group
41 total queries executed. 33 unique queries executed. |