Alt Gr and Shift keys

Asked by Piotr Mackowiak on 2011-10-19

Is it possible to set "sticky" function of <Alt Gr> and <Shift> keys to be active for only one key depressing? I want the keyboard to back to "normal" layout/state after single depressing of other keys. I want to turn off possibility to have <Alt Gr> and <Shift> do stay pemanenly in "depressed" state. Is it possible?

Question information

Language:
English Edit question
Status:
Answered
For:
Onboard Edit question
Assignee:
No assignee Edit question
Last query:
2011-11-04
Last reply:
2011-11-04
Launchpad Janitor (janitor) said : #1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Francesco Fumanti (frafu) said : #2

Hi,

Thanks for your interest in Onboard.

The modifiers in Onboard can be activated in two ways:

1) By performing a single click on a modifier (for example the Shift key), the modifier gets activated until the user clicks on a non-modifier key. By the click on a non-modifier key, the modifier gets automatically released.

2) By performing a double click on the modifier key, the modifier gets activated in a sticky way. In order to release it again, you have to perform an additional click on the modifier key.

If a modifier that you activated by a single click is not automatically released by a click on a non-modifier key, you probably have found a bug. Could you in this case give us more information about the problem.

Cheers

Piotr Mackowiak (mackowiakp) said : #3

The problem is using onboard in kiosk application. So if previous user lives keyboard in "sticky" state, the next user does not know why keyboard works in non proper way. It is important because of special characters of my language are avaliable by depresing <Alt Gr> key and "ordinary key (Polish language). Also shutting down onboard process (by killing it according to kiosk activity needs) lives even physical keyboard in "sticky" state after running onboard again. So some like time-out of "sticky" state is necesary and resetting onboard to un-sticky state after shut-downd onboard and start onboard in non-sticky state during start onboard again.
The next problem is that if onboard proces is running, screen saver can not triger its action (strange but it is true). It esspecialy important for kiosk application because screen saver is a slide-show with commercials.

Francesco Fumanti (frafu) said : #4

I just saw that the Onboard coder already addressed the issues here; so at least the sticky modifier problem should be fixed.
https://bugs.launchpad.net/onboard/+bug/879944

As you already have contact with the Onboard coder through the bug thread that I just indicated, I will mark this question as closed.

Cheers

Can you help with this problem?

Provide an answer of your own, or ask Piotr Mackowiak for more information if necessary.

To post a message you must log in.