My test project is basically the "Win32 Project" template in Visual C++ 2010, with the changes outlined below. Choosing different cursors in display preferences makes no difference Switching aero on or off makes no difference.NVidia graphics card with latest drivers (v270.61). ![]() I've had someone else running Windows 7 64 bit confirm that they experience the same problem, but another tester on Vista does not have the problem. I would expect the red line to match up exactly with the vertical part of the I-Beam, but this is not the case.Īs you can see, the red line is two pixels to the left of where it should be (the behaviour is correct for the standard arrow pointer), so it appears that the hotspot for the I-Beam cursor is wrong. All it does is turn the cursor into an IBeam and render a vertical red line where the last mouse down event was. I've written a very simple win32 program to demonstrate the problem. Basically, the x-coordinate is always two pixels left of where it should be. ![]() On windows, the coordinates returned for a "mouse button down" event seem to be slightly wrong for an I-Beam cursor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |