search

raizal / shortyz

Automatically exported from code.google.com/p/shortyz
0 stars 0 forks source link

Problems with native / BT keyboard + tablet-sized screen #36

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Use the native onscreen keyboard or an external bluetooth keyboard; use a 
layout on which the list-of-clues is shown (e.g., tablet in landscape mode); 
turn on "space changes direction" preference
2. Enter a puzzle
3. Repeatedly press space

What is the expected output? What do you see instead?
Toggles between 1-across and 1-down

What version of the product are you using? On what operating system?
Shortyz 3.2.1 / hg changeset 208 on default branch
nexus 7 / jelly bean 4.1.2
motorola bluetooth keyboard

Please provide any additional information below.
This is just idle speculation, but it seems like each keystroke may be seen by 
both the puzzle area and by the clue lists.  This problem or a similar also 
affects how arrow keys work (again affecting the 'native' keyboard when it is 
the 'hacker's keyboard' which includes arrow keys).  However even with this in 
mind I've failed to produce a patch which improves the situation.

Original issue reported on code.google.com by jep...@gmail.com on 16 Oct 2012 at 7:30

GoogleCodeExporter commented 9 years ago 
The attached file improves things with my bluetooth keyboard and in the 
emulator with real keyboard and android native onscreen keyboard.

The core idea is to stop 'normal' traversal by making the 
up/down/left/right/next view after the crossword view be .. the crossword 
itself.  This stops the activation of the clue lists that was leading to 
trouble.

The treatment of TAB as SEARCH is possibly a separate issue, but Nexus 7 has 
tab in its onscreen keyboard but no (soft or hard) search button, so it's very 
handy.  The same goes for using a physical keyboard; tab is sensible for this 
function and a physical search button may be absent or placed oddly.

Finally, the patch also changes the behavior of ENTER to be more like SEARCH 
when it is 'go to next clue'.  It's also debatable...

Original comment by jep...@gmail.com on 17 Oct 2012 at 5:00

Attachments: