| Re: [AD] al_toggle_display_flag ALLEGRO_NOFRAME |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Sat Mar 3, 2012, Elias Pschernig wrote:
> On Sun, 4 Mar 2012 12:01:45 +1100
>
> Peter Wang <novalazy@xxxxxxxxxx> wrote:
> > Hi,
> >
> > Why is the verb "toggle" instead of just "set"?
> > 5.1 adds al_toggle_menu_item_flags -- that should be reconsidered.
>
> Can we rename it to al_set_display_flag?
Don't we also now need a unset_display flag? My assumption was that toggle
acted on a given existing display. So there would need to be a set and unset
pair to take the place of toggle.
> > The NOFRAME flag is just confusing. Both the Windows and X11
> > implementations got al_toggle_display_flag(ALLEGRO_NOFRAME) wrong.
> >
> > Unfortunately we have a few negative flags already, but we should
> > avoid adding more.
>
> I don't think they are so bad, else we get confusion with some of the
> flags being on by default and others off. Right now (I think) they are
> all off by default. In this particular case something like
> ALLEGRO_BORDERLESS might be better. But it's also negative so don't
> know.
>
> ---------------------------------------------------------------------------
> --- Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
--
Thomas Fjellstrom
tfjellstrom@xxxxxxxxxx