Closed GoogleCodeExporter closed 8 years ago
This issue was closed by revision r199.
Original comment by paul.din...@gmail.com
on 2 Apr 2013 at 9:45
Has been implemented in version 1.96.
Tips for testing: During file conversion it is determined whether the user
already has solved at least two games. If so, the user is treated as a user who
already knows the rules of MathDoku and the tip will not be displayed.
Original comment by paul.din...@gmail.com
on 2 Apr 2013 at 9:48
Tested on Revision 224:
See general comment about the "Do not show again" checkbox on Issue 90.
My observations:
1) I managed to bring this dialog up twice when playing the game by:
a) Make sure maybe mode is on.
b) In a cell where I wanted to mark "1" & "3", I pressed both keys in quick succession. The tip dialog appeared twice i.e. I had to close both to get back to the board.
2) The example says "The entire grid below is therefore valid", but actually
shows the same order of values (low->high). To make the point, would it not be
better to show an example with the values both ways round e.g. "2/=4,2" &
"3/=1,3" or even more extreme: "3/=1,3" & "3/=3,1"?
3) The dialog does not fit on the screen on most devices without scrolling (see
screenshot from Nexus 4). Would it be worth reducing the size of the graphic so
that the tip can fit on a screen without having to scroll?
Original comment by em...@srlee.com
on 8 Apr 2013 at 5:16
Attachments:
Resolved in r227:
1) Multiple tip dialogs are now prevented
2) Image and text have been changed.
3) Image size has been reduced. Did not test on xhpdi screens as my emulators
keep crashing.
Original comment by paul.din...@gmail.com
on 9 Apr 2013 at 9:46
Original comment by paul.din...@gmail.com
on 9 Apr 2013 at 9:53
Tested Revision 227:
1) Only a single dialog is shown, regardless of how quickly the numbers are
pressed
2) Personally, I think the example is much clearer and will hopefully get the
point across.
3) The new screenshots are much clearer (both size and newspaper theme)
Original comment by em...@srlee.com
on 9 Apr 2013 at 5:39
Original issue reported on code.google.com by
paul.din...@gmail.com
on 1 Apr 2013 at 1:00