On Feb 3, 3:36 am, "Leslie P. Polzer" <[email protected]> wrote: > You're calling a flow-modifying function from a rendering function.
If I'm reading correctly, then what's happening is the lambda is being evaluated as an argument to the make-navigation function, the result of which isn't renderable, but the side effects are to replace the current widget, but only after the current widget has already been rendered, right? That would explain why navigating back to the "/" path shows the dialog. I suppose then that the reason anything at "/ info" is displayed at all is because of the behavior of the functions associated with the selector-mixin class (i.e, the function selector- mixin-canonicalize-pane) allows the navigation widget to be re- rendered with "info" as the name and nil as the widget (...or something like that. I'm still not clear on exactly what happens to the evaluated result of the lambda). Am I close? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
