[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On 2008-04-21, Milan Mimica <milan.mimica@xxxxxxxxxx> wrote:
> Peter Hull wrote:
> > I've done pretty much the same thing but I have added a field called
> > 'display_group' to the OSX-specific display structure which is
> > supposed to keep track of which displays are compatible with each
> > other.
>
> Great. Looks good.
>
> > The only down-side is that we have to do all that conversion to memory
> > bitmaps even if the app is actually just about to quit. I can't see a
> > way around that.
>
> Yeah. Users will destroy their bitmaps, if they experience slowdowns, which I
> both find very unlikely to happen.
Should we guarantee to destroy bitmaps when Allegro shuts down?
I think we probably should, as we do for displays and some other objects.
If that's the case, then we can set a flag when Allegro is shutting
down. Bitmaps destroyed by the process of shutting down Allegro won't
need to be converted to memory bitmaps.
Users who are meticulous about freeing their resources won't be
punished, as long as they destroy bitmaps before displays :)
Peter