-PART 2
Found a Google link talking about problems with Firefox and TextField.
I tried other browsers and the TextField works fine. I use Nightly of
Firefox version 20 1a , will try in older Firefox versions after I send this.
Would be nice to use a
I had programmed a table widget with search field using
the qx.ui.form.TextField() object under qooxdoo 2.0.1
I moved to 2.1 all my stuff works (now), had to change order
of operation around some with root placed items and
container placed widgets. but can not figure why TextField
is not worki
Hi,
I dont understand why the transition animation doesnt work with
page.Manager on a tablet.
I found this tweak on the web :
pageManager.__masterContainer.getLayout().setShowAnimation(true);
But its not working when I build the application because its a private
property
It have a
This is great. Looking forward to using it in my apps.
On Thu, Nov 22, 2012 at 8:09 PM, thron7 wrote:
> George Nicolaidis wrote in to inform us of a new qooxdoo-based XML -> UI
> tool called "Qookery". See his announcement.
>
> T.
>
>
> Original Message
>
> Dear Qooxdoo develope
Hi Martin,
Yeah, I've figured that out as well. Before, I'd always wondered what these
lines were doing in my console.
Strangely enough, the stack trace ends there:
> qx.log.Logger.trace:220
> qx.log.Logger:334
are the only two entries.
However, I do think I've isolated the problem:
While digg
Hey,
Did you also check the implementation of the deprecatedConstantWarning [1]? It
does not create the warning, it creates a getter which warns as soon as the
constant is accessed. Also, I'm quite sure its not in the framework. I made a
playground sample [2] and there is no warning when I use t
Hi,
the "qx.ui.tree.VirtualTreeItem" which you are using right now has (i.e.
knows) no 'size' property. Therefore this line fails in your code example:
---
...
controller.bindProperty("size", "size", null, item, id);
...
---
You are missing a custom class
("demobrowser.demo.virtual.tree.TreeIt
Hi Martin,
No, I'm not using anything out of the ordinary. I think Thomas was right: the
warning is thrown whenever the Opacity class is used, regardless of whether the
constant is being accessed or not.
I've found the relevant code here:
https://github.com/qooxdoo/qooxdoo/blob/release_2_1/fra
