Virtual keyboard cleanup for 1.8

[GoogleCodeExporter]

Some things will help our new virtual keyboard to be easier to use:

1) Allow the user to type "`" (combiner). Shouldn't be too difficult, since 
it's treated as a normal key press.

2) Allow the user to type "shift" and have it "lock" the shift key down for the 
next letter. This is standard behavior in virtual keyboards, and it will allow 
the user to use (mostly) the mouse for typing. (I can't add Backspace or Enter 
right now.)

3) Display the keyboard's encoding, perhaps in the upper-right, horizontal from 
the "title". This way, people won't be confused that they're typing in myWin 
2.2. (Later, we can allow them to click on it to change the help keyboard). 

These are simple enough to implement for 1.8.

Original issue reported on code.google.com by seth.h...@gmail.com on 25 Aug 2010 at 10:37

• Blocking: #89

[GoogleCodeExporter]

 1) Done. Also enabled "backspace"  ...might as well test it before 1.8. (But definitely no on Enter/Space).

 2) Done. Locking works, and interacts just fine with regular key-prsses. In general, clicking Shift will "lock" only for the next key press. 

 3) To do this properly requires that I select a good layout (small font? Maybe?) and then ensure this is updated every time the keyboard is re-generated. I can probably put off the second task until we allow encoding changes. Will work on layout later.

Original comment by seth.h...@gmail.com on 27 Aug 2010 at 8:07

• Changed state: InProgress

[GoogleCodeExporter]

3) Fixed. The keyboard won't display anything while minimized, which makes 
sense. 

All are fixed; will generate a nightly.

Original comment by seth.h...@gmail.com on 27 Aug 2010 at 8:51

• Changed state: Fixed

Attachments:

• helpkbd_enc.png