|
Vankwysha
Squire
Australia
43 Posts |
 Posted - Jul 14 2005 : 03:12:39 AM
|
| I've been working on my mouse code recently, and I've found a hitch while working with exclusive control. I have a simple test app using Direct3D, but whenever I operate in full screen and give the mouse exclusive/foreground control, I can't see the windows cursor. I have a font object outputting the co-ordinates of the mouse, so the mouse is being moved as normal, I just don't have a cursor. Is this what's actually meant to happen? So far the work-around that I'm using is actually having a sprite/texture object and keeping it at the point where the cursor should be, but it is slightly laggy. |
|
|
Struan
Squire
21 Posts |
Posted - Jul 14 2005 : 6:20:56 PM
|
I am pretty sure that is by design, if a program has exclusive control of the mouse then it doesn't show the windows mouse. It should be easy enough to draw a cursor if you want to display the mouse.
|
 |
|
|
Vankwysha
Squire
Australia
43 Posts |
Posted - Jul 15 2005 : 12:39:24 AM
|
| Yeah, that's what I thought, thanks. |
|
|
|
Struan
Squire
21 Posts |
Posted - Jul 15 2005 : 01:58:15 AM
|
| If its the kind of app where you want the windows mouse then why don't you just use the standard VB mouse events? |
|
|
|
Vankwysha
Squire
Australia
43 Posts |
Posted - Jul 16 2005 : 12:21:02 AM
|
| I don't want the windows cursor, I was just wondering why it wasn't there and the best way to work around it. Anyways, I've written all my events and I don't want them to go to waste. |
|
|
DirectInput
