Any idea please?
Should I open a bug?
dperez wrote:
>
> Hi,
>
> I have a HTML page that needs vertical scrolling. When I click some
> elements in the page, a want to show a menu. That's an easy task with
> qooxdoo. To position the menu near the clicked element, I use this code:
>
> va
Thanks Jim, it isn't a bad idea.
But I'm sure a more clean way of doing it must exist. It's a very usual
situation, when you wish an initial state that can be resized smaller or
bigger.
For example in Swing (java) each widget apart from the minimum, maximum,
preferred and current size, have a res
Another issue, this sample crashes Firefox 2.0
Why?
Setting a minimum height of 'auto' and a height setting of 100% is causing
the window to adopt some height, then it grows a little (possibly the window
border and padding), then a little more and more...
Waiting a few minutes, Firefox crashes.
Jim Hunter schrieb:
> After upgrading from .6.x to .7.x I am getting a warning in the
> following line of code that used to work. The code no longer works and
> generates a warning (the message follows the code sample). Here is the
> code:
>
> this.From.addEventListener ('keyup',
> function(){t
The API documentation system doesn't include any theme classes. This is
because the system doesn't appear to consider these as proper classes.
However, in trying to work out what themes can be provided and how to
derive from them it is essential information. For example, qx.theme.ext
doesn't appea
I uploaded an application, and this is a request for all who wants to have a
look at it.
It shows good some possibilities of qooxdoo and how fast it can be with
backend database requests.
The application is runnig like an applet, embedded in a normal html page.
Here is the url:
http://www.fitnessw
> Firefox:
> If you scroll the browser (not the table widget), the selected row
> is not the row where the mouse pointer is. Instad a row is selected,
> which is [scrolled pixel] below mouse pointer.
> This works well in IE - at least in IE6. (Please could someone give
> feedback, if the applicati
Hello Sebastian and others,
I am still having the same problem with drag and drop over the tree and
both Derrell and I cannot do anything without your input. I have
produced a screencast to demonstrate the problem:
http://m41s09.vlinux.de/dragDropProblem.avi (Sorry, 2MB)
I am using Firefox 2.
Some random hacking of the qooxdoo 0.7 code reveals thatt if I patch the
current 0.7 branch code like this, it does what I want. But this is
hardly the solution and might have many unintended consequences.
qx.ui.core.Widget.prototype.supportsDrop = function (dragCache)
{
var supportsDropMethod
Christian, it appears that all you've done here is revert to the
original behavior including your original patch. You've removed my
changes that alllow a drop onto self when self really supports it.
The problem with returning 'true' unconditionally in supportsDrop() is
that it allows, for example,
On 9/6/07, Derrell Lipman <[EMAIL PROTECTED]> wrote:
> Christian, it appears that all you've done here is revert to the
> original behavior including your original patch. You've removed my
> changes that alllow a drop onto self when self really supports it.
> The problem with returning 'true' unco
Has anyone run across the apostrophe in IE being displayed wrong issue? And
if you did, have you been able to fix it? I am sending over an apostrophe
from the server and when it gets displayed in IE it shows up as '
instead of '. In testing basic HTML it works fine, but when displayed via
qooxdoo i
Derrell Lipman schrieb:
> Christian, it appears that all you've done here is revert to the
> original behavior including your original patch. You've removed my
> changes that alllow a drop onto self when self really supports it.
> The problem with returning 'true' unconditionally in supportsDrop()
Fabian,
I wish it did work as expected, but alas it does not. My code used to upper
case user input, now I just get the warning and nothing else happens. Here
is what is in the log:
098624 WARN: qx.event.type.KeyEvent[3776]: Deprecated: please use
getKeyIdentifier() instead.swep.js (line 3304)
ap
Try one of the String functions:
qx.html.String.toText
See the docs for others.
Jim Hunter wrote:
> Has anyone run across the apostrophe in IE being displayed wrong
> issue? And if you did, have you been able to fix it? I am sending over
> an apostrophe from the server and when it gets display
Hey there, I'm new here, I'm from Karlsruhe/Germany and my name is Christian.
I am concerned about the following situation:
I need to mark some qx.ui.basic.Labels as headline, but I don't want to
style them with and CSS, so I tried to assign an appearance to those
labels, called "headline-1".
I
Hallo Hugh,
thank you for spending your time with me ;-)
Here is a snippet for testing, as required. Please use firefox and scroll
the browser and see what happens, if you click a line.
// in main
this.base(arguments);
var d = qx.ui.core.ClientDocument.getInstance();
var inlineWidget = new qx.ui.
Hi, Dietrich,
I like your solution but I have two questions:
- I think, in case of IE6 the time until application start will increase
because of loading the compressed content before loading of uncompressed.
Would be in my case between 10% and 20%, I think that's ok. Beyond this, is
it thinkable,
> I created my own meta theme (and its appearance theme), in which
> "headline-1" exists. It works.
So just to clarify you've created your own theme, derived from a standard
theme, where "headline-1" is added. But if you wanted to use a variety of
standard themes (and, indeed, use a standard theme
Jim,
> Firefox and all the rest work fine. I did a search of our archives
> and the word apostrophe was never used so this should be a new issue.
Already reported and fixed at
http://bugzilla.qooxdoo.org/show_bug.cgi?id=615
You should search the bugs first :-)
Hugh
---
20 matches
Mail list logo
