Hey,
> what about:
>
> construct : function(orientation)
> {
>// ...
>this.initOrientation(orientation);
> }
>
> It will initialize the orientation to default or to 'orientation'.
Exactly, and it will also fire and the change event. But after that, a set of
an external source is hand
Hi Martin,
what about:
construct : function(orientation)
{
// ...
this.initOrientation(orientation);
}
It will initialize the orientation to default or to 'orientation'.
Personally I don't understand why qooxdoo property system generates so
much normally unused methods like init/r
Thanks for the explanation and the link to the bug.
Although I can understand why you dont want to fix this bug, I think it's
problematic to keep a buggy behavior in the name of compatibility for too
long... I hope you will consider fixing this in a reasonable timeframe :)
Cheers
Jean-Noel
On Mo
Isn't the databinding problem only one of fireing/not fireing the event?
So couldn't you simply pass an extra parameter so that the event is not
fired?
Tom
Am 24.01.11 09:06, schrieb Martin Wittemann:
> Hey,
> I tracked down the problem to a known property system behavior / bug.
> The problem is
Hey,
I tracked down the problem to a known property system behavior / bug. The
problem is that the change vent is fired even if the init value is the same as
the new value.
Take a look at the example to see the example:
http://tinyurl.com/4tzppgr
Do you agree it's problematic (this is not consi
Hmm, I realized this is not directly linked to data binding, although
changeBubble is also used for data binding I think. Anyway, the problem is
here.
On Fri, Jan 21, 2011 at 10:49 AM, Jean-Noël Rivasseau wrote:
> Hi Martin,
>
> I noticed a weird behaviour of the data binding system today ( I thi
Hi Martin,
I noticed a weird behaviour of the data binding system today ( I think it's
a bug). This is reproduced by the small app in the playground:
http://tinyurl.com/4bgrzpb
My complaint is that a changeBubble event is trigggered on
imageOptions.verticalRasterMode although the value was not c
Sorry, I did not spot the post about the roadmap, ignore the last question.
I hope the animation framework for Widgets will be in final 1.0 (0.9 would
be even better)
On Wed, Jun 17, 2009 at 5:51 PM, Jean-Noël Rivasseau wrote:
> Hi. Actually I had another bug deep hidden that caused troubles. I
Hi. Actually I had another bug deep hidden that caused troubles. I managed
to fix this, but then ran against the bug you gave me the fix for, so this
was still very useful :)
I am good to go now. What about the roadmap I asked ? ;)
Thanks
Jean-Noel
On Wed, Jun 17, 2009 at 5:03 PM, Jean-Noël Riv
I did method 1 but I still have the bug. I think it's due to something else
that what you originally thought.
Let me see if I can gather more information.
On Wed, Jun 17, 2009 at 2:46 PM, Martin Wittemann wrote:
> Hello Jean-Noel,
> I gave my example code a try in a 0.8.2 environment and as you
Howdy!
> 1. You path the qooxdoo class qx.ui.form.AbstractField by adding this
> to the members section:
>
>
> /**
> * Resets the value to the default
> */
> resetValue : function() {
> this.setValue("");
> },
>
>
> 2. You use an evil JavaScript trick to patch the
Hello Jean-Noel,
I gave my example code a try in a 0.8.2 environment and as you said it
didn't work. As a workaround i thought of patching the textfield to
handle null values. That way you could leave the binding without a
converter and the problem is solved. There are two ways you could
Hi Jean-Noël!
> Btw, it would be *very* nice if there was a roadmap posted somewhere
> regarding new releases shipping dates and their features. Currently I
> have no idea when 0.8.3 will be out and what will be in it.
Apparently you don't know about the roadmap document yet at:
http://qooxdoo.or
Hi Martin, I am still not 100% sure it's a complete duplicate. Your bug
reproduces OK but that does not necessarily mean your fix will take care of
my original bug. I am waiting for your workaround to test
jean-Noel
On Wed, Jun 17, 2009 at 11:50 AM, Martin Wittemann <
[email protected]> w
Hi,
thats good to hear. So i close the bug as a dulicate and take a look
at a workaround after im done with my current task and come back to
you later. I hope i could find a solution for you.
Best,
Martin
Am 17.06.2009 um 11:20 schrieb Jean-Noël Rivasseau:
Hi,
I reproduced the test you g
Hi,
I reproduced the test you gave me in the bug and yes, it fails. I am on
0.8.2 and would prefer not to update to trunk... is there some workaround I
can apply until I upgrade to 0.8.3 ?
Btw, it would be *very* nice if there was a roadmap posted somewhere
regarding new releases shipping dates a
Hi,
It really looks like the bug I fixed yesterday. Jean-Noel, could you
please check the code snipped in the bug report to verify that the
code is reproducing your bug?
Best,
Martin
Am 17.06.2009 um 05:26 schrieb Vincent Vandenschrick:
> Hi Jean-Noel,
> It seems to me a duplicate of the b
Hello Jean-Noel,
ill take care of the bug today and let you know as soon as I know a
solution.
Best,
Martin
Am 17.06.2009 um 00:19 schrieb Jean-Noël Rivasseau:
> Hi all and especially Martin,
>
> Can anyone suggest a temporary workaround for bug 2478 or quickly
> come with a patch for the pro
Hi Jean-Noel,
It seems to me a duplicate of the bug #2457 that Martin fixed yesterday
in the trunk.
http://bugzilla.qooxdoo.org/show_bug.cgi?id=2457
The symptom is that the property resetter method of the target object is
called independently of the converter result (in your case the null
value
Hi all and especially Martin,
Can anyone suggest a temporary workaround for bug 2478 or quickly come with
a patch for the problem? My application deeply suffers of this...
Thanks
Jean-Noel
--
Crystal Reports - New Free
20 matches
Mail list logo
