|Anonymous | Login||03-07-2021 08:50 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|
|0000848||[Croquet] Jasmine||minor||sometimes||01-28-05 16:04||06-08-05 15:58|
|Summary||0000848: error if selectedPointer in #TUserCamera is nil|
There occurs an error in #TUserCamera>>mouseMove: when selectedPointer is nil.
I don't used TeapotMorph here, but a subclass of it where the navigation works in some other way. Maybe it's because there is a bug in there, however, you should catch that in #TUserCamera>>mouseMove: and #TUserCamera>>mouseUp:, shouldn't you?
|Attached Files||selPointerFix-bf.1.cs.gz [^] (645 bytes) 06-08-05 15:58|
(0001108 - 818 - 854 - 854 - 854 - 854 - 854)
Also, a tiny bit of documentation would be nice regarding what the difference of pointer, currentPointer and selectedPointer is in TUserCamera. This is what I got from RTFC:
CurrentPointer is set to the camera's normal pointer before rendering each frame. When rendering an overlay containing that overlay's camera's pointer the currentPointer is set to the camera pointer of the overlay. SelectedPointer is the one that was current when the red mouse button went down, it is reset to nil on red button up.
So currentPointer is the pointer of where the mouse was in this frame, whereas selectedPointer is the one used in an down-move-up transaction. Is that correct?
I just can't figure out the code in mouseMove:/mouseUp: that is, when and why currentPointer vs. selectedPointer vs. pointer is used there ...
(0001597 - 21 - 21 - 21 - 21 - 21 - 21)
|uploaded proposed fix|
|01-28-05 16:04||grit||New Issue|
|01-28-05 17:22||bert||Note Added: 0001108|
|06-08-05 15:58||bert||File Added: selPointerFix-bf.1.cs.gz|
|06-08-05 15:58||bert||Note Added: 0001597|
| Mantis 1.0.8[^]
Copyright © 2000 - 2007 Mantis Group
38 total queries executed.|
29 unique queries executed.