Re: [cc65] tgi_init functionality change request

From: Ullrich von Bassewitz; on Date: October 30, 2004, at 05:50 AM -0400
>
>  ..., we will have to think about changing
> the TGI driver spec. to make it possible. Mouse drivers can have an
interrupt
> routed to the driver.  If interrupts are necessary for TGI to make it
work on
> the Lynx, my suggestion would be to make that addition, ...

An IRQ entry point in TGI drivers would be useful on other platforms, too.
You have mentioned the Commodore 64/128's small palette.  Interrupts would
let a driver "multiplex" additional colors onto the screen.

>
> Is it really so bad to have the screen cleared after the program starts
[and,
> does a call to tgi_init()]?

Yes, for two reasons:

1. We might want to switch back-and-forth between graphics and text modes
without loosing what we had put on both screens (a drawing program might
show a menu and a picture).

2. We might want to use two separate programs to draw two different things
on the same graphics screen.

So, I believe that clearing the screen should be the application's
responsibility -- when it wants a virgin screen.

----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.