From: Neil R. <ne...@co...> - 2003-11-27 23:03:15
|
Fabio Stange wrote: > I know what you mean, but buffering things your way, I have to worry=20 > about where I=B4m writing to now. Am I writting to the screen or to my=20 > buffer? I also need to worry avout copying screen contents to my buffer= =20 > everytime, and so on. No, if you have BITMAP *buffer; and you blit something to buffer, you=20 can be 100% certain it will be drawn in the buffer and not on screen. ;)=20 Also, why would you copy the screen contents to the buffer?! You take=20 your graphics bitmaps you loaded from datafile or disk and you blit them=20 as needed to the buffer, when you're done creating your scene you blit=20 the finished scene to the screen and start over drawing the next scene.=20 Why would you ever want to blit the screen back to your buffer, not=20 only would that not make any sense, but it would be slow (reading video=20 memory). > By doing my way, you never need to worry where you are drawing your=20 > stuff. If you want to bufferize all your work you just did, just put=20 > StartBuffering before your code and FlushBuffer after it. You can Buffe= r=20 > and de-buffer your stuff anytime without changing anything. Huh? <scratches head> > And I never did temp =3D myscreen =3D screen. I did temp =3D my_screen,= then=20 > redirected my_screen to the real screen, but temp still points to the=20 > old my_screen to be able to destroy it later. Okay, I think I see what you are getting at now. You call a function,=20 if you wish to draw directly on the screen you simply redirect your=20 buffer to the screen. I don't see why you would want to do it that way=20 though, seems to overcomplicate things to me. <shrug> --=20 Neil Roy "No one has ever gone into heaven" - John 3:13 |