Sudoku issueshttps://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues2023-11-05T14:06:34Zhttps://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/1Add ability to play/load/save/share existing games2023-11-05T14:06:34ZBugzillaAdd ability to play/load/save/share existing games## Submitted by Todd Wilson
**[Link to original bug (#602655)](https://bugzilla.gnome.org/show_bug.cgi?id=602655)**
## Description
The current version of gnome-sudoku does not have the ability to play a game that is entered by the u...## Submitted by Todd Wilson
**[Link to original bug (#602655)](https://bugzilla.gnome.org/show_bug.cgi?id=602655)**
## Description
The current version of gnome-sudoku does not have the ability to play a game that is entered by the user, e.g., a game out of the newspaper or a book-collection of puzzles. Ideally, there would be two ways of entering an existing game:
1. A menu entry for "Enter Game", that would bring up an empty grid and allow users to add, remove, or change numbers, with a "Finish" or "Submit" button that would add the entered game to a new "Entered Games" section (along with the "New Game" and "Saved Games" sections).
2. A menu entry for "Load Game from File" that would bring up a file dialog to allow users to select a file, which would contain one or more Sudoku games in some plain-text format, say 9 lines of 9 characters each ('1' .. '9', plus '.' for an empty square), with blank lines between games. All games loaded from the file would be added to the "Entered Games" section.
The file format mentioned in 2 would also allow games to be shared among Sudoku uses, stored in annotated repositories (e.g., "Todd's Top Ten"), etc. To facilitate this, a way to export specific puzzles or generated puzzles to a file would also be useful. As an example of the successful use of such file formats, the developers might want to look at the KSokoban game:
http://hem.passagen.se/awl/ksokoban/
Thanks!
Version: git masterhttps://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/2Printing multiple sudokus should allow for double sided printing2023-11-05T14:06:34ZBugzillaPrinting multiple sudokus should allow for double sided printing## Submitted by Tiffany Antopolski
**[Link to original bug (#663930)](https://bugzilla.gnome.org/show_bug.cgi?id=663930)**
## Description
When printing multiple sudokus, it would be nice to be able to fold the resulting pages into a...## Submitted by Tiffany Antopolski
**[Link to original bug (#663930)](https://bugzilla.gnome.org/show_bug.cgi?id=663930)**
## Description
When printing multiple sudokus, it would be nice to be able to fold the resulting pages into a booklet and have the puzzles oriented correctly. This would require the puzzles to be printed on both sides of the page in landscape format instead of portrait.
This would of course make the print dialog more complex, taking into account one-side printers (which would just require printing half the amount of puzzles and then flipping the pages for the other half) and duplex printers (which at the moment require the exact same steps as one sided printers to print booklets).
So maybe being able to print in landscape format is actually the key to being able to produce an actual booklet of puzzles.
Summary:
1. Is it possible to add a choice for landscape orientation?
2. Is it possible to add a selection for duplex printers (so the user doesn't have to calculate 1/2 the puzzles and pages and then repeat the process for the second side?)
Just a thought.
Version: git masterhttps://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/3Add highscore support2023-11-05T14:06:34ZBugzillaAdd highscore support## Submitted by Robert Ancell `@robert.ancell`
**[Link to original bug (#664948)](https://bugzilla.gnome.org/show_bug.cgi?id=664948)**
## Description
Add highscore support
Version: git master## Submitted by Robert Ancell `@robert.ancell`
**[Link to original bug (#664948)](https://bugzilla.gnome.org/show_bug.cgi?id=664948)**
## Description
Add highscore support
Version: git masterhttps://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/5Tab and Ctrl+arrow focus shifting shortcuts should switch focus between grid ...2023-11-30T22:59:23ZBugzillaTab and Ctrl+arrow focus shifting shortcuts should switch focus between grid and buttons, not squares within the grid## Submitted by Michael Catanzaro `@mcatanzaro`
**[Link to original bug (#731138)](https://bugzilla.gnome.org/show_bug.cgi?id=731138)**
## Description
Every once in a while, especially when redesigning an application, it's a good id...## Submitted by Michael Catanzaro `@mcatanzaro`
**[Link to original bug (#731138)](https://bugzilla.gnome.org/show_bug.cgi?id=731138)**
## Description
Every once in a while, especially when redesigning an application, it's a good idea to pretend to develop a disability to see if users with accessibility needs will be able to use your app. Normally
I think blind Sudoku might be a bit ambitious, but we can surely handle keyboard navigation. A couple problems that I immediately see:
* I should be able to tab between all of the grids on the new game screen in order to select my difficulty level. I think you have them set to be unfocusable. I can't get to the Back button with tab, either.
* When playing a game, tab takes me to the next cell in the grid, but it really needs to take me between the grid, each button in the right bar, and each button in the header bar. This might be fixable using Gtk.Container.SetFocusChain(), or it might be more effort.
Version: git masterhttps://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/8Warning X marks are confusing2023-11-05T14:06:34ZBugzillaWarning X marks are confusing## Submitted by Allan Day `@aday`
**[Link to original bug (#734796)](https://bugzilla.gnome.org/show_bug.cgi?id=734796)**
## Description
When a cell can't be filled, a red X is shown in the cell. This has a few problems:
* It does...## Submitted by Allan Day `@aday`
**[Link to original bug (#734796)](https://bugzilla.gnome.org/show_bug.cgi?id=734796)**
## Description
When a cell can't be filled, a red X is shown in the cell. This has a few problems:
* It doesn't look like you can enter a number into the cell.
* If you put a number into the cell, you no longer see the warning.
* The X looks bad.
Changing the background colour of the cell would be a better approach for showing the warning.
Version: 3.13.xhttps://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/10Numbers move around when I resize the window2023-11-23T17:31:46ZBugzillaNumbers move around when I resize the window## Submitted by Allan Day `@aday`
**[Link to original bug (#734800)](https://bugzilla.gnome.org/show_bug.cgi?id=734800)**
## Description
As the grid changes size, the numbers jiggle around like they are doing a little dance. Resizin...## Submitted by Allan Day `@aday`
**[Link to original bug (#734800)](https://bugzilla.gnome.org/show_bug.cgi?id=734800)**
## Description
As the grid changes size, the numbers jiggle around like they are doing a little dance. Resizing should be smooth, ideally.
Version: 3.13.xhttps://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/11Show solution2018-05-22T12:25:44ZBugzillaShow solution## Submitted by Michael Catanzaro `@mcatanzaro`
Assigned to **Sahil Sareen `@sahilsareen`**
**[Link to original bug (#734893)](https://bugzilla.gnome.org/show_bug.cgi?id=734893)**
## Description
We should have a button that allows...## Submitted by Michael Catanzaro `@mcatanzaro`
Assigned to **Sahil Sareen `@sahilsareen`**
**[Link to original bug (#734893)](https://bugzilla.gnome.org/show_bug.cgi?id=734893)**
## Description
We should have a button that allows the player to give up and display the solution on the board.
Not that a Sudoku genius like myself would ever want such a button when working on a Simple puzzle. Not I. F4or others. Yup.
Version: 3.13.xhttps://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/12Restore a simplified version of Hints2021-04-18T09:28:10ZBugzillaRestore a simplified version of Hints## Submitted by Parin Porecha
**[Link to original bug (#735158)](https://bugzilla.gnome.org/show_bug.cgi?id=735158)**
## Description
I haven't used the pre vala-port Sudoku much, but it didn't exactly have an ideal Hints feature.
H...## Submitted by Parin Porecha
**[Link to original bug (#735158)](https://bugzilla.gnome.org/show_bug.cgi?id=735158)**
## Description
I haven't used the pre vala-port Sudoku much, but it didn't exactly have an ideal Hints feature.
Here is the discussion regarding Hints we had some time ago -
Should be useful enough to help players once they're already on an impossible track. "If we build it, we have to build it for people that are stuck"
"If I am stuck and I get a mismatch and so on and I press hint, it should maybe show me two numbers I filled in incorrectly. That would be useful. That's what the hint system should do instead of pointing me to the direction of the next wrong number."
Hints should preferably point out wrong things and if you've done everything right, it should point to cells you might be able to fill.
I'd like to add -
We can tie the 'Show warnings' action with Hints. If there are a large no.
of cells with warnings at a point, we should enable the warnings by ourselves
so that the user does not go on filling wrong values.
Also tie 'Show solution' option with Hints. Details - https://bugzilla.gnome.org/show_bug.cgi?id=734893#c3
Version: git masterhttps://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/15Certain forms of puzzle symmetry are less-desirable2023-11-05T14:14:49ZBugzillaCertain forms of puzzle symmetry are less-desirable## Submitted by Thomas M. Hinkle
**[Link to original bug (#749759)](https://bugzilla.gnome.org/show_bug.cgi?id=749759)**
## Description
The new gnome-sudoku comes with games that are not symmetrical. This is a regression -- prior ve...## Submitted by Thomas M. Hinkle
**[Link to original bug (#749759)](https://bugzilla.gnome.org/show_bug.cgi?id=749759)**
## Description
The new gnome-sudoku comes with games that are not symmetrical. This is a regression -- prior versions respected sudoku symmetry rules.
Version: 3.16.xhttps://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/19Lack of contrast makes it hard to play2023-11-05T14:14:50ZBugzillaLack of contrast makes it hard to play## Submitted by Gautier Pelloux-Prayer `@bagage`
**[Link to original bug (#759039)](https://bugzilla.gnome.org/show_bug.cgi?id=759039)**
## Description
I got some feedbacks from casual user (~65years old) which find the game very ha...## Submitted by Gautier Pelloux-Prayer `@bagage`
**[Link to original bug (#759039)](https://bugzilla.gnome.org/show_bug.cgi?id=759039)**
## Description
I got some feedbacks from casual user (~65years old) which find the game very hard to play because of the lack of contrast / visibility.
While application is greatly designed, the game is actually hard to play because of this lack of contrast.
I wanted to enable "highlight mode" thinking that this would colorize the selected line in whatever color, but it's actually only there to colorize in red errors.
I then enabled high contrast in accessibility, but gnome-sudoku look did not change.
Can the design be more contrast-friendly somehow (adding a color mode option for instance)? I know that it would break the sweet black&white design, so I hope someone has a better idea to deal with such problems :).
Version: 3.16.xhttps://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/31Reduce background color brightness and allow larger numbers2021-04-18T10:48:49ZGhost UserReduce background color brightness and allow larger numbersMy family enjoy the Gnome-Sudoku.
This time, I ask you the improve idea.
The Background of Sudoku table is white.
It is high brightness and make eyes ticking when play it with large monitor.
If the background color change to light gray, ...My family enjoy the Gnome-Sudoku.
This time, I ask you the improve idea.
The Background of Sudoku table is white.
It is high brightness and make eyes ticking when play it with large monitor.
If the background color change to light gray, it will better for lazy eye players.
Also, numbers font size possibly make larger.
Above information came from my grandma.
Thank you.https://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/35WIP: Keyboard Shortcuts checklist2020-02-17T14:31:12ZGhost UserWIP: Keyboard Shortcuts checklistWe are trying to provide better (F1) Help shortcut and Keyboard Shortcuts Page for users.
For that, would be awesome that all Gnome applications to have a KSP and some common shortcuts.
We believe that all GNOME applications deserve to h...We are trying to provide better (F1) Help shortcut and Keyboard Shortcuts Page for users.
For that, would be awesome that all Gnome applications to have a KSP and some common shortcuts.
We believe that all GNOME applications deserve to have a Main Menu (MM) and to have some entries on it.
* [x] Does F1 key open Help?
* [ ] Does F10 key open Main Menu?
* [x] Does MM have "Help" entry?
* [ ] Does MM have "Keyboard Shortcuts" entry?
* [ ] Does Application have KSP?
* [ ] Does "Ctrl+question" shortcut open KSP?
* [ ] Does KSP contain "F1" entry? : "F1 : Show help"
* [ ] Does KSP contain "F10" entry? : "F10 : Open menu"
* [ ] Does KSP contain "Ctrl+W" entry? : "Ctrl+W : Close window"
* [ ] Does KSP contain "Ctrl+Q" entry? : "Ctrl+Q : Quit"
* [ ] Does KSP contain "Ctrl+question" entry? : "Ctrl+? : Keyboard shortcuts"
* [ ] Ensure all shortcuts are listed in KSP.
Read more about this at the [initiative](https://gitlab.gnome.org/GNOME/Initiatives/issues/14),
@libreajans will help with the implementation of it.
Let us know if you have any questions & thoughts.
# Quick answers about my suggestions
- Why I select Ctrl+question for Keyboard Shortcuts?
Check [GTK automatic help overlay support](https://gitlab.gnome.org/GNOME/gtk/blob/master/gtk/gtkapplication.c)
- Why I select F10 for the primary menu?
It was on [standart navigations keys](https://developer.gnome.org/hig/stable/keyboard-input.html.en)
- Why I remove Ctrl+F1 shortcut
It used to work but, due to a conflict, it was removed (https://gitlab.gnome.org/GNOME/gtk/issues/626)https://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/48Number picker popover is too small when Sudoku window is large2021-04-19T15:20:36ZRichard DuivenvoordeNumber picker popover is too small when Sudoku window is largeHi, enjoying gnome-sudoku here en testing on some touch devices I have (as in trying to convince the world to use Linux on phones and tablets :-) )
- Lenovo IdeaPad MIIX D330 10.1 inch 1920X1200 touchscreen (tablet like):
tested with...Hi, enjoying gnome-sudoku here en testing on some touch devices I have (as in trying to convince the world to use Linux on phones and tablets :-) )
- Lenovo IdeaPad MIIX D330 10.1 inch 1920X1200 touchscreen (tablet like):
tested with flatpak build 4.0 master and plain Debian testing with GNOME Shell 3.38.4 (gnome-sudoku: same)
- Purism Librem 5 phone: running pureOS, gnome-sudoku: 3.30.0
On the 1920X1200 touchscreen it is the other way around: the game grid looks good, but the NumberPicker is very tiny (and for bigger hands just hard to use.
On the Librem 5 phone the screen is only shown half, but the little input widget (NumberPicker) has a nice size to use it though...
I'm aware of work going on to make the game more responsive:
https://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/41
and wondering what the status is and if I can be of any help in testing stuff with those devices.
I'll attach some screenies I made on the devices mentioned above
Librem5:
![sudokuOnLibrem5](/uploads/963d57a288018b5271a4dcdcb956fa09/sudokuOnLibrem5.png)
1920X1200 touchscreen 10" 'tablet':
![tablet](/uploads/bb8d258647191b3031d2dce299a91a97/tablet.png)https://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/49Add hint to highlight all rows and columns with the same particular number in it2021-04-18T10:46:44ZRichard DuivenvoordeAdd hint to highlight all rows and columns with the same particular number in itNot sure for others here, but I'm a lousy sudoku player. And even the 'easy' ones take me >30m ...
On an ipad version of a sudoku app there was an optional 'hint' showing: when you click on a cell (say 5 in it): all rows and cells conta...Not sure for others here, but I'm a lousy sudoku player. And even the 'easy' ones take me >30m ...
On an ipad version of a sudoku app there was an optional 'hint' showing: when you click on a cell (say 5 in it): all rows and cells containing a 5 show up: making it for beginners more easy to 'find' the open spot or see if 5 is a number to focus on.
Is that easy to implement?
I'm also aware of an old 'hint' issue:
https://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/12
but that is more about showing one or more 'solutions'...
One thing thing that bugs me too: sometimes after some (apparent) wrong choices, you are presented with with 'red numbers' but it is not clear how to solve this (other then 'play again'). To me it would be nice if there would be some option: 'fix my faults' as in: ok either go back to where I took the wrong turn, OR remove all my faults so at least I can go on without a full restart..https://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/51[Feature] enable cell background color setting2022-01-12T15:00:51ZMarko Minđek[Feature] enable cell background color settingHi,
as a sudoku player I find it really useful and user-friendly being able to 'highlight' some cells. It really helps to deal with X-wing and Swordfish patterns whose are a must at 'very hard'. I think it could be implemented as an ext...Hi,
as a sudoku player I find it really useful and user-friendly being able to 'highlight' some cells. It really helps to deal with X-wing and Swordfish patterns whose are a must at 'very hard'. I think it could be implemented as an extension to earmarks, where colors would be placed right under or next to numbers.https://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/62Feature: Automatically pause when device is locked2023-04-26T20:10:55ZAlbin LarssonFeature: Automatically pause when device is lockedThe current game should pause if the screen becomes locked. This would be especially useful on mobile.The current game should pause if the screen becomes locked. This would be especially useful on mobile.https://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/83Can't select multiple cells for pencilmarking2023-11-21T19:15:39ZGreg CarvinCan't select multiple cells for pencilmarkingIt will only allow the selection of individual cells for the tiny number notations.It will only allow the selection of individual cells for the tiny number notations.https://gitlab.gnome.org/GNOME/gnome-sudoku/-/issues/94Several warnings saying "Allocating size to GtkLabel 0x3a5a700 without callin...2024-03-17T09:42:45ZAutomeris naranjaSeveral warnings saying "Allocating size to GtkLabel 0x3a5a700 without calling gtk_widget_measure" appear in the CLI## Affected version
git (master)
## Steps to reproduce
1. Open Sudoku from a CLI
1. Start a game
## Seen behavior
Several warnings telling "Allocating size to GtkLabel 0x3a5a700 without calling gtk_widget_measure" will appear in the...## Affected version
git (master)
## Steps to reproduce
1. Open Sudoku from a CLI
1. Start a game
## Seen behavior
Several warnings telling "Allocating size to GtkLabel 0x3a5a700 without calling gtk_widget_measure" will appear in the CLI, over and over:
```
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.828: Allocating size to GtkLabel 0x36cca90 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.829: Allocating size to GtkLabel 0x370a030 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.829: Allocating size to GtkLabel 0x376f490 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.829: Allocating size to GtkLabel 0x37bb510 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.829: Allocating size to GtkLabel 0x372b8e0 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.829: Allocating size to GtkLabel 0x378fe30 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.829: Allocating size to GtkLabel 0x37e6d10 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.829: Allocating size to GtkLabel 0x37415a0 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.829: Allocating size to GtkLabel 0x379abf0 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.829: Allocating size to GtkLabel 0x37b0760 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.830: Allocating size to GtkLabel 0x3881220 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.830: Allocating size to GtkLabel 0x3896ed0 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.830: Allocating size to GtkLabel 0x38fdf10 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.830: Allocating size to GtkLabel 0x3855910 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.830: Allocating size to GtkLabel 0x38aca50 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.831: Allocating size to GtkLabel 0x3908cc0 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.831: Allocating size to GtkLabel 0x38607f0 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.831: Allocating size to GtkLabel 0x38c2720 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.831: Allocating size to GtkLabel 0x38dd400 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.831: Allocating size to GtkLabel 0x39ac3d0 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.831: Allocating size to GtkLabel 0x39c2160 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.831: Allocating size to GtkLabel 0x3a19170 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.831: Allocating size to GtkLabel 0x3975c30 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.831: Allocating size to GtkLabel 0x39ccf10 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.831: Allocating size to GtkLabel 0x3a2efb0 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.831: Allocating size to GtkLabel 0x39a1610 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.831: Allocating size to GtkLabel 0x39eda80 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.831: Allocating size to GtkLabel 0x3a4f940 without calling gtk_widget_measure(). How does the code know the size to allocate?
(gnome-sudoku:20112): Gtk-WARNING **: 20:07:55.831: Allocating size to GtkLabel 0x3a5a700 without calling gtk_widget_measure(). How does the code know the size to allocate?
```