Proof-of-concept to display unicode via the UC macro#446
Open
guidoism wants to merge 1 commit into
Open
Conversation
Collaborator
|
@guidoism can you upload a json file with an example? Thanks |
Author
|
Added file — See Layers 7 and 8. |
Collaborator
|
So it's pretty cool. the question is how to integrate this. We could maybe add a new tab for unicode, but the bigger problem is I think we need API support in the form of data driven QMK that @skullydazed is working on. |
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current behavior displays an Any key with the text from the UC macro. This commit changes it to display the unicode character. The intent is to have a better experience if you are using the configurator just to view and tweak your keyboard.
There are several issues:
Again, this is a proof-of-concept. It seems like a simple enough change to merge but I don't want to add anything that would be confusing to future coders due to the half-assed nature of my code. Please let me know if there's anything I can do, other than adding full unicode support, which I don't think I'd be able to actually accomplish.
@yanfali