From: Atani <at...@at...> - 2005-11-20 18:47:17
|
On 11/19/2005, "Atani" <at...@at...> wrote: >>I think maybe we're looping through the events too quickly. If I add >>a NSLog that outputs point.x and point.y, then the data comes through >>fine, but if I remove the NSLog message then I just get garbage. > >Interesting... I have not had a chance to dig into it yet, I dont know >when I will get to yet.. My son doesnt want to take a nap yet! If I can >get him down I will try to get working on this.. ok, digging done! The NSPoint returned by the locationInWindow method is already translated to window coord, which does not entirely match the docs for that method. That said, I have a local change which does fix this and returned reliable results now. Unfortunately though, NSCursor hide/unhide does not seem to have any effect when called in the switch statement for NSMouseMoved case. I could not locate anything in the docs about this behavior but I think that the NSCursor hide/unhide can not be done from the event thread.=20 Anyone know how to do a defered call in Obj-C? I will be committing this "as-is" shortly since it mostly works.=20 Probably safest to not call the hide methods on OSX yet since it never gets "unhidden" :( Mike |