search

isawred2 / hackerskeyboard

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

hold 8 key will draw square bracket by default #191

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.touch and hold 8 key
2.pop-up symbols will be shown
3.square bracket is selected by default

What is the expected behavior? What do you see instead?
expected to input parenthesis like it happens with 9 key but it enters a square 
bracket instead.

What version of Hacker's Keyboard are you using? (See "Debug" section at
the bottom of the app's Settings menu.)
On what phone or tablet?
galaxy tab 10.1 GT-P7500

If applicable, does this affect the 4-row or 5-row layout, or both? Which
language(s)?
PT layout

Please provide any additional information below.
suggest swapping positions of square bracket and parenthesis on the 8 key 
pop-up symbols

Original issue reported on code.google.com by pedrocat...@gmail.com on 21 Feb 2012 at 4:47

GoogleCodeExporter commented 9 years ago 
The problem is that there are too many alt chars to fit, I'll move some of the 
rarely-used nonstandard ones such as †‡. The most-frequently used one 
should always be at the edge, swapping wouldn't work since the precise position 
depends on screen size and layout and could change unpredictably.

See revision fe6aea7ae1ff.

Original comment by Klaus.We...@gmail.com on 21 Feb 2012 at 8:31

GoogleCodeExporter commented 9 years ago 
Please try v1.30rc5 (or later) from 
http://code.google.com/p/hackerskeyboard/downloads/list and let me know if that 
works for you.

Original comment by Klaus.We...@gmail.com on 21 Feb 2012 at 8:40

GoogleCodeExporter commented 9 years ago 
[bulk bug update]

The changes from the 1.30rcX prerelease series are included in version 1.31 as 
published on Android Market, and this bug should be fixed. If it's still not 
working for you, please reopen or file a new bug. Thanks to everyone who helped 
with finding bugs and testing!

Original comment by Klaus.We...@gmail.com on 24 Feb 2012 at 6:23

GoogleCodeExporter commented 9 years ago 
Didn't work for me..
I couldn't find how to re-open this issue but I have another suggestion which 
is to move (at least) 1 alt char to another key. I attached 2 pics that may 
help you to understand.
Thanks for your effort.

Original comment by pedrocat...@gmail.com on 24 Feb 2012 at 7:06

Attachments:

GoogleCodeExporter commented 9 years ago 
Are you sure you're running the latest release? Please see the version number 
shown in Settings at the bottom, it should be 1.30rc5 or 1.31. Your screenshots 
have the mapping from the previous version.

Note that there's some delay before a new release shows up in the Market app, 
try the web version at 
https://market.android.com/details?id=org.pocketworkstation.pckeyboard if 
you're not seeing v1.31 yet.

Original comment by Klaus.We...@gmail.com on 24 Feb 2012 at 8:00

GoogleCodeExporter commented 9 years ago

Original comment by Klaus.We...@gmail.com on 24 Feb 2012 at 8:05

GoogleCodeExporter commented 9 years ago 
Solved! It's perfect..
Sorry about that, probably the latest version wasn't on market yet when I 
downloaded it.

Thanks a lot :)

Original comment by pedrocat...@gmail.com on 24 Feb 2012 at 8:10

GoogleCodeExporter commented 9 years ago

Original comment by Klaus.We...@gmail.com on 24 Feb 2012 at 8:50

GoogleCodeExporter commented 9 years ago 
I have just a small "correction" to the PT layout (probably my fault when I 
submitted it). The } character shouldn't be on the 9 key, only on the 0 key.

Original comment by j...@joaopluis.pt on 2 Mar 2012 at 11:34

GoogleCodeExporter commented 9 years ago 
Thanks! I made the "}" correction in revision 04cb6cb5e175 which is included in 
v1.32rc3: http://code.google.com/p/hackerskeyboard/downloads/list

Original comment by Klaus.We...@gmail.com on 7 Mar 2012 at 7:08

GoogleCodeExporter commented 9 years ago 
Bulk update - changing "Fixed" to "Verified" for old bugs.

(Background: I'm changing the "Fixed" status to be considered open, the next 
steps in the lifecycle will be the closed states "FixInTest" and "Verified". 
This lets me mark issues as "Fixed" in commit messages without hiding them from 
the issue tracker.)

Original comment by Klaus.We...@gmail.com on 22 Jan 2013 at 7:33

GoogleCodeExporter commented 9 years ago 
Bulk update - changing "Fixed" to "Verified" for old bugs.

Original comment by Klaus.We...@gmail.com on 22 Jan 2013 at 7:34