| Re: [AD] Display options that aren't really options |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: "Coordination of admins/developers of the game programming library Allegro" <alleg-developers@xxxxxxxxxx>
- Subject: Re: [AD] Display options that aren't really options
- From: Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx>
- Date: Wed, 9 Jun 2010 08:14:54 -0600
On June 9, 2010, Elias Pschernig wrote:
> On Wed, Jun 9, 2010 at 3:58 PM, Thomas Fjellstrom
<tfjellstrom@xxxxxxxxxx>wrote:
> > On June 9, 2010, Milan Mimica wrote:
> > > On 9 June 2010 02:39, Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx> wrote:
> > > > Still aren't options regardless.
> > >
> > > I agree. But that's just a little inconsistency.
> >
> > I thought the point of the new api was to get rid of all the little
> > inconsistencies?
>
> So should we rename al_get_display_option() to
> al_get_display_parameter()? (I don't like abbreviations like _param as
> suggested by Peter)
I dunno. if we can make the options which currently don't behave like
"options" like options, then I have no real complaints. Of course I'm not
sure how we can do that, since MAX_BITMAP_SIZE wants two parameters, and the
api takes one. Could do tricks with shifting but that just feels dirty..
Maybe split it into ALLEGRO_MAX_BITMAP_WIDTH/HEIGHT ?
--
Thomas Fjellstrom
tfjellstrom@xxxxxxxxxx