Re: [AD] windows resizing regression

[Trent Gamblin <trent@xxxxxxxxxx>]

Just look at the examples. ex_resize, ex_fs_resize, and ex_fs_window are the only
ones that call al_resize_display. And ex_fs_window is the only one that currently
doesn't have a call to al_acknowledge_resize. It was planned that way from the beginning by Elias and I. Something may have changed that I missed, or something may
need to change, and that's fine... I'm not booting windows again tonight though, I'll
fix it tomorrow or at least look into what the issues are if any. Also, as a side note, the OpenGL driver on Windows doesn't need the al_acknowledge_resize.

And the original reason for the al_acknowledge_resize was that on X11 you have to wait
for an event to come to tell you when you can resize the display, which could take an
indeterminate amount of time. I think Elias simply simplified it by waiting some small fixed amount of time.
--
Trent Gamblin

On 2010-11-08, at 8:33 PM, Evert Glebbeek wrote:

> On 8 Nov 2010, at 22:01 , Trent Gamblin wrote:
>> Sorry, I misread that as ex_fs_resize not ex_fs_window the other day.
>> The bug is in the example. It was always intended that al_acknowledge
>> resize was needed after an al_resize_display.
> 
> I don't think that's true.
>> From what I remember, the rationale was that you don't know when the user is going to resize the display, so you have to call al_acknowledge_resize() at the appropriate time. You (as a user) know when you're calling al_resize_display(), so there is no good reason you couldn't do the acknowledge resize at the same time.
> The OS X port does this explicitly. It also doesn't generate a resize event when you call al_resize_display().
> 
> I think that's also in agreement with the documentation, which lists says nothing about resize events or the need to call al_acknowledge_resize() after calling al_resize_display().
> 
> So I would say that this is indeed a bug in the Windows port that should be fixed. Regardless, behaviour should be the same across platforms, so the behaviour on at least some platforms will need to be modified. I don't know what the X11 port does, but I guess it's similar to the OS X port since this was originally listed as a Windows-specific bug.
> 
> Evert