[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Ben Davis <ben@xxxxxxxxxx> wrote:
> There's clearly a debate about the intended purpose of GFX_SAFE. I believe
> it was created initially as a kind of hack for getting into any graphics
> mode just to display a dialog or something. However, people now want to use
> it to set a graphics mode in a polished program where the resolution doesn't
> matter.
>
> Maybe we need a new mode for the latter, like GFX_ANY ? Then GFX_SAFE would
> really do what the name says it should :-)
We've had this dicussion at least once before, without resolution.
We had the same names for the constants as well (GFX_ANY and
GFX_SAFER). I don't think we should introduce a new constant.
Either keep the current behaviour (i.e. die if can't set a mode) or
bite the bullet and make GFX_SAFE return an error code like
everything else.
Personally, I'd have to go with the latter, as I don't like
functions except `exit' and the like to kill my program. The former
is just a specialised case of the latter (albeit convenient for the
example programs).