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
The Simplified OptiKey #accessibility #860
Comments
@alexandre-mbm |
Yes, it can be... in tests: "blank buttons with actions, and no animations", but I looked for this on code already, a rebinding of objects, and I didn't see it. |
Hi @alexandre-mbm if I've understood correctly, you are trying to add a YesNo key and a Calibrate key in the bottom row. I think they are being replaced by empty keys in this block of code:
I imagine this will be fixed by changing the first line to
Alternatively, you could comment out this line so no blank keys are added at all:
|
Hello, guys!
I am working an accessiblity approach for my father, a ALS person in advanced state (issue #855). Initially is an simplified OptiKey with two screens only. The first "point of use" is a dynamic keyboard maximised (ref.: #857) always.
Another screen is the dynamic keyboards selector as a "final point" for the user. From it the user can only "back" to maximised dynamic keyboards.
See the changes for this workaround here: v3.2.3...ENE:OptiKey:alberto
The problem
The initial change on "selector" is working as in this commit and shown in the image above. BUT the changes bellows are buggy:
Mentions: @kmcnaught, @AmaralVini, @alandbm
The text was updated successfully, but these errors were encountered: