From: Karri Kaksonen; on Date: November 07, 2004, at 09:24 AM -0500 > > On Sat, 6 Nov 2004, Ullrich von Bassewitz wrote: > > On Thu, Nov 04, 2004 at 09:22:54AM -0500, Greg King wrote: > > > 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). > > > > OK, that sounds reasonable. But then, what should tgi_init() do? > > Setting the palette to default also will change the appearance > > of the displayed screen. > > Therefore, you should not set the palette to default. > > The "default" palette could mean that the hardware will use those values > in case no initialisation is done. Most of the things that tgi_init() now does should be moved to tgi_install(). The default settings should be initiated only once; after that, the current settings -- whatever they happen to be -- should be retained. Clearing the screen is the only "one-way street." It would be either tedious or impossible for a program to recover from that act. So, neither one of those TGI functions should do it. The instructions for TGI programming should say that programmers must clear the graphics screen explicitly [tgi_clear()] if they want to start their drawings on a freshly scrubbed canvas. ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Sat Nov 13 21:27:53 2004
This archive was generated by hypermail 2.1.8 : 2004-11-13 21:29:33 CET