fgKeyBoard

[Filippo]

Hi,

with this library you can create a Virtual-KeyBoard.

.NET Compact Framework 2.0 or higher is required.

Questions, comments or suggestions are welcome.
Please report all errors (if it was found).


Version 1.001 ; with 3 languages

Version 1.002 ; with new Methods and Property
Methods:
1. DefaultLanguage

Property:
1. Enabled
2. Visible


Version 1.003 ; with auto Landscape-orientation


Version 1.012 ;
1) auto-orientation away. Fundamental problem with the Form-Resize function.
2) The method "DefaultLanguage" is now a property.
3) The Enter-Key is now also available.
4) The German and Italian letters are accessible via a context menu.


Ciao,
Filippo

[wm.chatman]

Hi Filippo

very nice source thanks for sharing your knowledge!

merry Xmas

Best regards

William

[derez]

Very nice Filippo , Thank you.

Can you enable selection of the keys (to allocate other keys then those that are defined ) ?

[Filippo]

Can you enable selection of the keys (to allocate other keys then those that are defined ) ?

currently not, but in future would provide for different language.

[Ariel_Z]

Looks amazing!! Absolutely the thing we are missing. I was playing with it a bit and it looks excellent.
2 things went on my mind - if you wish and have the time of course: the ability to adjust the characters (different language) and to show the tapped one (above the touching finger), I guess it would help others a lot to be able to adjust their languages... But don't get me wrong - really good work!

[Filippo]

Hi,

I would like to customize the keyboard for different languages.
Currently, the keyboard is only in german.
For which language the keyboard should be created?
Can someone explain what characters are also on the keyboard?


Thank you for assisting
Filippo

[Ariel_Z]

I guess the best thing is to allow loading the characters from a text file, something like (if fgKey is a fgKeyboard object):

fgKey.LoadCharSet (Filename)
and the file should contain a mapping in text. You can separate the different layouts with section tags in [], and then the lines preceded with --, and then the chars separated with |. It's readable and easy to parse, and way simpler than XML. Something like:

[smallChar]
--FirstLine
q|w|e|r|t|y|u|i|o|p
--SecondLine
a|s|d|f|g|h|j|k|l
.....
.....

[Capitals]
--FirstLine
Q|W|E|R|T|Y|U|I|O|P
.....
.....

[Symbol]
--FirstLine
Q|W|E|R|T|Y|U|I|O|P

[Nums]
--FirstLine
1|2|3
--SecondLine
4|5|6
...



and so on. This way users will quickly create the different layout they use in each languages and you will not have to bother.


You may also consider another key not currently implemented is the "Change language" key - it requires one extra set of characters to be implemented but is essential for people working in foreign languages and need to switch to English from time to time. I've attached a sample from the iPhone keyboard - the key to the left of [space] is what I meant.

I'd be happy to assist. It's a great work anyway and thank you very much!

[Filippo]

The function "Change language" to add is not a problem.
My problem is that letters must be prepared for the different languages?

For example, for Germany, I have:
LowerCase: qwertzuiopasdfghjklüyxcvbnmöäß,.-
UpperCase: QWERTZUIOPASDFGHJKLÜYXCVBNMÖÄ?;:_
Symbol: !"§$%&/()=?`*°'^©~²³{[]}<|>\Ø£€@#
Number: 789/456*123+0,--

[Ariel_Z]

Originally Posted by Filippo

My problem is that letters must be prepared for the different languages?

Do you mean that you have the bitmaps prepared for all keys? Or you draw the character on an empty bitmap of a key?

[Filippo]

Do you mean that you have the bitmaps prepared for all keys? Or you draw the character on an empty bitmap of a key?

I draw the characters always at runtime on an empty bitmap of a key.

The problem is that you must send with the function "Sendkeys" certain characters in different way.