On 08/08/2018 08:01 AM, Erich Rast wrote:
model change-->model notifies view of 'model-change-->view receives
'model-change-->view changes GUI class-->external library and OS-level
widget display handling-->GUI class event-->view notifies model of
'view-change
Is there a better solution to this problem? How do mature
notifier/subscriber frameworks deal with these kind of problems?
The most straightforward solution I've seen puts the responsibility on
the view. When the view gets a 'model-change, set a flag, change the
GUI, unset the flag. While the flag is set, the view will not send
'view-change events.
It's worked well for me, but maybe not at the level you're looking for.
Thanks,
Dave
--
You received this message because you are subscribed to the Google Groups "Racket
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
