From: Sam S. <sam...@gm...> - 2005-11-19 23:04:50
|
On Nov 19, 2005, at 4:48 PM, Atani wrote: > Ok, I will look into it while fixing the Y invert. > 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. > How about Tiki::showCursor(boolean)? > Done. I'll commit this in a few minutes for OSX. I wanted to re- show the cursor when it leaves the window, but Tiki isn't receiving mouseEntered / mouseExited. I added some code to mouseMoved to show/ hide based on whether it's inside the window bounds, but it's kind of quirky since the coordinates aren't working. I'll leave this part commented out, and just use the instant show/hide that happens during showCursor(bool) for now. > How about a generic Cursor drawable which you can bind by > Device::Type? > I'll play around with this. I initially thought to use an Anim so that anything could be a pointer, but I suppose I could also have the Cursor drawable see if it has any subdrawables attached, and only draw a triangle if there's nothing else to draw. -Sam |