I took this comment by Joe Strout from the NUG :
> But I venture to suggest that it's still not a good design -- you're
> going to get the spinning beachball that indicates a frozen app, and
> the user will not be able to interact with your app in any way for 18
> seconds. Much better would be to restructure your code so that the
> line is actually drawn from the Timer, instead of using a tight loop.
> Then you won't need UpdateNow, you won't get the spinning beachball,
> and your app won't essentially be frozen until the drawing is over.
I think I need a tight loop in my game. Is there a way to prevent the beach
ball? The best thing would be if the cursor would be hidden somehow.
I use
#pragma disableBackgroundTasks
#pragma disableAutoWaitCursor
but the beach ball wont go away...
Thanks
Nils
---
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>
|