Placement of number count is distracting

[GoogleCodeExporter]

While the number count is useful, the current implementation is too confusing.

Instead of putting the count in parentheses next to the number, like this:

   5(6)

how about putting it in the lower right corner of the button, with or
without parentheses, like this:

   5
      6

You might even consider using the same color blue for the count font that
you use for the button when the count is maxed out.

Original issue reported on code.google.com by greg.tho...@earthlink.net on 1 May 2010 at 4:52

[GoogleCodeExporter]

This gets my vote too - but perhaps use a different colour for the "used" count 
- and the used count should be on all numbers including the selected number.

Original comment by rednectar.chris on 20 Jun 2010 at 4:14

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Maybe this issue could be resolved in a different way.

Frankly, I am not so interested in how many 4s, 8s, or whatever are left open 
on the board. I am more interested in whether a number appears in every 9x9 
square, i.e. when there are nine of a number on the board. If I know there are 
some missing, I can easily determine how many and where they are by scanning 
the board. 

Currently, in order to determine this, I must make the extra step of pretending 
to fill in another cell to see whether the number I am interested is filled in 
blue on the pop-up keyboard.

What if you created a list of nine mini-buttons, white outlined with black 
background, to the right of the elapsed time counter. Then, when there are nine 
of any number on the board, you could change the corresponding button to blue 
(same as you do on the data entry pop-up).

I doubt this would be too difficult to implement - it is just a matter of 
displaying currently tracked information in a different, more useful way.

If you wanted to get tricky, you could make the buttons active so that when one 
of them is selected, it would show the locations of the corresponding number on 
the board for a few seconds. If the buttons are too small, however, it might be 
difficult to implement this using the touch screen.

Original comment by greg.tho...@earthlink.net on 11 Aug 2010 at 6:37

• Added labels: ****
• Removed labels: ****