|Re: [AD] MSG_IDLE in grabber and menus|
[ Thread Index |
| More lists.liballeg.org/allegro-developers Archives
> Well, if you don't use do_dialog, but update_dialog, anything can run
> while the menu is running. But I guess, if it is done only for
> do_dialog, this works quite well, and you're right - I can't see a
> reason why yield_timeslice might hurt - since no (CPU intense or not)
> user code can be running anyway.
Haven't menus been made non-blocking? In that case, there should be no call
to yield_timeslice() forced from the menu code.
I'd be in favour of scanning for d_yield_proc().