Skip to content
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

Design events #6

Open
mwcampbell opened this issue Sep 21, 2021 · 2 comments
Open

Design events #6

mwcampbell opened this issue Sep 21, 2021 · 2 comments

Comments

@mwcampbell
Copy link
Contributor

Accessibility APIs require applications to raise events when the UI state changes, or in some cases, when UI elements are added or removed. AccessKit should imply as many of these events as possible from tree updates, to make it as easy as possible to implement accessibility correctly and completely. But some events will need to be raised directly by toolkits.

@mwcampbell
Copy link
Contributor Author

Our implementation of implicit events needs to be smart enough to only raise events for things that have actually changed. For example, an immediate-mode GUI should be able to send a whole tree per frame without spamming ATs with events for things that haven't changed.

@mwcampbell
Copy link
Contributor Author

I believe we now have a robust implementation of automatic events based on changes to the tree. I'll leave this issue open until we've figured out which events need to be explicitly provided rather than being implied from tree changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant