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 313130 - Pause and Unpause (continue) should be only one menu or button
Pause and Unpause (continue) should be only one menu or button
Status: RESOLVED OBSOLETE
Product: atomix
Classification: Other
Component: atomix
1.2.x
Other All
: Normal normal
: ---
Assigned To: Atomix Maintainer(s)
Atomix Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2005-08-10 15:43 UTC by Alan Horkan
Modified: 2018-02-23 16:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch to mimic Pause/Continue behavior of reqular gnome-games application (4.37 KB, patch)
2007-08-16 18:21 UTC, Yuriy Syrota
none Details | Review

Description Alan Horkan 2005-08-10 15:43:34 UTC
Rather than having two seperate and mutually exlcusive menu items for Pause game
and Continue game (aka Unpause) it would be better to have one single menu item.
Comment 1 Alan Horkan 2006-11-08 14:18:26 UTC
This request was based on the HIG recommendations for media player buttons
http://developer.gnome.org/projects/gup/hig/2.0/toolbars.html#toolbars-media
(That guideline was informed by the fact that having a button which changes label based on state is not something screen readers can predict as they can only read the first label.)  

I realise having two menu items allows for two labels but a checkbox menu item with one label seems more consistent with what other Gnome Games do.  
Comment 2 Yuriy Syrota 2007-08-16 18:21:10 UTC
Created attachment 93802 [details] [review]
Patch to mimic Pause/Continue behavior of reqular gnome-games application
Comment 3 GNOME Infrastructure Team 2018-02-23 16:04:30 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gcab/issues/2.