Surprised at callback/livecallback on multiselect

Just an FYI for those playing in the area.

 From a bit of research into liveCallback it appeared that the callback
block would not get called. The tests also seem to indicate this.

However if the form containing the multiselect gets submitted then the
callback fires even though the liveCallback has already fired. I guess
it makes sense but it wasn't what I expected.


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

But what did you expect exactly?


On 25 Feb 2008, at 08:34 , Steve Aldred wrote:

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Michel Bany wrote:
> But what did you expect exactly?

For someone exploring things the comments in WAAsyncLiveTest
#renderButtonOn: and #renderAnchorOn:  imply the callback block won't be
invoked. So being influenced by those comments I was surprised when the
form was submitted they were invoked after the liveCallback had already
fired.

As I said what it does probably makes sense. I was just creating an
informational post for those trying to learn Seaside.

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

I'm confused because in both #renderAnchorOn: and #renderButtonOn:  
the method comments are right and the callback block is never evaluated.

On the other hand, the callback blocks in #renderCheckBoxOn:  
#renderInput1On: #renderInput2On: and #renderMultiSelectOn: would  
indeed be evaluated if the forms were submitted (and a way to submit  
the forms was coded in those methods), but there are no comments in  
those methods that pretend otherwise. In #renderDateInputOn:  
#renderListOn: #renderRadioOn: and #renderTimeInputOn:, the callback  
block would also be evaluated if one were supplied and the form were  
submitted.

To summarize: when there is a liveCallback block, the callback block  
is only disabled for anchors and buttons.

HTH
Michel.



On Feb 27, 2008, at 2:49 AM, Steve Aldred wrote:
renderCheckBoxOn:
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Michel Bany wrote:
> I'm confused...

No, the confusion was mine :)

I'd incorrectly expected the liveCallback to disable the callback on the
input fields too. With the code I was using there was no point in
calling the callback on submit if the liveCallback had fired as state
changes had already been made, no harm done either. I suppose you could
write code where the second call would create issues but that would be a
poor way to structure it anyway.

>
>
> To summarize: when there is a liveCallback block, the callback block
> is only disabled for anchors and buttons.

Yes.

thanks
Steve
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside