search

filipst / hackerskeyboard

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

Support "shift lock" as an option instead of Caps Lock #177

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Since v1.29, the keyboard uses Caps Lock/AutoCaps instead of the old Shift Lock 
behavior. This means that on most layouts, the 5th row now shows digits instead 
of !@#$% punctuation when in this mode.

Consider adding Shift Lock as an option for users who prefer the old behavior, 
for example:

- accessibility, Shift-Arrow selections are difficult without multitouch

- get number keys by default on the French AZERTY or similar keyboards that 
currently show uppercase accented chars on the 5th row

Original issue reported on code.google.com by Klaus.We...@gmail.com on 22 Jan 2012 at 3:58

GoogleCodeExporter commented 9 years ago 
First of all: thanks for a very nice keyboard !

Second: after the last update I can't get the capital letters in the way I 
always did it: 
- either type Shift and then F (let's say)
- or simultaneously press Shift and F 

Both of the above yield lower case 'f'.

The only way I can get capital F is to press Shift twice (shows red LED) and 
then I get 'F'.

But this way is cumbersome.

I'm not sure if this behavior is related to this bug or I'm doing something 
wrong, but I just thought I would mention it here.

Original comment by dnast...@gmail.com on 24 Jan 2012 at 9:39

GoogleCodeExporter commented 9 years ago 
dnastase, that's definitely not the intended behavior. While the cause is 
probably related to the shift state handling changes, I think it's a separate 
issue - can you please add details about your device and application(s) 
affected to http://code.google.com/p/hackerskeyboard/issues/detail?id=179 ?

Original comment by Klaus.We...@gmail.com on 24 Jan 2012 at 10:27

GoogleCodeExporter commented 9 years ago 
The switch to Caps Lock/AutoCaps in 1.29 has caused the following problem for 
me:

I run Debian in a chroot and access it via Remote VNC to run X apps. Since 1.29 
the Shift doesn't work, i.e. pressing shift and then a character, or holding 
shift and pressing another character sends an unshifted character. Only turning 
on Caps Lock then sends a capital character. It doesn't affect Android apps, 
where shift works, only the X apps in Real VNC.

This has made me stay with v. 1.27 which works fine.

I therefore also ask to make this an option, so that I can use the keyboard for 
running chrooted GNU apps.

Original comment by ShiroiK...@gmail.com on 6 Mar 2012 at 4:18

GoogleCodeExporter commented 9 years ago 
ShiroiKuma - it appears that some applications don't handle Shift states in 
incoming key events correctly, please see issue 179 for that. Adding Shift Lock 
wouldn't fix your problem, but it may be possible to add a workaround.

Can you please add details to issue 179? Please include the exact application 
you're using (ideally a Market link). And you can try using the "xev" program 
on the destination system to see which key events it gets.

Original comment by Klaus.We...@gmail.com on 6 Mar 2012 at 6:43

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

It now offers a choice of Shift Lock or Caps Lock.

For Shift Lock, there's an additional option to control how it interacts with 
special keys. By default, Shift Lock only applies to regular keys (alphanumeric 
and punctuation), but it may be useful in some cases to enable it for those 
too, for example shift-arrow selection on non-multitouch devices.

Original comment by Klaus.We...@gmail.com on 6 Jul 2012 at 12:49

GoogleCodeExporter commented 9 years ago 
Issue 250 has been merged into this issue.

Original comment by Klaus.We...@gmail.com on 6 Jul 2012 at 1:30

GoogleCodeExporter commented 9 years ago 
The RC5 fix works great and restores the old behavior as a very useful option. 
I appreciate it!

Original comment by ji...@kaplowitz.org on 20 Jul 2012 at 4:57

GoogleCodeExporter commented 9 years ago 
[bulk bug update]

The changes from the 1.34rcX prerelease series are included in version 1.37 as 
published on the Play Store, 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 26 Dec 2013 at 7:12