From: Manu Temmerman-U. <man...@gm...> - 2006-03-27 07:18:53
|
Alright! Great! On 3/27/06, Jon Aseltine <Jon...@ti...> wrote: > > Hi, > > Sorry, my mail server seems to be a bit too draconian. I will try to fix > it when I have time. > > Yes, I will do it. Probably not this week (but you never know). And yes, > UpdateAfterCallBack should not be in the viewstate. I will also add > anthem:Literal while I am at it. > > > Jon > > > Manu Temmerman-Uyttenbroeck wrote: > > Hmmm Jon, again I got the same msg. So again to the list... > > So Jon I can count on it that you will do it? That would be nice.... > Andy I just had a look at the sample fix you posted in the patches. Could > it be that it's better *not* to put the UpdateAfterCallBack into viewstat= e? > If that property is in viestate, does it then mean that if once I put it = to > true somewhere in my code, that it will be true *forever*? > > That's not how it should be I think. UpdateAfterCallBack should be only > valid for 1 callback cycle. After it, it should be false again. > Correct? > > Manu. > > > > -- > Jonathan Aseltine > Software Engineer > TicketNetwork.com > 27 Terrace Drive > Vernon, CT 06066 > Ph: 860.870.3400 x278 > Fax: 860.870.8744 > Email: Jon...@Ti... <jon...@Ti...> > > *TicketNetwork=99 > **Think outside the box office. > *www.TicketNetwork.com > > |