Ok. No worries/need to rush on my account. I just was trying to figure out if the problem was on my end or not. Now that I know to wait, happy to do so! :)
Thank you so much for your hard work. I know I speak for a lot of people when I say that your work is appreciated. -----Original Message----- From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] Sent: Thu 3/8/2007 8:56 PM To: Tapestry users Subject: Re: Autocompleter in 4.1.2 I'm not ignoring this, just ran out of steam last night and was too busy with $$ work to get to it today.. Andy pointed out the problem in a previous thread - AbstractWidget. I can't figure out what I was doing / thinking at the time but the whole point of ResponseBuilder was to eliminate those kinds of if(condition) checks.....Ehh..So just bad design on my part... I've figured out why I did it originally and have taken steps to fix it properly in the actual culprit but will still need to tread carefully as these changes are "delicate" wrt widgets and such ... So...Almost done, I'm pretty sure a fix will be out tomorrow but I don't know when. On 3/8/07, Leffel, Daniel <[EMAIL PROTECTED]> wrote: > Jesse, > This problem has to do with the same problem I emailed about a few days > ago that components nested within a dialog aren't updating. > > I finally boiled this down to this: > If the autocompleter is not nested within the dialog, it works > perfectly. Here is the firebug output: > filter US > json true > updateParts parentRegionChooser > <snipped> -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
