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

Move Event wrapper and its associated traits and impls to a separate module #217

Open
luukvanderduim opened this issue Dec 16, 2024 · 1 comment · May be fixed by #218
Open

Move Event wrapper and its associated traits and impls to a separate module #217

luukvanderduim opened this issue Dec 16, 2024 · 1 comment · May be fixed by #218
Assignees

Comments

@luukvanderduim
Copy link
Collaborator

Could we move the Event wrapper plus associated traits and impls to a separate module - and gate it?

Rationale is that we have a lot of event-related traits and implementations.

  • It is tidier to have the bits pertaining the wrapper in a (eg.) 'event_wrapper' module.
  • AT users would likely use the trait, 'atspi types-only' users won't.
    Having a gate hiding/exposing the feature might help the latter user a little.
@TTWNO
Copy link
Member

TTWNO commented Dec 16, 2024

Good idea!

@TTWNO TTWNO self-assigned this Dec 16, 2024
@TTWNO TTWNO linked a pull request Dec 30, 2024 that will close this issue
19 tasks
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 a pull request may close this issue.

2 participants