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)
...
>
> > Also, IIRC proteus does handle this for your (or at least is it
> > planned).
>
> Heh! I thought Proteus requires direct database access, whereas I'm
> using xmlrpc. But looking closer I see there's an xml proxy! Cool.
>
> I'll look into that one.
>
>
>
--
Bertrand Chenal
B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
Email: [email protected]
Website: http://www.b2ck.com/
--
[email protected] mailing list
