-
Notifications
You must be signed in to change notification settings - Fork 23
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
Grid settings - keyboard board #471
Comments
The current automatic detection to detect if it's a keyboard letter which should be printed big is:
There is no decision for a whole grid anymore, but only for single elements. So in which situation you think we need to explicitely specify that an element is a keyboard letter?! I think maybe the more probable use case is to specify that something is not a keyboard letter, e.g. on a page with many words and a single letter word like "I" or "a" which is not a keyboard letter and should not be printed bigger than the other elements. |
Maybe we have not explained well. Let's try to explain some cases in which what we are talking about would be necessary. Many teachers create syllabic or phonetic keyboards or keyboards in which they mix letters with syllables or keyboards with visual aids (images that begin, for example, with the letter on the keyboard), for example as a way for children to learn to write written words. These are adapted keyboards that do not fit into what a conventional keyboard is. In these cases, Asterics does not automatically detect them as keyboards and when pressing the letters on the keyboard it leaves blank spaces which prevents complete words from being written. Taking advantage of the fact that there is now a new keyboard settings window, it could be interesting to have an option to manually force that board to work as a keyboard and, therefore, behave as such when writing. It would be up to each person to mark it. It could even be auto-marked on those boards that the system already detects as keyboards automatically. It would be a board-level adjustment. It doesn't make sense to do it letter by letter because of the work it would entail. However, for visualization problems like the ones you mention it could make sense although our request was not in that line of visualization. |
Add an option in grid setting to set this board as a keyboard although don't accomplish with all the conditions to be a keyboard with actual automatic detection. Sometimes professionals create custom keyboards that are not detected by system. With the new grid settings could be possible to add an option to force to be a keyboard board.
The text was updated successfully, but these errors were encountered: