Silly oversight that replaced the frame-enabled function with a simplified
non-frame-enabled function. Fixed locally. Will be in the next build.
This function no longer uses the lazy pattern at all, leaving
getMousePosition as the only one that does. Glad to be rid of that
complication for this one.
Get the feeling I didn't test much with frames when this was first slapped
together? :) Testing the new frames-based examples with widgets has
illuminated a few problems.
Original issue reported on code.google.com by dmark.ci...@gmail.com on 6 May 2010 at 3:10
Original issue reported on code.google.com by
dmark.ci...@gmail.comon 6 May 2010 at 3:10