Index:
[thread]
[date]
[subject]
[author]
From: Jon M. Taylor <taylorj@gaia.ecs.csus.edu>
To : ggi-develop@eskimo.com
Date: Thu, 22 Apr 1999 06:25:33 -0700 (PDT)
Re: aalib target
On Thu, 22 Apr 1999, Brian S. Julin wrote:
> On Thu, 22 Apr 1999, [iso-8859-1] Niklas Höglund wrote:
> > > It would require the AAlib target to overload ggiPutchar() and
> > > friends, right? I think this is possible.
> >
> > The problem is what to do when someone uses ggiPutc() on a coordinate
> > that isn't on a text line, but "between" two.
>
> An extension could fix this -- something like GGIConsoleOverlay;
> it could take over the console as a text visual, and allow/request
> fbcon to render portions of the console during graphics, like it
> does without linvtsw or in aalib/monotext's case, draw portions
> of the console in ASCII text over the image.
Good idea, I didn;t think of that. It'll look a bit more raggedy -
the ASCII art will be brutally clipped at the offending charcell - but it
will result in much faster framerates.
> Of course then you have to deal with potential syslog messages
> and other cruft appearing on the console.
So turn off log messages to the console. I had to do this anyway
- you lose your mind in KGI driver development if those debugging prints
spew out all over your VCs ever time you switch. I'm sure you have seen
this before |->.
Jon
---
'Cloning and the reprogramming of DNA is the first serious step in
becoming one with God.'
- Scientist G. Richard Seed
Index:
[thread]
[date]
[subject]
[author]