You must keep in mind that the toolkit isn't only being used for new development. Some of us have to use it to create browser front ends to 10 year old Windows applications. I don't have a choice, the font information I'm getting is in points. On the server side I simply divided all font sizes by .
Hello Sebastian,
I committed a simple change which corrects
the problem by
enclosing the unload handler in a try/catch block.
I don't think this was a good idea. More interesting is the real place
which leads to this error. A try/catch around the unload handler will
also hid
All sizes in qooxdoo are in pixels. In my opinion points are only used
historically. But they are only useful when designing something for
print. This is because the size of points on the screen generally
differs between the operating systems and browsers. There is no
possibility to switch to p
Does qooxdoo treat the value passed in for the font size, when creating a new font, as pixels not points? It seems that the fonts I create are too small and when I have a font on the same page that is done with pure CSS using the same size font but explicitly set as points, the CSS fonts are larger
Hi,
I am trying to print a list with ListView that has a vertical scrollbar in
case of overflow.
In FireFox it works fine, but int IE there is a delay in the scrollbar, it
iss not responding as it should.
I believe it cannot be the amount of items in the list, because the problem
is already cau
Hi,
It would be a good idea that
myWidget.set({ padding: 10 });
worked. It is a property group instead of a regular property, but it is set
in the say way, and many times the end user doesn't know this fact.
BTW, this kind of properties aren't shown in the API viewer.
Regards
David
--
V
Thanks Sebastian,
Now I understand
Sebastian Werner wrote:
>
> Hi David,
>
> you need to use BorderObject instead of Border if you want to have a
> dependency between the widget and the border. Otherwise the border will
> be applied just once (which is more efficient).
>
--
View this mes
Hi all,
I would like to comment that the resize behavior is coded in BaseResizer.js,
and is used from Window.js and Resizer.js.
Now you can limit the resizeable behaviour in each direction.
dperez wrote:
>
> Finally, I have commited it to SVN.
>
> Class qx.ui.window.Resizer
>
> A new exampl
Hi,
Finally, I have commit it to SVN.
Class qx.ui.window.Resizer
A new example has been created example/Resizer_1.html
If you find any bug in this class or in qx.ui.window.Window, please report
it.
dperez wrote:
>
> Hi all,
>
> I'm preparing a new contribution called qx.ui.window.Resizer,
Hi David,
you need to use BorderObject instead of Border if you want to have a
dependency between the widget and the border. Otherwise the border will
be applied just once (which is more efficient).
Sebastian
dperez schrieb:
> Thanks Jim, but I have initially already done so, and doesn't work
Thanks Jim, but I have initially already done so, and doesn't work.
Here is a more complete snippet:
myWidget.setBorder(new qx.renderer.border.Border(1, 'solid', '#000'));
myWidget.getBorder().setRightWidth(20);
Jim Hunter-2 wrote:
>
> Just a guess, but if you had not assigned a border object
Just a guess, but if you had not assigned a border object to the widget then getBorder() is going to return null. When you create the widget, assign a border to it, even if the border has a 0 width. At that point you should be able to set properties of the border.
JimOn 10/31/06, dperez <[EMAIL PRO
Hi,
If I call this:
myWidget.getBorder().setRightWidth(20)
then nothing happens visually, even if I call Widget.flushGlobalQueues().
I wonder why.
Thanks in advance for any light in this area.
Regards
David
--
View this message in context:
http://www.nabble.com/Border-width-tf2544700.html#a
13 matches
Mail list logo
