Jan Rychter <[email protected]> writes: > The hodgepodge of methods you refer to is something I'd call a protocol > and I believe is still required to a certain extent.
The problem is with methods that are required to handle both the updating and the descent part. The only way to keep one from randomly screwing up descent, especially in the case of combination, is to take away that responsibility. > (defun update-widget-tree () > (walk-widget-tree (root-composite) #'update-children)) This is what I was suggesting. -- I write stuff at http://failex.blogspot.com/ now. But the post formatter and themes are terrible for sharing code, the primary content, so it might go away sooner or later. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
