0005710: problems from selection locking in pointer events

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0005710

[Croquet] Hedgehog

minor

always

01-07-07 21:54

04-17-07 02:45

Reporter

howardstearns

View Status

public

Assigned To

Priority

normal

Resolution

open

Status

new

Summary

0005710: problems from selection locking in pointer events

Description

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.

Additional Information

Attached Files

Relationships

Notes
(0010563 - 181 - 193 - 193 - 193 - 193 - 193) howardstearns 04-17-07 02:45	By Wisconsin-hrs.137, the KAT code started defining a recursive TFrame>>clearCurrentUser (including a a synthesized #doPointerLeave:), and using it withinin KAvatarReplica>>destroy.

Issue History
Date Modified	Username	Field	Change
01-07-07 21:54	howardstearns	New Issue
04-17-07 02:45	howardstearns	Note Added: 0010563

Mantis 1.0.8[^]

31 total queries executed.
26 unique queries executed.