Hi! On Mon, Sep 07, 2009 at 01:21:03AM +0100, Jonathan Graham Harston wrote: > > Message-ID: <f97798c20909061455i481d6fb8n6894156a2dbd0db4@mail.gmail.com> > > Oliver Schmidt wrote: > > From my perspective the actual "new" API could look like this: > > > > unsigned char __fastcall__ videomode (unsigned char mode); > > > > #define VIDEOMODE_40COL 0x?? > > #define VIDEOMODE_80COL 0x?? > > How about videomode(unsigned int mode) ? Then you could pass column > and rows. The idea is nice, but it makes the switching code larger and more complex, while most programs won't use it. Having just 40x25 and 80x25 chars for now will suffice for more than 98% of all needs and the necessary routines will be really small. My suggestion would be to implement it as suggested by Oliver. We can still add more video modes later even using your scheme, because the constants 0x0000 and 0x0001 could be handled special in upcoming code. Regards Uz -- Ullrich von Bassewitz uz@musoftware.de ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Mon Sep 7 08:54:18 2009
This archive was generated by hypermail 2.1.8 : 2009-09-07 08:54:19 CEST