|
Mantis - tweak
|
||||||||||
| Viewing Issue Advanced Details | ||||||||||
|
|
||||||||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: | |||||
| 2994 | Any | minor | always | 02-21-06 09:58 | 07-07-06 09:50 | |||||
|
|
||||||||||
| Reporter: | bernd | Platform: | ||||||||
| Assigned To: | bert | OS: | ||||||||
| Priority: | normal | OS Version: | ||||||||
| Status: | resolved | Product Version: | ||||||||
| Product Build: | Resolution: | duplicate | ||||||||
| Projection: | none | |||||||||
| ETA: | none | Fixed in Version: | ||||||||
|
|
||||||||||
| 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: | ||||||||||
| Relationships |
| |||||||||
| Attached Files: | ||||||||||
| Notes | |||||
|
|
|||||
|
|
||||