[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
You mean
void (*resize_handler)( int w, int h, void * data );
?
I suppose thats good. data can be set in set_resize_screen_callback:
int some_int;
set_resize_screen_callback( my_resize_handler, &some_int );
Also I think that set_resize_screen_callback should tell allegro whether
or not resizing is allowed. If the resize_handler is NULL then the
driver should not allow resizing.
Christer Sandberg wrote:
On Sunday 19 December 2004 19.22, Jon Rafkind wrote:
The attached patch allows the X11 window driver to be resized. As
May I suggest that the application callback takes a data-pointer in
addition to co-ordinates (implying set_resize_screen_callback to take one
too). I think it is a good thing not forcing people to use global
variables.
Second, I am not sure about what is the current conventions in Allegro, but
if an entity need to be global but is not exported in the API, shouldn't
the name start with an underscore? (I am thinking of the pointer to the
call-back).