MySQL Bugs: #25434: hourglass-mouse-cursor waits for user-input

Bug #25434	hourglass-mouse-cursor waits for user-input
Submitted:	5 Jan 2007 14:55	Modified:	23 Jan 2007 10:44
Reporter:	Yahoo Serious (Silver Quality Contributor)	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.2.9	OS:	Windows (Windows XP SP2, 2000 SP4)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
While checking Bug #25072 I noticed the hourglass-mouse-cursor does not go away when done fetching tablenames (what I was waiting for), but 'waits' for some input (mouse or keyboard, even Alt-Tab will do).

Very minor, but probably also easy to fix ;-)

How to repeat:
- open QB
- click on the unfold-arrow next to any db in Schemata
- wait
>> notice the hourglass-mouse-cursor does not go away until there is any user-input

Suggested fix:
make the hourglass-mouse-cursor go away when done fetching tablenames (if possible, it may be a Windows bug?)

Thank you for a bug report. Verified just as described on XP SP2.

Please check this again with the next release. I cannot reproduce this problem, neither with a slow nor a fast connection.

It still exists in 1.2.9 .
If you do not move your mouse (at all) after the click, the hourglass cursor remains.  It even remains if I press the up/down/left/right-arrow to shift database.
It returns to normal (just an arrow-picture) when left-arrow folds a database.  It also returns to normal when another window pops to the front (e.g. Workpace).

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

Note: the change I applied is rather a preventive one as the problem cannot be reproduced (tested on several machines, by different people). So I have only the option to guess what is wrong. After all it's a minor visual glitch and does not harm functionality. I'm sorry if this fix does not work for you but it is all I can do about it.

I just got a message from one of our developers who can reliably reproduce this problem, so I think it is not a good idea to entirely close the report. However, because of its low impact and importance I'll have to defer it for the time being and will come back to it later, when we have a bit more time.

This bug is not scheduled to be fixed at this time.