Bug 74153

Summary: gnomine - hard to see which squares are pressed
Product: [Retired] Red Hat Linux Reporter: James Turner <jamesfturner>
Component: redhat-artworkAssignee: Havoc Pennington <hp>
Status: CLOSED UPSTREAM QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: alexl, garrett, srevivo
Target Milestone: ---Keywords: MoveUpstream, Triaged
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-01-12 23:30:32 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description James Turner 2002-09-16 20:31:04 EDT
From Bugzilla Helper: 
User-Agent: Mozilla/5.0 (compatible; Konqueror/3; Linux) 
 
Description of problem: 
In gnomine with the default GNOME/Gtk+ theme, it's almost impossible to tell 
which squares are/arn't pressed down. They look almost identical. 
 
Version-Release number of selected component (if applicable): 
gnome-games-2.0.3-2 
 
How reproducible: 
Always 
 
Steps to Reproduce: 
1. Load gnomine on a fresh Null/GNOME2 installation. 
2. Try to play it. 
	 
 
Actual Results:  You develop a squint trying to tell the difference between 
squares that are/arn't pressed down. 
 
Expected Results:  You can easily tell which squares are pressed. They should 
be shaded so as to appear pushed in; remaining squares should be shaded so 
that they appear raised up from the game board. 
 
Additional info: 
 
None
Comment 1 Havoc Pennington 2003-01-08 17:09:53 EST
Looks to me like gnomine should use the GTK button drawing 
stuff instead of whatever it uses to draw the buttons. Maybe pass
in "button" detail or just use buttons.
(In the meantime the big blue "1" etc. should compensate)
Comment 2 Havoc Pennington 2003-01-12 23:30:32 EST
Moved to http://bugzilla.gnome.org/show_bug.cgi?id=103343
Comment 3 Callum McKenzie 2003-05-12 05:54:42 EDT
This has now been fixed upstream.