[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
--- Angelo Mottola <a.mottola@xxxxxxxxxx> a écrit : > > > with Allegro implies a
cross plateform programming, then I
> > > will always
> > > use
> > > GFX_AUTODETECT_FULLSCREEN or GFX_AUTODETECT_WINDOWED in my progs.
> >
> > I think the user will need those in order to select which mode
> > to use when GFX_AUTODETECT is used, through the configuration
> > file. That said, I've not seen the code, but I assume that's
> > what Angelo did.
>
> Let me explain again:
>
> Current situation: there are 5 gfx driver for BeOS, which different
> AL_IDs and associated constants:
>
> GFX_BEOS_FULLSCREEN = 'BFS'
> GFX_BEOS_FULLSCREEN_SAFE = 'BFSS'
> GFX_BEOS_WINDOWED = 'BWN'
> GFX_BEOS_WINDOWED_SAFE = 'BWNS'
> GFX_BEOS_OVERLAY = 'BOVL'
>
> I'd like to change both constants and IDs in a more pertinent way, so
> that these would look like:
>
> GFX_BWINDOWSCREEN_ACCEL = 'BWSA'
> GFX_BWINDOWSCREEN = 'BWS'
> GFX_BDIRECTWINDOW = 'BDWN'
> GFX_BWINDOW = 'BWN'
> GFX_BWINDOW_OVERLAY = 'BOVL'
>
> This would mean that sources using the old constants (if any) would
> need to be updated. Also, ABI compatibility would be broken as the user
> program could refer to a BeOS specific ID and the Allegro .so file
> could not recognize it... Now normally I'd be very worried about this
> issues, but since we're talking about the BeOS port, and we know there
> aren't many BeAllegro users, I'd apply the changes.
> Your thoughts?
>
> --
> Angelo Mottola
> lillo@xxxxxxxxxx
Oh, in that way... You can obviously apply them :)
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com