[SDL] iOS System Callback
jurksztowicz at gmail.com
Tue Mar 27 20:47:56 PDT 2012
Your use of the words 'time-critical' hit the nail on the head.
Perhaps some system might implement such events as signal handlers, which
would add a new synchronization element to handling them. In such cases
clients might not want to enter the murky waters of correct signal handling
and opt to wait for the nice message to be handled in a normal context on
the main thread.
You asked for an example, so I made one up :)
I feel as though we should avoid over-tailoring this patch to iOS, but I
still strongly suggest the callback mechanism, as it's the only way to keep
the library out of the way of clients that want to get down to the metal. I
understand the confusion that might arise from having two delivery
mechanisms, but remember that the library already provides alternate ways
of doing the same thing (such as LoadWAV vs using rwops).
My 2 pennies.
On Tue, Mar 27, 2012 at 10:49 PM, Jared Maddox <absinthdraco at gmail.com>wrote:
> > Date: Tue, 27 Mar 2012 09:59:42 +0100
> > From: Tim Angus <tim at ngus.net>
> > To: SDL Development List <sdl at lists.libsdl.org>
> > Subject: Re: [SDL] iOS System Callback (attn: Piotr Drapich) (fwd)
> > Message-ID: <4F71817E.9030807 at ngus.net>
> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> > On 27/03/2012 08:19, sdl at union.pl wrote:
> >>> It also implements all important iOS events as SDL
> >>> events:
> > I sort of wonder if it's a good idea expose the functionality by events
> > as well as it implies it is expected to work OK where in many situations
> > it won't. It also means the same functionality is exposed in two
> > different ways; this may be confusing.
> At the same time, there may be apps where it makes sense to separate
> time-critical code & non-time-critical code. Can't say that I know of
> any, though (my backburner project likely won't deal with the
> time-critical bits correctly EVER, so.. ). Can anyone think of any
> cases where it would be useful to have both callbacks & events?
> SDL mailing list
> SDL at lists.libsdl.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SDL