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 560069 - Would like a way to be able to specify the board size at runtime.
Would like a way to be able to specify the board size at runtime.
Status: RESOLVED DUPLICATE of bug 543387
Product: gnome-games-superseded
Classification: Deprecated
Component: iagno
2.24.x
Other All
: Normal enhancement
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-09 21:16 UTC by Kyle Reed
Modified: 2009-12-08 07:07 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Kyle Reed 2008-11-09 21:16:10 UTC 
I have a sub-notebook with a 1024x600 screen.  I'd like to be able to play iagno but I can't because it seems to have been created for 768 or greater screen height.  After looking at the code, it looks like the screen size is hard coded in gnothello.h.  This would be a non-trivial fix but I'd really like to have either:
A) The board size is determined from examining the dimensions of the pieces pixmap.  This would allow the most flexibility because existing boards would work and new smaller boards could be added.

B) Use a GConf setting to set board size.  This could be set to the default for the normal boards and could be changed for added boards.  This isn't the best answer but would probably be easier.

Disclaimer: I'm not a Gnome dev so I don't know the difficulty of getting things out of GConf.
Comment 1 Robert Ancell 2009-12-08 07:07:00 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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