Re: terminal API: Intent of multiplot suspend/resume?

[Hans-Bernhard B. <br...@ph...>]

Ethan Merritt wrote:
> On Thursday 14 July 2005 11:49 am, Hans-Bernhard Broeker wrote:

>>* Removing suspend()/resume() completely would be a Very Bad Idea[TM].

> Removing them would save about 400 bytes of permanent storage in
> TERM_TABLE.  Other than that it's all cosmetic.

It would also render 5 more-or-less independent terminal drivers 
unusable for interactive multi-plotting.  That's what would make it bad.

> The cause of my confusion was the implication in the existing 
> documentation that these routines could be used to detect the
> change between one multiplot plot and the next.  They cannot.

Yet they are.  See the X11, OS/2 PM, Windows, mac and aquaterm drivers.

But if we do add a "term->next_multiplot()" call or similar, then yes, 
these should probably be modified to move that functionality to the new 
call.  For good measure, such a call should also carry the current 
"interactive" state as an argument, so the driver can decide whether to 
trigger a replot or not.