[lcdproc] What is the current version to start developing?

[Joris Robijn]

> wwf@splatwerks.org wrote:
> 
> > It's probably easier to just define a certain priority level that
> > means "run this on exit only." The original idea posted here a bit ago
> > mentions this too. You define the screen, then make sure the widgets
> > are filled out before exiting.
> 
> I would discourage this idea.  Then you wind up having a priority which
> means something OTHER than a display priority.  I would prefer to keep
> the priority ONLY for how often a standard screen will be shown.

I Agree. This has caused too much trouble in the software world already 
:)

> Setting up a screen called "exit" is simplicity from both ends; then all
> the server really has to do is extract "exit" from the screen_list, and
> save a pointer to it in a global location:

Why not give the screen a flag that it is an exit screen. If you want 
it to be invisible normally, use a low priority. (or is there a command 
to really hide it ?)

> > Perhaps the server could include a "hey, client, you claim
> > to have an exit screen defined, so gimme your stats, I'm going away
> > real soon!" message when it shuts down?

The client could quickly add a screen that it wants as exit-screen, 
with the 'retain on exit'-flag set.

Joris

-- 
 Joris Robijn <joris@robijn.net>
 Home: 053 4311 553
 Mobile: 06 288 41 964

 // To understand recursion, we must first understand recursion


-----------------------------------------------------------
To unsubscribe from this list send a blank message to
lcdproc-unsubscribe@lists.omnipotent.net