Re: [Bug] gnue-forms / gnue-appserver: OnChange / abort / editable="new"

David Ayers schrieb:
> Reinhard Mueller schrieb:
>> Am Samstag, den 03.05.2008, 11:48 +0200 schrieb David Ayers:
>>> When saving an newly to be inserted object fails due to an abort
>>> during the OnChange processing in the gnue-appserver, the form's field
>>> property editable="new" is misinterpreted in the sense that the
>>> fields become deactivated ...

[snip]

>> Second, I could not reproduce the behaviour with OnChange but only with
>> OnValidate. Could you please double-check?
> 
> Ahm... yes I haven't implemented OnValidate, but actually the check I'm
> making /should/ be implemented in OnValidate... especially if I call
> abort.  So unless you want me to debug thism I would 'correct' my code
> and go from there.

I just raised on OnChange and the field remained editable.  So it
/seems/ that whether the 'new' status changes is independent of whether
OnChange or OnValidate raises, but is potentially dependent of some
arbitrary order of processing in the appserver.

Cheers,
David