Move mouse over object

[jacek]

My problem is when I move over the top QGLWidget it seems like it is asking for the scale factors from the bottom QGLWidget and not the top QGLWidget. But once I click on the top QGLWidget, then everything works how I expect it to.

Do event->x() and event->y() return the same values for the top widget in both cases or maybe sometimes you get the mouse position relative to that bottom QGLWidget?

[ToddAtWSU]

Do event->x() and event->y() return the same values for the top widget in both cases or maybe sometimes you get the mouse position relative to that bottom QGLWidget?

Yes they return the same value. event->y( ) returns values between 0-185 and event->x( ) returns 79-955. Both before and after I click on the top QGLWidget.

[jacek]

Yes they return the same value. event->y( ) returns values between 0-185 and event->x( ) returns 79-955. Both before and after I click on the top QGLWidget.

This means that other variables in that conversion formula must have wrong values. How and when do you set them?

[ToddAtWSU]

This means that other variables in that conversion formula must have wrong values. How and when do you set them?

I set them upon creation of the QGLWidget. I have some other functions that get called by the constructor and create the data set that goes and calculates my mins, maxs, widths, and heights for all my different objects. But it looks like I might not be storing my mins and maxs like I thought I was...so I will look more deeply into this and let you know if this is what it is. Thanks a whole lot!!!

[jacek]

I set them upon creation of the QGLWidget.

Remember that widget size isn't correct until the widget is shown for the first time.

[ToddAtWSU]

The widget size wasn't causing my problem. I was forgetting to initialize my mYMin value after I added data. The data itself knew what the min was, but since I use it so frequently I had a variable in my other class to hold it, and I forgot to update it. But now that I initialized it, it works fine! Thanks for your help and I guess I should debug more first before blaming Qt!