One other thing!

Started by
1 comment, last by ghost1206 22 years, 3 months ago
One other decision I''ve already made (and I am not too sure if it''s correct) concerning the game, has to do with the way the screen is updated. I''ve used directInput and had the pointer blited each time I get a mouse event. The thing is that I am NOT following Microsoft''s example having a function ("updateFrame") called constantly to update the screen, but rather a function that is called only if something occurs (e.g. a mouse event or something else). Is this the right way to do things, or I should follow Microsoft''s example. It''s just that it strikes me as not too efficient. Any thoughts?
Advertisement
How often will the images on screen change? If it''s pretty often, just redraw everything as soon as you can; It''s not that inefficient in that case. Otherwise, your approach is basically what you should be doing.

[Resist Windows XP''s Invasive Production Activation Technology!]
That''s my thinking too. Since the game is a strategy (and not let''s say an RTS) there is no reason why I should be bliting like a madman, but only when it''s necesssary. Thanks!

This topic is closed to new replies.

Advertisement