From: Thomas F. <tfj...@sh...> - 2009-03-12 23:09:57
|
On Thu March 12 2009, Milan Mimica wrote: > Peter Wang wrote: > >> Let's have a function: > >> void al_clear_screen() { // or rather al_clear_bakbuffer() > >> old = al_get_target_bitmap(); > >> al_set_target_bitmap(al_get_backbuffer()); > >> al_clear_target_bitmap(); > >> if (old != al_get_backbuffer()) > >> al_set_target_bitmap(old); > >> } > >> > >> and make a promise we won't do this with every drawing function. > > > > I don't think it's very useful to clear the backbuffer while keeping > > the target bitmap as something else. Usually you'd clear the backbuffer > > as a precursor to drawing onto it. > > But you sure wouldn't like al_clear_screen() to change the target bitmap. > What you see here are implementation details. The point is, we can have > both al_clear_screen() and al_clear_target_bitmap(). I'm not sure anyone was suggesting having a "al_clear_screen" that always acted on the "screen". Just a function that clears the active target, as thats essentially what the screen is going to be at any given time (even if it isn't you want it to be). > > -- > Milan Mimica > http://sparklet.sf.net > > --------------------------------------------------------------------------- >--- Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com -- Thomas Fjellstrom tfj...@sh... |