A Dijous, 28 de gener de 2010, [email protected] va escriure:
> Hello,
> Perhaps I'm misunderstanding something, but I'm not clear on how the button
> element works. Specifically, in sale_view.xml there is a button with name
> 'order_confirm' with no corresponding function in sale.py. There is,
> however, a signal in the workflow with that name. I assume that is fine -
> the signal is the function. Correct?
Well, the signal is not the function. That button is used as a signal
(trigger) for the given workflow transition. The target ("to") of the workflow
transition will be the next state, and if that state is configured to execute
a function, that function will be called.
Not sure, if I've been clear enough...
>
>
>
>
> -------------------- m2f --------------------
>
> --
> http://www.openobject.com/forum/viewtopic.php?p=50363#50363
>
> -------------------- m2f --------------------
>
>
> _______________________________________________
> Tinyerp-users mailing list
> http://tiny.be/mailman2/listinfo/tinyerp-users
>
--
Albert Cervera i Areny
http://www.NaN-tic.com
Mòbil: +34 669 40 40 18
_______________________________________________
Tinyerp-users mailing list
http://tiny.be/mailman2/listinfo/tinyerp-users
