> There are no bugs. The default value of liveUpdate is false
Ah, thanks. I've now read up on liveUpdate (not without difficulties -
see my posting about the API viewer sent with this message).
Hugh
-
This SF.net email is sp
Hugh Gibson schrieb:
>>> Any comments about the problem of the "input" event listener
>> hiding the
>>> "changeValue" event, and the listener on "changeText"?
>> What exactly do you mean?
>
> Did you not get the other email I sent in this thread? I've copied the
> relevant bit below (the demo is
> > Any comments about the problem of the "input" event listener
> hiding the
> > "changeValue" event, and the listener on "changeText"?
>
> What exactly do you mean?
Did you not get the other email I sent in this thread? I've copied the
relevant bit below (the demo is
http://demo.qooxdoo.org/0.
Hugh Gibson schrieb:
> Sebastian,
>
>> After you have send me your key press order I
>> was able to reproduce it here.
>>
>> I have found and fixed the bug. Revision 8538.
>
> Any comments about the problem of the "input" event listener hiding the
> "changeValue" event, and the listener on "chan
Sebastian,
> After you have send me your key press order I
> was able to reproduce it here.
>
> I have found and fixed the bug. Revision 8538.
Any comments about the problem of the "input" event listener hiding the
"changeValue" event, and the listener on "changeText"?
Hugh
--
Hi Nick,
wow this really was a bug. After you have send me your key press order I
was able to reproduce it here.
I have found and fixed the bug. Revision 8538.
Thank you again for your stying power ;)
Sebastian
Nick Glencross schrieb:
> Sebastian,
>
> thanks for your time on this.
>
> On 1
Sebastian,
thanks for your time on this.
On 12/06/07, Sebastian Werner <[EMAIL PROTECTED]> wrote:
> This was not the text which the widget got on focus. This was the text
> configured before the event listener was attached. The "changeValue"
> fires, even when using the setters. Just put them ab
Nick Glencross schrieb:
> Sebastian,
>
> Sebastian Werner wrote:
>> Nick Glencross schrieb:
>>> Hi all!
>>>
>>> I've been using the changeValue event with liveUpdate to control the
>>> Enabled property of two mutually exclusive fields. Works well, but I
>>> found that when I removed all the text i
> I can't currently see a reason for the current behaviour, and think
> it will bite quite often. For users that really want this, they
> should be able to implement it in the application layer.
I agree totally with this. Every change should be visible, though it
seems that adding an "input" list
Sebastian,
Sebastian Werner wrote:
> Nick Glencross schrieb:
>> Hi all!
>>
>> I've been using the changeValue event with liveUpdate to control the
>> Enabled property of two mutually exclusive fields. Works well, but I
>> found that when I removed all the text in a field the event doesn't
>> trigg
Hi Nick,
Nick Glencross schrieb:
> Hi all!
>
> I've been using the changeValue event with liveUpdate to control the
> Enabled property of two mutually exclusive fields. Works well, but I
> found that when I removed all the text in a field the event doesn't
> trigger.
this seems to work well for
Hi all!
I've been using the changeValue event with liveUpdate to control the
Enabled property of two mutually exclusive fields. Works well, but I
found that when I removed all the text in a field the event doesn't
trigger.
Looking at the code, the current value is remembered when the widget
recei
12 matches
Mail list logo
