Hi James,
I think your problem is similar to one I encountered a while back.
The overflow settings for window content don't work properly unless you set a
minWidth and minHeight like this:
// Allows overflow settings to work properly
this.setMinWidth(200);
this.setMinHeight(200);
Hope th
I'm currently working in 0.6.6. How do I make a qx.ui.window.Window
object be a fixed size so that the contents scroll within it? It seems
that the preferredBoxWidth and preferredBoxHeight cached properties are
causing the windows to get resized despite the maxWidth and maxHeight
properties.
You certainly can extend the classes, just that you won't have access to new
properties via the IDE unless you modify the PHPVCL as well. Any changes you
make will need to be addressed directly in code at page load or during code
execution. When you create a file that extends qooxdoo, make sure th
On 6/26/07, FrozenDice <[EMAIL PROTECTED]> wrote:
> Wish I could but there's a few problems with that. I'm running 0.6.6,
> and I can't upgrade since I'm using qooxdoo through Delphi4PHP, which
> generates the code for me. Extending a class in qooxdoo then
> modifying a component to extend an ext
Hello List,
in the last few days we have been working hard to set up
qooxdoo-contrib. qooxdoo-contrib will be a central place to host qooxdoo
related projects like
* New backends
* Example applications
* New widgets
* New qooxdoo classes
* ...
Its main purpose is to give anyo
Wish I could but there's a few problems with that. I'm running 0.6.6,
and I can't upgrade since I'm using qooxdoo through Delphi4PHP, which
generates the code for me. Extending a class in qooxdoo then
modifying a component to extend an extended component is really a lot.
Is there any other way?
Unfortunately winService.self.IMAGE_NAME does not work too. It has
"undefined" value.
Firebug shows that winService.self references to the function that has the
attached "self" function. Latter self function has the attached "classname"
variable and its value is "qx.core.Object".
Fabian Jakobs-
Hi,
With this 3rd form, I get same results as 2nd one:
qx.Class.define("Caja", {
extend : qx.ui.layout.BoxLayout,
properties: {
width: {
refine: true,
init: 'auto'
},
height: {
Hi,
I used to have this before:
qx.Class.define("Box", {
extend : qx.ui.layout.BoxLayout,
construct : function(orientacion) {
arguments.callee.base.apply(this, arguments);
this.auto();
},
});
Now I have changed it to use a custom appearanc
Hi Dioc,
> Hello,
>
> I have written a class that subclasses qx.ui.window.Window and has static
> variable IMAGE_NAME. I pass an instance of the class in the constructor of
> the other class and would like to access static variable IMAGE_NAME by using
> the instance reference. The code looks like:
That's exactly what I wanted. :-)
It's handy for small customizations to built-in appearances. I just have to
override what is needed instead of copying the whole entry.
Sebastian Werner wrote:
>
> In 0.7 you need to define it completely. The most users think this is
> more convenient becaus
Hello,
I have written a class that subclasses qx.ui.window.Window and has static
variable IMAGE_NAME. I pass an instance of the class in the constructor of
the other class and would like to access static variable IMAGE_NAME by using
the instance reference. The code looks like:
qx.Class.define("m
12 matches
Mail list logo
