Replies: 2 comments 3 replies
-
Yeah, I see a problem here. Some listeners want not only to be notified on a change but also to use the new value. |
Beta Was this translation helpful? Give feedback.
2 replies
-
Forget about. It make no sense |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi again Greg.
This is about the issue I had with listeners. I was thinking that restricting capsules rebuilds to be triggered inside a listener is a problem in POV. EG you can call an abstract method inside a listener and you don't know whether it will try to change any capsule or not.
I quickly thought on a possible workaround and I want your opinion: what about modify or create another CapsuleContainer listen function that has as parameter a set of capsules and a callback function, then wrapping the callback with a closure that uses all that capsules and call the callback with a future.delayed
Beta Was this translation helpful? Give feedback.
All reactions