No question is stupid, it's good that you are thinking about the different ways to do things.
Sprites are a much better way to manage your screen entities than drawing. The pipeline is optimised for this way of working.
You can actually draw to the screen (
DrawBox() etc). But using these methods means you have to redraw every cycle. Sprites are persistent, once you have created and positioned them, they will remain until you move or delete them.
It is also possible to use the draw commands and then
GetImage(). then you can
CreateSprite() from the image and you have the best of both worlds. You would normally create the images at the start, because it is a slow command. Only milliseconds, but eats up a lot of your framerate when running at 60FPS.
Images are cheap in terms of file size these days, if that is your concern.
Text is best created using the
CreateText() and related commands. It is generated from a bitmap atlas of the font. (There are free tools on the forum here to make your own). If you want to parent it to a button, then you could use the
getImage() approach described earlier. This is exactly what I do
It is worth creating a small routing that you pass the button, text and font into, and to returns a finalised image for you.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Quidquid latine dictum sit, altum sonatur
TutCity is being rebuilt