On Feb 5, 3:26 am, "Leslie P. Polzer" <[email protected]> wrote: > Scott L. Burson wrote: > > Hi, > > > Is it intentional that UPDATE-CHILDREN is not called on an AJAX > > request? > > I don't know. I've never ran into problems with it so far, > but I tend to not use that functionality anyway so that > might be the simple reason behind it.
Oh wait, I see what's going on. The problem is a little different from what I thought. I've defined an UPDATE-CHILDREN method for one of my own classes. There is code to call UPDATE-WIDGET-TREE (which calls UPDATE-CHILDREN on every widget in the tree) on an AJAX request, but it's in (SETF WIDGET-CHILDREN), and frankly, it's a hack. The worst part is that it's explicitly conditionalized on the presence of a selector widget in the subtree, which means it doesn't work for other kinds of widgets that might have UPDATE-CHILDREN methods. But also, this doesn't seem to me like the right place to be doing this; there could easily be multiple calls to (SETF WIDGET-CHILDREN) in a request, whereupon this is making redundant calls to UPDATE-WIDGET- TREE, which can be arbitrarily expensive. I'm going to see if I can find a better way. -- Scott -- 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.
