[AD] Proposed clarification of get_gfx_mode_list |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: Allegro Conductors <conductors@xxxxxxxxxx>
- Subject: [AD] Proposed clarification of get_gfx_mode_list
- From: Grzegorz Adam Hankiewicz <gradha@xxxxxxxxxx>
- Date: Mon, 11 Mar 2002 20:05:16 +0100
Hi.
This has been causing headaches to a friend of mine:
Index: allegro._tx
===================================================================
RCS file: /cvsroot/alleg/allegro/docs/src/allegro._tx,v
retrieving revision 1.29
diff -u -r1.29 allegro._tx
--- allegro._tx 23 Feb 2002 19:20:20 -0000 1.29
+++ allegro._tx 11 Mar 2002 19:02:13 -0000
@@ -2196,7 +2196,10 @@
} GFX_MODE_LIST;
<endblock>
If this function returns NULL, it means the call failed. The mode entry
- points to the actual list of video modes.
+ points to the actual list of video modes. Note that you are meant to use
+ _real_ drivers as the card parameter, which means that this function
+ will always fail if you are passing GFX_SAFE, GFX_AUTODETECT, or any
+ other 'magic' driver.
<codeblock>
typedef struct GFX_MODE {
int width, height, bpp;
I understand that this happens because some available drivers wouldn't
be able to report modes until selected, but then, isn't this function
really pointless? It doesn't seem to fulfill the task of helping out
the programmer, rather seems to ask for writting lot's of #ifdef'ed code
for each driver/platform...
--
Grzegorz Adam Hankiewicz gradha@xxxxxxxxxx http://gradha.infierno.org/