On Fri, 2004-04-30 at 16:10, Vadim Gritsenko wrote:
> Bruno Dumon wrote:
>
> >On Fri, 2004-04-30 at 14:30, Vadim Gritsenko wrote:
> >
> >
> >>Sylvain Wallez wrote:
> >>
> >>
> >>
> >>>Bruno Dumon wrote:
> >>>
> >>>
> >>...
> >>
> >>
> >>
> And now the practical side: example us
Bruno Dumon wrote:
On Fri, 2004-04-30 at 14:30, Vadim Gritsenko wrote:
Sylvain Wallez wrote:
Bruno Dumon wrote:
...
And now the practical side: example usage in flowscript:
form.getWidget("test").addActionListener(newActionListener(function(event)
{
print("hi there");
On Fri, 2004-04-30 at 14:30, Vadim Gritsenko wrote:
> Sylvain Wallez wrote:
>
> > Bruno Dumon wrote:
>
> ...
>
> >> And now the practical side: example usage in flowscript:
> >>
> >> form.getWidget("test").addActionListener(newActionListener(function(event)
> >> {
> >>print("hi there");
Sylvain Wallez wrote:
Bruno Dumon wrote:
...
And now the practical side: example usage in flowscript:
form.getWidget("test").addActionListener(newActionListener(function(event)
{
print("hi there");
}));
where the newActionListener function is as follows:
function newActionListener(list
On 27 Apr 2004, at 10:24, Bruno Dumon wrote:
(*) multivaluefield: the builder happily builds the listeners, but
multivaluefield seems to nowhere create events. So I haven't added
instance-based event listeners on that widget either. -> solution I see
is to add full support for value changed even
Bruno Dumon wrote:
I've just added the instance based event listeners. You can both add and
remove them.
Following table summarizes the current event situation, see below for
more info.
valuechanged action
field Y N/A
multivaluefield (*)
I've just added the instance based event listeners. You can both add and
remove them.
Following table summarizes the current event situation, see below for
more info.
valuechanged action
field Y N/A
multivaluefield (*) N/A
booleanf
