RE: [Anthem.NET-users] big problem with Anthem

[Andy M. <am...@st...>]

Good point. We *want* UpdateAfterCallBack to reset to false, unless
AutoUpdateAfterCallBack is set.

 

I was overzealous. That property should not be in ViewState.

 

Andy Miller

 

  _____  

From: ant...@li...
[mailto:ant...@li...] On Behalf Of Manu
Temmerman-Uyttenbroeck
Sent: Sunday, March 26, 2006 8:03 PM
To: Andy Miller; anthem user
Subject: Re: [Anthem.NET-users] big problem with Anthem

 

.other stuff.


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 viewstate? 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.