Re: [AD] Windows Addition for Message Parsing

[Milan Mimica <milan.mimica@xxxxxxxxxx>]

Evert Glebbeek wrote:
> On 8 Oct 2008, at 13:07, Milan Mimica wrote:
> > There are some D3D functions that we export:
> > AL_FUNC(LPDIRECT3DDEVICE9, al_d3d_get_device, (ALLEGRO_DISPLAY *));
> > AL_FUNC(HWND, al_d3d_get_hwnd, (ALLEGRO_DISPLAY *));
> > AL_FUNC(LPDIRECT3DTEXTURE9, al_d3d_get_system_texture,  
> > (ALLEGRO_BITMAP *));
> > AL_FUNC(LPDIRECT3DTEXTURE9, al_d3d_get_video_texture,  
> > (ALLEGRO_BITMAP *));
> > AL_FUNC(bool, al_d3d_supports_non_pow2_textures, (void));
> > AL_FUNC(bool, al_d3d_supports_non_square_textures, (void));
> >
> > Maybe those would be useful with OpenGL so we can make them driver- 
> > independent.
>
> Possibly, though I would think the last two already have OpenGL  
> equivalents?

You can check if the extension is supported... that's probably a better way 
because you are going to use OpenGL code anyway. Nah, except al_d3d_get_hwnd(), 
I don't find others useful in OpenGL.

> Yes, but not hard coded in the source, surely?

The only way left would be to use allegro.cfg. That's not always convenient.

> What we specifically want to avoid is people using ALLEGRO_D3D  
> because they think that's what they need on Windows to use Allegro at  
> all. People use ALLEGRO_DIRECTX where they should be using  
> ALLEGRO_AUTODETECT with Allegro 4 as well because they think it's  
> better.

A4 forced you to specify something in set_gfx_mode. I expect most users won't 
even bother call al_set_new_display_flags().

> So if we keep it, we need to stress under what circumstances it's  
> needed and more importantly when and why it shouldn't be used.

Sure.

> > ALLEGRO_AUDIO_DRIVER_OPENAL,
> > ALLEGRO_AUDIO_DRIVER_ALSA,
> > ALLEGRO_AUDIO_DRIVER_DSOUND
> > ALLEGRO_AUDIO_DRIVER_OSS
>
> True. By the same logic, those shouldn't be exposed either, and maybe  
> indeed they shouldn't be - not by default anyway (maybe you only get  
> the autodetect drivers when you #include "allegro5/allegro5.h" and  
> need to #include "allegro5/non-portable-driver-ids.h" to get all of  
> them?). In practice though, I see fewer people requesting specific  
> audio drivers than graphics drivers.

This is a bit different. You must pass something to al_audio_init() and 
everything is shorter to type than "ALLEGRO_AUDIO_DRIVER_AUTODETECT" :P So yes, 
hide them.


--
Milan Mimica
http://sparklet.sf.net