Simone Gianni wrote:
| | Hi Myriam,
| | yes, the fd;on-value-changed is the right way to do it.
| |
| | The typical case is the state/region/province/town selections, where
| | selecting a state must populate the regions dropdown with the right
| | regions and so on. This is done with an fd:on-val
Hi Myriam,
yes, the fd;on-value-changed is the right way to do it.
The typical case is the state/region/province/town selections, where
selecting a state must populate the regions dropdown with the right
regions and so on. This is done with an fd:on-value-changed listener
that populates the ot
Simone Gianni wrote:
| | Hi Myriam,
| | the fd:on-value-changed is a SERVER SIDE event handler. So it's
| | triggered when the form is submitted by the browser. You can force
| | the browser to submit the form whenever a given widget value is
| | changed
| | using the in the form
| | template (
Hi Myriam,
the fd:on-value-changed is a SERVER SIDE event handler. So it's
triggered when the form is submitted by the browser. You can force the
browser to submit the form whenever a given widget value is changed
using the in the form template (it
should do this automatically if there is a l
| | even if i change the value of my list, nothing is printed and the
| | value of the other list isn't changed.
| | I think the javascript isn't read.
| |
in fact the print is done once the form is submited,
is it normal?
-
T
hello,
I'm working this cforms.
My forms are OK except for one thing :fd:on-value-changed :
key="dossier.type"/>
java.lang.System.err.println("Was here!");
java.lang.System.out.println("Was here!");
print("was here");
var datatype = event.source;
var
