jeffRCarlson
25th November 2008, 19:15
We are having a problem with the background of our window manager showing a busy cursor. I have deployed through all of the setting and restoring of the overwrite cursor code. We are always doing this in a balanced fashion although there are times when the stack may it several levels deep.
The application and other Windows seem to have a normal cursor after we have restored it. However the background cursor shows busy until you restart the window manager. This happens right after a call to setOverrideCursor setting it to busy.
We have our own cursor class with its own stack. Before we control the cursor we pushed all of the current cursors onto our stack clearing the qt stack. When we destroy our cursor we put all the old cursors back. It's during this restoration process where it gets screwed up while we're cleaning up the modal dialog we just displayed.
Has anybody seen anything like this or have any ideas what might be causing the problem?
The application and other Windows seem to have a normal cursor after we have restored it. However the background cursor shows busy until you restart the window manager. This happens right after a call to setOverrideCursor setting it to busy.
We have our own cursor class with its own stack. Before we control the cursor we pushed all of the current cursors onto our stack clearing the qt stack. When we destroy our cursor we put all the old cursors back. It's during this restoration process where it gets screwed up while we're cleaning up the modal dialog we just displayed.
Has anybody seen anything like this or have any ideas what might be causing the problem?