While writing the post, I got an idea: would it be a proper way, to create a
wrapping class for the value to bind which contains the method so it can be
called in converter?
My Real-World-example which is working (with Date instead of int, sorry for
the confusion):
Okay, there is at least one more fallacy. If I add a method like the
following to the DateWrapper to increase the date by x days, the
label-binding wouldn't call the converter because the wrong key is listened.
But if I am setting the binding-key to gameData.date.date, the converter
would run but
Hello John
done, https://github.com/qooxdoo/qooxdoo/issues/202
Thxs, Werner
On 4/13/16 9:51 PM, John Spackman wrote:
> Hi Werner
>
> It looks like a bug to me - the issue is that the yellow bars on the side are
> where the native scroll bars go, but on Chrome & Safari they do not appear.
>
Hi everybody,
is it possible, to pass or use another object from outside inside of the
converter-method used in a singlevalue-binding?
For e.g. I have this code:
var someObjectFromOutside = new CoolObject();
var lblInfo = new qx.ui.basic.Label();
this.bind("propertyObject.intValue",
Finally I found a working solution. I'm not sure if I like that way but it
works and its not that much more code.
Following is the wrapper-class. It contains a new property which is set as
the formatted date-string:
qx.Class.define("mkss.data.DateWrapper", {
extend: qx.core.Object,
I think that would work (although it's hard to be sure without a working
example) but you could solve the initial problem with a closure.
John
> On 15 Apr 2016, at 20:44, LoneSurvivor wrote:
>
> While writing the post, I got an idea: would it be a proper way, to create a