[Bese-devel] Re: Having a simple-form call an action

[Marijn Haverbeke]

Ho hum. I swear I really do think about these things before mailing, but it
seems I had missed the answer-component function. So what I do now is get
the parent reference from the form, and call answer-component on that in the
refresh-component method of the form. Is this more or less the intended way?
I'd still prefer to directly call an action on the parent component and go
without the ugly parent pointer altogether.


Well, it seems I am confused. Defining a refresh-component for my form class
> does allow me to do something when the form is submitted, but it's not quite
> what I needed. Firstly, I what I want to do is call an action on the
> component that this form is a part of. Now I keep a parent reference to that
> in my form component, but that is a bit crummy. Second, when I try to call
> answer from this refresh-component method it complains that the form's
> calling-component slot is unbound. Which I guess it is... the user got to
> that page by clicking a link that called an action which called the
> component that this form is a part of. What I expected was that when I call
> answer, it will return from the last component that was called... but
> apparantly that is not the case.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/bese-devel/attachments/20060609/db1b4302/attachment.html>