🚀 go-pugleaf

Gregory L Hansen wrote:
 

> >> Well... if the Blue Box crashes and is restarted, chances are the program
> >> will receive a restart Blue Box event.
> >
> >Then the blue box would have to restart all the applications that were running at the
> >time the blue box crashed. While I certainly consider this a feasible sort of thing,
> >re-loading every application sure does kill the prospect of 'shorter startup times'.
> I don't think you'd have to restart any apps.  As far as I can tell, if
> the restart generates some kind of RestartedBlueBox event, you can
> trivially redraw everything.  

Surely though the routines for window drawing MUST be cooperatively run inside the Blue Box and 
therefore be restarted upon a Blue Box crash. As specs have come by now, there is no way for a 
protected thread to preemptively call the Toolbox.

A problem I see is that there is noone listening to the RestartedBlueBox event since to do 
that, you'd have to run cooperatively inside the Blue Box that has just crashed and is 
recovering itself.


> Everything is linked, so you'll always know how to find anything
> you need.  Then go through it and, one at a time, call the functions you
> used to draw them in the first place.  Replace the old window handles
> with the new ones.

You can't call these functions from a protected thread, and your cooperative Blue Box thread 
has just crashed along with the Blue Box. How are you going to call these functions without 
first restarting your cooperative thread?


> But until we learn more, it's all just blind speculation.

Lot's of fun nevertheless :)



-* no thing *-