Re: demo stuff

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

Ethan A Merritt wrote:
> On Friday 20 August 2004 12:50 am, Hans-Bernhard Broeker wrote:
> 
>>That almost invariably
>>has to go through term->options(), which I'm quite sure most terminals
>>will fail on if you try it between term->graphics() and term->text(),
>>i.e. while the graphics is open.
> 
> 
> Where do you see a problem?  

That calling term->option() in any other place in the terminal API usage
than right at the start of a terminal's usage.  It's almost sure that at
least some of the drivers have hardwired in the assumption that the call
order given in term/README is fixed, and thus hardwired assumptions 
about call order into the driver.  term->option() was never designed to
be used like this, so it *will* break, in rather interesting fashions.

E.g.: those drivers that keep a polyline open between drawing operations
will almost certainly not have thought of closing that properly at the
start of their term->option() implementation, because it was never
needed before.

 > term->option() does not actually *do*
> anything; it just loads some fields in the terminal data structures.

Which term->option() in particular are you speaking of?  There are 
dozens of them, each a bit different.

-- 
Hans-Bernhard Broeker (br...@ph...)
Even if all the snow were burnt, ashes would remain.