[AD] [ alleg-Bugs-2388441 ] design bug with al_acknowledge_resize |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: noreply@xxxxxxxxxx
- Subject: [AD] [ alleg-Bugs-2388441 ] design bug with al_acknowledge_resize
- From: "SourceForge.net" <noreply@xxxxxxxxxx>
- Date: Wed, 10 Dec 2008 04:19:23 +0000
Bugs item #2388441, was opened at 2008-12-04 13:52
Message generated for change (Comment added) made by eglebbk
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105665&aid=2388441&group_id=5665
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: 4.9
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Peter Wang (tjaden)
Assigned to: Nobody/Anonymous (nobody)
Summary: design bug with al_acknowledge_resize
Initial Comment:
Peter Hull pointed out a problem with the design of
al_acknowledge_resize() a while ago. Two resize events may come in
without an intervening call to al_acknowledge_resize(). The user may
think he is responding to the first resize event, whereas Allegro is
likely to think he is responding to the second event.
I'm not sure what the practical consequences would really be; probably
none, as the user is likely to see the second resize event pretty
quickly anyway. But we should decide what we want to do about it,
even if it's just documenting it.
----------------------------------------------------------------------
>Comment By: Evert Glebbeek (eglebbk)
Date: 2008-12-10 05:19
Message:
Can we pop resize events that are still in the queue?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105665&aid=2388441&group_id=5665