| Re: [AD] New graphics API, take 2 |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Shawn Hargreaves wrote:
[snip]
Why is AL_DISPLAY different to AL_BITMAP?
The rationale was that Allegro would keep a table of bitmaps somewhere to
represent, for example, all three buffers of a triple buffer display.
al_acquire_display() would simply return the next bitmap to draw on. If we
have one bitmap, then we may need to do through hoops to fill in the vtable
with the proper values for it to reference the correct memory location.
[snip]
That way you just need to do:
global AL_BITMAP *screen = al_create_display(..., single page mode);
to get exact backward-compatible semantics with the current API.
Right.
I find the name al_update_display() confusing.
I agree, but I didn't have any good ideas on to call it.
show_user_contents_of_this_bitmap() seems a bit too much :)
[snip]
I think the D3D name is best: "present" means to do whatever is
required to present the results of your drawing so they will be
visible to the user.
Perhaps ->show() would be more adequate. I read it as "the present" when I
first read the mail :)
show() would also go with the naming that Allegro is currently using, which
may be beneficial in some sense.
[snip]
--
- Robert J Ohannessian
"Microsoft code is probably O(n^20)" (my CS prof)
http://pages.infinit.net/voidstar/