Skip to main content
gamedev.net
🔒 Locked

Mock Controls

Started by FenixRoA Oct 30, 2004 at 10:29 PM 0 replies 550+ views
Original Post
FenixRoA
FenixRoA
I am an intermediate programmer making a, rather sophisticated, DirectX DirectDraw application. My problem is I have never programmed controls such as textboxes. My question is about speed vs. memory. Should I: a) have a static DirectDraw surface with the textbox background and then draw the text on top of it each frame. -Low Memory usage -Low Performance b) Same as above but instead use a seperate surface for each instance of the object to hold the drawn text. -Medium Memory -Medium Performance c) have a seperate DirectDraw surface for each textbox that only gets redrawn when text changes. -High Memory -High Performance. No- I do not want to use the window default control so don't give me any tuts on those. My program calls for high performance over memory saving (ya a game), so my initial reaction is to go for option C however, I wanna make sure that I correctly understand my options. So if you guys who are more experienced then me give me any advice please hit me wit it. Thanks for your time and consideration, FenixRoA
superpig
superpig
You're probably best implementing each one and profiling the results.
Richard "Superpig" Fine - saving pigs from untimely fates - Microsoft DirectX MVP 2006/2007/2008/2009
"Shaders are not meant to do everything. Of course you can try to use it for everything, but it's like playing football using cabbage." - MickeyMouse

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.

Sign in to reply to this topic.