Finally, an official bug report of this problem!

Say I am running a Phrogram 3D application.
When I try to read the Mouse location values ( Mouse.X, Mouse.Y, Mouse.Location.X, Mouse.Location.Y ), I can only read them when they are on the extreme right of the program window ( in my case, the screen - due to VMware limitations on graphics acceleration I can only run phrogram 3D apps in fullscreen ).
When I do receive the mouse coords they are very erratic and inaccurate.

This makes no sense. Even in 3D mode, the program should be able to read 2D mouse coordinates normally.

 

Can you post some repro code for me please. Much quicker for me to look at your code than spend time recreating the issue.

---

Managed DirectX and XNA ? Check out http://www.thezbuffer.com

OK, here it is. I'm basically just reading the mouse coords normally ( Mouse.X & Mouse.Y ) and sending the values to a TextLabel.

I was really hoping I could push this one of and blame VMWare (To be honest I am gobsmacked you can run this at all in VMWare!). However I can repro this. Its slightly different for me in that the mouse coordiantes don't get updated at all unless I go outside the window and back in.

I tried adding the age old Delay(1) and DoEvents() workarounds but nothing helped.

The mouse code hasn't been updated or changed in a long time so I am going to have to guess that somehow the mouse coordinates are tied to the 2d/console views and are just not being updated when 3d view is top most. I'll take a quick look in the code tomorow and work out if this is a big fix or not. Maybe I can come up with a workaround then too.

 

---

Managed DirectX and XNA ? Check out http://www.thezbuffer.com

ZMan:

I was really hoping I could push this one of and blame VMWare (To be honest I am gobsmacked you can run this at all in VMWare!). However I can repro this. Its slightly different for me in that the mouse coordinates don't get updated at all unless I go outside the window and back in.

I tried adding the age old Delay(1) and DoEvents() workarounds but nothing helped.

Yeah, I was getting this same error on my PC before I moved to Mac..  A very very early test of BZPhrog ( long time ago! ) revealed that I couldn't use mouse driving as I had hoped. That's when I first discovered this bug. Not sure why I didn't report it until now..

I had to enable a few video options before VMWare would run anything DX. But it does run them! :) I'm really hoping they will eventually have full GPU acceleration in VMWare, but that's wishful thinking..

My 15 minute quick look comes to the same conclusion as my guess. The Phrogram mouse scanning code is actually running in the background so that we can read the mouse even when you are in a tight loop. It tied to a partciluar 'window' (window in this case is what the rest of us call a control) and it looks like thats NOT the 3d one. However my quick look can't work out why its stopping working since the 2d window is still there behind the 3d one.

Anyway no quick fix, nor a workaround right now. Bug is logged for now we will have to say - mice don't work in 3d.

---

Managed DirectX and XNA ? Check out http://www.thezbuffer.com