Re: [AD] al_acknowledge_display_disconnected |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On 2012-05-23, at 8:39 AM, Elias Pschernig wrote:
> I think that is impossible, since the user code always can be in the
> middle of, let's say, an OpenGL call. We do not have any locks around
> our drawing functions (and even if we did, we allow direct use of
> OpenGL). So as far as I can see, there is no way around waiting for
> the user to handle the event. Only at that point do we know that they
> are not accessing anything which would crash immediately when the
> OpenGL context goes down.
Yeah, this is why it can't be done that way. Seems to be a common thing
between iOS and Android, lots of blocking threads until user responds.
Sort of reminds me of D3D. All 3 are sort of hard to fit into the Allegro 5
API, they seem to be made under the assumption that you'll use them
directly, in which case these things aren't a problem.
Trent