Phil Surette wrote: > Sorry, I said IActionListener, but it's Directs I have > problems with. With a Direct the page renders itself > before the IDirectListener gets called. Then you have to > do the dance that you told me about if you stay on > the same page.
I tend not to use Direct components, so I'm not too sure about the differences, but I think that the page is rendered after the direct listener is called, and that again the default is to stay on the same page. The difference is that the state of the page is as it was before rendering, so you don't have access to state changes performed during rendering (like processing a form submit I suppose). What do you want to happen with direct listeners, and what does happen? I should figure this out, as Direct components can be more efficient (but remember that premature optimisation is the root of all evil :-) Tom _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
