|Anonymous | Login||08-25-2019 12:30 UTC|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Simple Details [ Jump to Notes ]||[ View Advanced ] [ Issue History ] [ Print ]|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0005710||[Croquet] Hedgehog||minor||always||01-07-07 21:54||04-17-07 02:45|
|Summary||0005710: problems from selection locking in pointer events|
pointerEnter: "grabs" an object for exclusive use until pointerLeave:. There are (at least) two problems with this:
1. If an avatar is disconnected while they have locked up an object, no one else can interact with it.
2. CroquetHarness>>mouseUp: simulates a pointerLeave: to free up the object. This means that button-like objects that act on pointerUp: must be writtent to expect a pointerLeave: afterwords. This gets interesting if pointerUp: deletes the object and pointerLeave: expects the object to be in the scene graph.
(0010563 - 181 - 193 - 193 - 193 - 193 - 193)
|By Wisconsin-hrs.137, the KAT code started defining a recursive TFrame>>clearCurrentUser (including a a synthesized #doPointerLeave:), and using it withinin KAvatarReplica>>destroy.|
|01-07-07 21:54||howardstearns||New Issue|
|04-17-07 02:45||howardstearns||Note Added: 0010563|
| Mantis 1.0.8[^]
Copyright © 2000 - 2007 Mantis Group
31 total queries executed.|
26 unique queries executed.