> For backward compatibility. Introduce a TimSetSecondsDeferred or something for
the future.
That's a reasonable reason (and is the obvious one). Maybe we'll fix the
simulator to do a synchronous broadcast instead. We only changed it because
there was an app that was calling TimSetSeconds from a background task, and
synchronous broadcasts from background tasks can cause weird problems under
certain circumstances. Luckily, very few people ever have to use background
tasks...
> I would like to continue being supported by Palm and not tinkered with. :-)
We really don't try to tinker with our developers, honest. We just want to make
a great OS.
I didn't expect that this would cause any problems - I guess I should have
thought it out more carefully.
> I was suggesting a one off allocation for efficiency ...
> For nested notifications I would suggest dynamically allocating a stack.
The code would start to get a bit complicated, but the rest of NotifyMgr is
pretty complex already, so what the heck. I'll see what I can do for the next
go-around.
Jesse
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
