On 24-09-10 14:56, Bertrand Chenal wrote:
Le Fri, 24 Sep 2010 13:53:58 +0200,
Paul J Stevens<[email protected]> a écrit :
Bertrand,
thanks for the quick reply.
on_change is handled client side:
- To know if on_change exist for a field you have to call
"fields_get" on the model you are working on, this will give you a
description for each field. But you probably already know it.
- This description (a dictionary) will eventually contains an
on_change key associated with a list of field names. Then you
have to do an rpc "on_change_field_name" and pass those fields.
Sorry, I'm getting close, but I'm unsure what to pass to the
on_change handlers.
Example took from party/contact_mechanism.py:
def on_change_value(self, cursor, user, vals, context=None)
...
It is the type/structure of vals I was inquiring about. But don't worry:
proteus looks good to go.
One point: while calling Method.save() I think I've stumbled upon a
mismatch between hg/tip and proteus/tip
Method.save calls:
context['_timestamp'] = self._get_timestamp()
but this will trigger an exception on the trytond end. Something to do
with the recent timestamp changed by Cédric I assume?
--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
--
[email protected] mailing list
