Thanks, that's a sanity saver-
I was calling it from wiithin my main function i.e.
qx.core.Init.getInstance().defineMain(function()
{ etc..}
It was still after the qx.js, but when I took it out of the function and put
it above or below it it works.
Thanks again!
Dan
Alee wrote:
>
> I
I have called it in the HTML file after including the qx.js
qx.dev.log.Logger.ROOT_LOGGER.setMinLevel(qx.dev.log.Logger.LEVEL_OFF);
and it works .. Where are you calling it ?
Dan1234 wrote:
>
> Thanks for that.
>
> T
Thanks for that.
That does disable logging to the log window, however it does not stop the
small "log" window appearing when the application is first loaded in the
browser.
Any other ideas? Perhaps I have to do a special build or something?
Thanks
Dan
Alee wrote:
>
> Hello Dan
>
> try usin
Hello Dan
try using
qx.dev.log.Logger.ROOT_LOGGER.setMinLevel(qx.dev.log.Logger.LEVEL_OFF);
Dan1234 wrote:
>
> A no doubt shamefull question to ask, but
>
> How do I turn off/ stop that debug/ log window popping up.
>
> I'm running 0.61
>
> I thought I could do something like
> qx.de
A no doubt shamefull question to ask, but
How do I turn off/ stop that debug/ log window popping up.
I'm running 0.61
I thought I could do something like
qx.dev.log.Logger.ROOT_LOGGER.removeAllAppenders();
or even
qx.dev.log.Logger.ROOT_LOGGER.enabled=false;
But the window keeps on popin
Hi Alessandro!
Thank you for your contributions. This is really helpful.
In your described case this was my fault. Yes, it's not enough to just
remove the update handler. We also need to be sure, to not to register
methods inside the global scope.
After applied your patch, I've however detecte
Hello Sebastian,
looking at svn revision 4458 I noticed that you applied my patch
to variableoptimizer.py, thank you.
I also noticed that you reverted my change at the and of the
search() function in order to not substitute global variables
and functions; anyway, simply avoiding to call update()
What browser are you using? The artifacts should have nothing to do with
qooxdoo, I would think.
Derrell
Hmm... You are right: this issue appears only under FF 1.5.07, IE has no
problems. Strange... What can i do besides refreshing while scrolling?
And when nothing th
any chance that one of the qooxdoo gurus could take a look. Below is a link
to the standard helloworld firefox extension (helloworld.xpi) - if you
install this in firefox, it hangs firefox; if you delete line 7 of
content/overlay.xul ( ) and reinstall the extension it
works fine. To remove the ex
Hi!
Because of many user problems regarding the cache feature I have just
checked in a little enhancement which automatically compares the state
of the cache files with the internal files.
This means if one of the build files is newer than the cache file, the
cache file will be ignored.
Norma
Hi Dietrich,
>
> would you consider opening a bug in bugzilla for this so it doesn't get
> lost.
>
>
I think Sebastian applied these patches in revision , so the problem
should
already be solved.
Cheers,
Alessandro
Yes your right. The problem is solved.
Best Regards...
[EMAIL PROTECTED] schrieb:
Hi Dietrich,
would you consider opening a bug in bugzilla for this so it doesn't get
lost.
I think Sebastian applied these patches in revision , so the problem
should
already be
Hi Alessandro!
The patch for Tree is applied to SVN, revision 4441.
The other patch is IMHO a bit problematic. We don't want to compress
names in the global scope. However other parts are looking good. I've
applied the complete patch but ignored the part which runs through the
global namespace
Perfect now! Thank you!
Sebastian Werner schrieb:
Has been fixed by Andreas in revision 4445.
Sebastian
Dietrich Streifert schrieb:
Thank you Sebastian.
But now the build fails in a previous state:
make[1]: Entering directory `/development/www/qooxdoo/frontend/api'
INITIAL
> Alex, I believe this is a commonly-discussed deficiency in the currently
> layout
> system. The tree widgets (and, I believe, many others) must have their size
> fixed.
>
> You should be able to catch an event on the window ("ONAPPEAR"?) and resize
> the tree based on the size of the window.
Has been fixed by Andreas in revision 4445.
Sebastian
Dietrich Streifert schrieb:
> Thank you Sebastian.
>
> But now the build fails in a previous state:
>
> make[1]: Entering directory `/development/www/qooxdoo/frontend/api'
>
> INITIALIZATION:
> ---
"Alex D." <[EMAIL PROTECTED]> writes:
> i have a little problem with TreeFullControl(same with Tree): I have one in
> a window and i want it to fill the window vertically(100%). So i thought i
> set: tree.setHeight("100%") and height of the window to absolute:
> win.setHeight(300), so the height o
Thank you Sebastian.
But now the build fails in a previous state:
make[1]: Entering directory `/development/www/qooxdoo/frontend/api'
INITIALIZATION:
* Processing arguments...
SOURCE LOADER:
-
Hey!
This is already fixed in SVN revision 4443. :)
Sebastian
Dietrich Streifert schrieb:
> The current svn rev. 4441 fails building with the following error:
>
> make[1]: Entering directory `/development/www/qooxdoo/frontend/api'
>
> INITIALIZATION:
> --
The current svn rev. 4441 fails building with the following error:
make[1]: Entering directory `/development/www/qooxdoo/frontend/api'
INITIALIZATION:
* Processing arguments...
SOURCE LOADER:
-
Hi Alessandro,
would you consider opening a bug in bugzilla for this so it doesn't get
lost.
I'm now on the way implementing the "table" parts of my application and
get hit by this bug.
My understanding of the optimizer is zero compared to yours and you're
shure much more able to describe th
Hi folks,
i have a little problem with TreeFullControl(same with Tree): I have one
in a window and i want it to fill the window vertically(100%). So i
thought i set: tree.setHeight("100%") and height of the window to
absolute: win.setHeight(300), so the height of the tree is limited
through t
I think is something like:
input7.dispatchEvent('click')
candy wrote:
>
> var input7 = new qx.ui.form.Button("Send Message");
>
> input7.addEventListener("click",function(e){
>
> });
>
>
>
> If I don't click button,how to active button "click" event
>
>
--
It would be better if focus were restored automatically to the widget that
had focus before the modal window was opened.
Jim Hunter-2 wrote:
>
> It happens in IE if there are no controls with focus and you hit the
> ENTER/SHIFT/CTRL/ALT keys. It does not happen in the other browsers. I
> would
Visual Studio.NET is working ok.
Don't remember about old version VS 6.0
alex.d wrote:
>
> Thx Alee,
> Visual Studio 6.0 has by default only Visual C++(the whole other stuff
> is extra). I will install VStudio 2005 i think.
>
> Best Regards,
> alex.d
>> Hi alex.d,
>>
>> You can use Visual Int
Hi again,Thanks for the advice -- I tried both of your suggestions. Moving the dispose() call into a qx.ui.window.Window._afterDisappear() method and adding a qx.constant.Event.DISAPPEAR listener to the window. Unfortunately both methods still results in the same error messages when dispose is ca
26 matches
Mail list logo