[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
--- Angelo Mottola <a.mottola@xxxxxxxxxx> a écrit : > Title says it
all.
>
> I've put up the modifications I talked about in my previous posts; no
> one replied so I thought it was ok to put them up. I've not touched
the
> drivers IDs as I wanted to, to preserve ABI compatibility; I wonder
if
> this matter though as the BeAllegro users could be less than 100
> (optimistic extimation)... What do you think? Should I change the IDs
> to more pertinent ones?
>
> Another thing: as I was there I've added another new gfx driver,
using
> the BeOS overlays. This has been tested a little, and seems to work
ok;
> it always runs fullscreen using hw scaling, so it allows any
> resolution, and this is very nice under BeOS, where the default
> fullscreen gfx driver doesn't allow low resolutions...
>
> --
> Angelo Mottola
> lillo@xxxxxxxxxx
>
That's great that you completely rewrote a new gfx driver for BeOS!
However, I think
that there is no matter to use pertinent IDs or not on BeOS. I mean
that programming
with Allegro implies a cross plateform programming, then I will always
use
GFX_AUTODETECT_FULLSCREEN or GFX_AUTODETECT_WINDOWED in my progs.
That's up to you
:)
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com