-
Notifications
You must be signed in to change notification settings - Fork 165
a library for the german keyboard-layout capable of sending keystrokes for ALL characters #52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…oard-original Rename KeyReport to KeyReportFr and _asciimap to _asciimapFr
…ginal-lib Integrate the modifications of the 1.0.2 version of the original library
Fix naming KeyboardAzertyFr_ from the integration of 1.0.2 of the ori…
Léo Martin seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
Thanks for sharing your library @StefanL38. I will suggest that you publish it to a fork in order to make it easy for everyone in the community to use and contribute to. You can learn about that here: |
Hi per1234, nice gesture to invite me to "fork" the repo. Thank you for that. I took a look into this link https://docs.github.com/en/get-started/quickstart/fork-a-repo SAME thing there: NO explanation on how it is done in DETAIL with step by step screenshots The times when I had fun learning things through a lot of try and error are definitely OVER If the GitHUB-documenting-Team is unable to provide a STEP-BY-STEP tutorial with SCREENSHOTS how "fork" a repo Man this really makes me upset!!! NOT everybody is a NERD which has the greatest fun on trying to find out by looking up dozens of links and asking a lot of questions in forums until he/she is able to fork a repo. If you can't post a link to such a step-by-step-screenshot tutorial it stays like it is. |
Woah, no need to get so upset. Just scroll up to the top of this page and click this button. Clicking will create a copy of this repository which is owned by your github account. Because it's your copy, you will have permission to change it any way you wish. Github will know it is a fork, so when you've made changes to your copy, Github will offer you buttons to easily create a pull request to contribute your changes back to this original. Github and the git software are powerful tools. They offer a lot of features (far more than I know) and indeed it gets very complex if you dive deep into the details. But the truth is most people use only a subset of all that stuff. Like most tools, and especially very powerful ones, some learning is involved, but that knowledge & experience is (probably) well worth investing some of your time. |
Hi Paul, thank you for answering with a screenhot how to fork.
Yes and it becomes even more powerful if the documenting-Team creates a step-by-step tutorial with screenshots to show each step until a pullrequest is finished. Creating this tutorial means investing time once to enable saving time for all newcomers in the future. One purpose of Github is to serve code and knowledge to the community. So it would be just consequent to serve the knowledge on how to use Github istelf in a way that makes it efficient for newcomers to learn it. And this is with step-by-step-tutorials with screenshots. IMHO Text and Screenhots are even better than videos because it is much easier to scroll back and forth on a website than dragging back and forth the timeindicator-point of a video best regards Stefan |
So in lack of such a tutorial I did some quick tries which ended in a mess. searching the screen clicked on "commit to master-branch" or something similar reading this maybe makes it better understandable why a step-by-step-tutorial is needed |
Hi,
I wrote a library for the german keyboard-layout that is capable of sending keystrokes for ALL characters
It will send the correct keypress-codes for every character that is on a german keyboard.
Including the characters ° ^ ² ³ { '[' ']' } \ ~ @ € | ä ö ü _ Ä Ö Ü µ ß
which are special to the german keyboard-layout and all other characters where some of them have a different key on the keyboard compared to the US-keyboard-layout
functional keys like "F1", "F2" backspace, cursor up/down etc. are not included. Except the Return-Key.
Some characters have a two-byte or even three-byte representation which needs a different analysis than a simple lookup of single character.
This library has one main-function called typetext where the name is what the function does.
I'm not familiar with creating repositaries on GitHub so I just post the *.h and the *.cpp-file here in this post.
Adapting this library to other language specific keyboard-layouts just requires to change the values in the library
I have tested this library with an Seeeduino-XIAO which is a SAMD21 based microcontroller
best regards Stefan
KeyboardGER2.zip