Of course as i said the __Click is used to know which @formula button was
clicked !
(did i say that this field is useless ?)
and of course it can be something completly different from a
@command([FileSave]), but here we are comparing the behavior of domino when
handling a @command([FileSave]) button and a submit() script. One runs fine,
the other has a bug but both should save the document:
you say "A possible solution would be to respond on the form.submit() action as
if the first button was used", well domino *has* to: a lot of people (lotus
included) use submit() this way...
my post (i know my english could be improved) was
saying : you dont need a __Click to know whether a field is to be updated or
not.
And as __Click is the only difference between the 2 posts, i dont see a reason
why the submit() post could not be correctly handled.
Of course as i said the __Click is used to know which @formula button was clicked ! (did i say that this field is useless ?) and of course it can be something completly different from a @command([FileSave]), but here we are comparing the behavior of domino when handling a @command([FileSave]) button and a submit() script. One runs fine, the other has a bug but both should save the document: you say "A possible solution would be to respond on the form.submit() action as if the first button was used", well domino *has* to: a lot of people (lotus included) use submit() this way...
my post (i know my english could be improved) was saying : you dont need a __Click to know whether a field is to be updated or not. And as __Click is the only difference between the 2 posts, i dont see a reason why the submit() post could not be correctly handled.