Skip to content

Conversation

ids1024
Copy link
Member

@ids1024 ids1024 commented May 14, 2025

With the rough incomplete version here, upstream Orca and at-spi2-core are able get key input from the server. More needs to be done to handle grabs correctly, restrict access to the protocol, and make sure all the details work correctly.

@ids1024
Copy link
Member Author

ids1024 commented Jun 20, 2025

To restrict interfaces to only certain well-known names, I've added NameOwners, similar to something Mutter and Gnome Shell have. (Still need to actually use it properly, and test.) A little arcane async stuff, but not too complicated, and I think should work well.

I guess we also need to remove grabs for clients that are disconnected...

@ids1024 ids1024 force-pushed the a11y-keyboard-monitor_noble branch 2 times, most recently from e2c33ed to fa3302f Compare August 1, 2025 21:09
@ids1024 ids1024 force-pushed the a11y-keyboard-monitor_noble branch from fa3302f to a270e51 Compare August 13, 2025 18:56
If we need to use simple async code in a few places, a single executor
may be better than having several threads blocking on async code.

This should probably use the calloop executor, but that's had issues in
cosmic-workspaces, though that may not apply here.
The `zbus` blocking API just wraps the async API with `block_on`, so we
may as well use our own executor.
Allows us to restrict a DBus protocol to only the owners of specific
dbus names.
unused code

url

unichar

store set grabs

KeyGrab

key grabs

virtual_mods

Fix deadlock

fmt
@ids1024 ids1024 force-pushed the a11y-keyboard-monitor_noble branch from a270e51 to 956a8a4 Compare October 6, 2025 21:48
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

Successfully merging this pull request may close these issues.

1 participant