-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Accessibility: improve support for caret configuration #206
Comments
Since the code that actually does the drawing, etc., isn't in the framework, but is in wxme, the changes would have to be there for those parts. |
I haven't had a chance to test 1c4e78e yet, but IIUC making the change at the level of |
Yes, that's true. I put it in the framework because the preferences are accessible there. But you're right, it is better at the text% level. |
Probably I should take it out before the release because of this! |
I'm not sure if this fits here, but I would love to be able to configure the type of caret used in an editor. In emacs, for example, the caret can be one of these types |
@loafofpiecrust the editor is actually implemented completely at the Racket level, not using gtk's (or other platform's) editors. Changing the drawing of the insertion caret might be challenging as it is one of the parts of the |
Related: racket/drracket#667 |
This issue was first reported on the mailing list: some people find a blinking caret either an annoyance or an accessibility issue.
Robby’s 1c4e78e was a first step toward addressing this by creating a preference (
'framework:caret-blink-disable?
) to turn blinking off.As noted, it would be nice to look at the system-level preference when available. The issue electron/electron#10668 seems to have some useful notes.
Beyond disabling blinking, it looks like all platforms support configuring the speed of caret blinking, and Windows and GTK seem to make the width and color of the caret configurable as well. Probably Racket should, too.
The text was updated successfully, but these errors were encountered: