Re: [AD] windows resizing regression |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
IMHO the proper behavior is to send event when user resize window
manually, after calling al_resize_display(), after changing from/to
windowed/fullscreen mode (is there any event to notify about that?).
al_acknowledge_resize() is not necessary from the point view of the
user. Just yet another thing to remember about. I first thought
handling resize event is good enough, because this is the right place
to handle incoming changes. Events are processed in single thread, so
I will not be drawing while processing event queue.
2010/11/9 Elias Pschernig <elias.pschernig@xxxxxxxxxx>:
> On Tue, Nov 9, 2010 at 1:34 PM, Evert Glebbeek <eglebbk@xxxxxxxxxx> wrote:
>>
>> On 9 Nov 2010, at 7:10 , Elias Pschernig wrote:
>> > Getting ALLEGRO_EVENT_DISPLAY_RESIZE events in response to
>> > al_resize_display can be nice since you could handle all resizes in your
>> > event handler, whether it's a user-initiated or program-initiated resize. At
>> > the same time there's no need to require an al_acknowledge_resize after
>> > al_resize_display.
>>
>> But then you're not really handling anything, are you? :P
>
> Well, you might do additional game-specific things, like using a new scaling
> transform, use a different UI layout, re-load different fonts for the new
> size... but yes, you would have that in a function anyway so no big deal
> whether you call it from one or from two places.
>
>
> ------------------------------------------------------------------------------
> The Next 800 Companies to Lead America's Growth: New Video Whitepaper
> David G. Thomson, author of the best-selling book "Blueprint to a
> Billion" shares his insights and actions to help propel your
> business during the next growth cycle. Listen Now!
> http://p.sf.net/sfu/SAP-dev2dev
> --
> https://lists.sourceforge.net/lists/listinfo/alleg-developers
>
--
thedmd, Michał Cichoń
Artifex Mundi
michcic@xxxxxxxxxx
http://www.artifexmundi.com