probably easier to just draw it yourself as a sprite.
I also had that idea, but I threw it away quickly because quite frankly, wouldn't that lead to freezing the mouse if e.g. the app hangs? Not that this isn't something one wants to avoid anyway, but I don't want to give the user the illusion his PC died when really only the app got some sort of problem. Isn't that quite a common problem with this solution?
never send windows to do a game's job. its designed for business apps, not games. they had to add directx to it cause they were losing the PC game market. only now are they beginning to embrace directx as a better way to do graphics for all of windows. when building games, the best thing to do is get windows the "F" out of your universe, then get on with building a game. this means create a window, go directx fullscreen, and kiss windoze goodbye (except for a message pump)!
Interesting statement, in the past I've read numerous people here stating the exact opposite, namely that you should concern the OS with anything like drawing texts, gui, cursor... I'm not a fan of that eigther, but is it really a good idea to take everything into your own hands?