[Qt-interest] Mouse movement required to make things happen?

[Eric Clark]

Btw, I would also like to point out that we can see this anomaly on both Windows Vista and Windows 7, 32-bit and 64-bit. Our application is always a 32-bit build and we are currently building under Qt 4.6.1.

One more thing, if there is animation going on in our QGLWidget, when the menu is transparent (the anomaly), the QGLWidget stops rendering. It probably does when there is no animation as well, but it is hard to see because, well... there is nothing moving in the viewer.

Eric

> -----Original Message-----
> From: qt-interest-bounces at trolltech.com [mailto:qt-interest-
> bounces at trolltech.com] On Behalf Of Eric Clark
> Sent: Tuesday, February 23, 2010 1:18 PM
> To: qt-interest at trolltech.com
> Subject: Re: [Qt-interest] Mouse movement required to make things
> happen?
> 
> I am experiencing very similar behavior. We have a context menu that
> appears when you right click on an item in a QTreeView. When the user
> right-clicks, a completely transparent menu appears where you can just
> barely see the beveled edges only. If the user moves the mouse in any
> direction, the popup menu will completely appear.
> 
> In our application, we have a QGLWidget (or 2 or 3 or more) as the
> central widget in our main window. We have the ability to turn off the
> rendering of the QGLWidgets by a click of a tool button. If we turn off
> the rendering, the anomaly does not happen, it works just as usual.
> When the user right-clicks the item in the tree view, the popup
> (context) menu appears just fine without any need for extra mouse
> movement.
> 
> I wonder Bob, do you have any QGLWidgets in your application?
> 
> Eric
> 
> > -----Original Message-----
> > From: qt-interest-bounces at trolltech.com [mailto:qt-interest-
> > bounces at trolltech.com] On Behalf Of Bob Hood
> > Sent: Tuesday, February 23, 2010 1:05 PM
> > To: qt-interest at trolltech.com
> > Subject: [Qt-interest] Mouse movement required to make things happen?
> >
> > We're seeing a rather strange behavior (Qt 4.6.1 Windows Vista 64-
> bit,
> > and verified to also happen with 4.6.2).  We're seeing action
> initiated
> > by the user (from the GUI) requiring the mouse to move before they
> > begin.  For example, I have a window that animates as an overlay onto
> > the main interface, and I do this using a timer to move it manually.
> > When I activate the code by selecting a menu item from the main
> > interface, if the mouse remains perfectly still, the window will not
> > appear.  It is only after I move the mouse at least one pixel in any
> > direction that the mechanism activates, and the window pops into
> view.
> >
> > Note that I've also tried using QPropertyAnimation, and I have the
> same
> > problem after start()'ing it.  The mouse has to move at least one
> pixel
> > before the animation will commence.
> >
> > Anybody have any clues as to why this weird Qt behavior is occurring,
> > and how to make it stop?
> >
> > _______________________________________________
> > Qt-interest mailing list
> > Qt-interest at trolltech.com
> > http://lists.trolltech.com/mailman/listinfo/qt-interest
> 
> _______________________________________________
> Qt-interest mailing list
> Qt-interest at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-interest