Re: [AD] mode list update and implementation for vga, modex and xtended gfx drivers.

[Henrik Stokseth <hstokset@xxxxxxxxxx>]

On Tuesday 14 August 2001 22:56, Henrik Stokseth wrote:

> i saw angelo mottola implemented fetch_mode_list() on the beos fullscreen
> driver. that's nice. i've updated it and made sure the list is properly
> terminated by an { 0, 0, 0 } entry. please look over it.

btw! angelo, does this modelist cover *all* *valid* modes on this driver? i 
just want to know... and is there a syscall for enumerating the modes instead 
of defining them?

--

while on the topic. the proposed rewrite of the graphic modes selector will 
result in a dialog which will perhaps be a little big for a 320x200 mode. i 
was thinking perhaps to split it up and let the user first run a driver 
dialog and then the either a resolution dialog or a resolution/colordepth 
dialog.

one of the things that concerns me most is to avoid having an 
unneccesary big 'default' mode list. (the mode list that will be used for 
drivers that doesn't have the fetch_mode_list() capability.) to avoid that 
problem we could use separated resolution and colordepth selectors like 
allegro currently uses instead of a 'default' mode list.

the design plan looks something like this now:

-Driver selection dialog.
   if (driver->fetch_mode_list)
      -Resolution dialog. 
      -Combined Resolution and Colordepth dialog.
   else
      -Resolution dialog with 'default' resolutions.
      -Sepparated Resolution and Colordepth dialog with 'default' resolutions.

hope this isn't too unclear. please send your opinions and suggestions to my 
email address.

-henrik