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.

Sign up for GitHub

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

Jump to bottom

Determine best approach for Undo/Redo support #192

Open
ecton opened this issue Oct 20, 2024 · 0 comments
Open

Determine best approach for Undo/Redo support #192

ecton opened this issue Oct 20, 2024 · 0 comments

Comments

@ecton
Copy link
Member

ecton commented Oct 20, 2024

No description provided.

@ecton ecton mentioned this issue Oct 20, 2024
Open
7 tasks
ecton added a commit that referenced this issue Jan 13, 2025
@ecton
Initial Channel implementation
74abb13 
This new type isn't integrated in with any of the existing types yet.
This is a step towards what is needed to implement the command pattern,
which I think is the best approach for #192.

I think we might need a Broadcast channel type as well to allow a
channel type where multiple callbacks can be associated rather than a
single, but it will require a Clone bound or extra allocations and the
current implementation doesn't need either.
@ecton ecton mentioned this issue Jan 13, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ecton