Type: Posts; User: sonata82
I was asking myself the same thing!
I ended up settings the mentioned property in the build.xml:
In the callback of cascadeBy, you shouldn't alter the structure of the tree.
To delete a number of childnodes you could use the following structure:
var i, node,
nodesToDelete = ;
Please bring back the comments :((
It was a really helpful feature!
Thanks to this hint I was able to find a solution for my problem: removing a childnode from a tree, without the Store trying to remove the object on the server. Unfortanelty the remove function of...
For those interested in a dirty workaround:
var p = Ext.ComponentQuery.query('#panel');
Ext version tested:
Ext 4.2.1 rev 883
Browser versions tested against:
IE 8, 9
Couldn't agree more. Especially because IDEs can work with this, but not interpret the "me" assignment.
This is not an issue for me, because ExtJS always provides an extra parameter scope:
When the project started two years ago, Java 1.6 looked like a version which was in a stable enough state to use it (we are developing for IBM i). Originally we even started on Java 1.5, to keep the...
Imho 1.6 would be the way to go.
We are deploying our application for Java 1.6.x and for consistency reasons, compiling and building is done using the same Java version. Requiring 1.7 just for...
Fixing this issue seems to be on the road map for 4.2.
Any progress here?
You probably already solved your problem, but please see this post for updates to Saki's component for ExtJS 3.
Please post the code of the class and where setLayers is called, this is not enough to determine what went wrong..
Thanks Condor, had the same problem in IE 8 using Ext 3.3.1 and defining the image as Ext.BoxComponent fixed it.
I have found the examples in the API inadequate too..
According to this thread http://www.sencha.com/forum/showthread.php?133653-Unable-to-subclass-and-use-panels&p=645543&viewfull=1#post645543,...
To me, this piece of information should be mentioned in the API, with a big exclamation mark!
Turning off Garbage collection is definitly not an option for me!
I could reproduce this error on IE 8 with ExtJS 4.0.0. It seems Ext.cache is empty on the call of getElementEventCache..