After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 361214 - toolbar buttons lose sensitivity between levels and games
toolbar buttons lose sensitivity between levels and games
Status: RESOLVED DUPLICATE of bug 56070
Product: gnome-games-superseded
Classification: Deprecated
Component: gnobots2
2.14.x
Other All
: Low minor
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-10 18:14 UTC by Teppo Turtiainen
Modified: 2006-10-14 04:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Teppo Turtiainen 2006-10-10 18:14:09 UTC 
Please describe the problem:
The toolbar buttons stop responding to mouse clicks when a new level or game begins if the mouse pointer hasn't moved since the previous game or level. The button starts working again if I move the mouse pointer away from the button and back on top of it.

Steps to reproduce:
1. Start a new game.
2. Click the Wait button until the robots get you (you can reproduce this with any of the buttons but it is easiest with the Wait button).
3. Wait for a new game to begin and try clicking the Wait button again.


Actual results:
The Wait button doesn't do anything until I move the pointer away from it and back on top of it.

Expected results:
The Wait button keeps working without needing me to move the pointer.

Does this happen every time?
Yes.

Other information:
Comment 1 Andreas Røsdal 2006-10-13 21:24:05 UTC 
Good idea. Patches for this is welcome.
Comment 2 Bruno Boaventura 2006-10-14 04:03:40 UTC 
I think this is a gtk+ bug.
In many applications it happen. Try with synaptic:

1. Open synaptic;
2. Click in the "Search" button;
3. Press ESC to close the search dialog;
4. try "Search" again.
Comment 3 Bruno Boaventura 2006-10-14 04:15:19 UTC 
this bug must have anything similar to bug #351600 , I think.
Comment 4 Bruno Boaventura 2006-10-14 04:19:13 UTC 

*** This bug has been marked as a duplicate of 56070 ***