PDA

View Full Version : [OPEN] Ext.tree.TreePanel: unable to cancel events



schmidetzki
12 Jun 2007, 3:49 AM
There is another bug in TreePanel:

You should be able to cancel the "beforecklick" event by returning false.
However the Tree-s eventProxy does not return the value.

Please change


Ext.tree.TreePanel.prototype.proxyNodeEvent = function(){
this.fireEvent.apply(this, arguments);
};
in


Ext.tree.TreePanel.prototype.proxyNodeEvent = function(){
return this.fireEvent.apply(this, arguments);
};

schmidetzki
12 Jun 2007, 11:02 PM
I anaylised this bug (together with another bug I posted in http://extjs.com/forum/showthread.php?t=7553).

I hoped to get any answer in this forum form the developers.
A simple agree/not agree whould be enough to know if it will be fixed in the final version or not (in wich case I have to find my own workaround)

Getting simply no reaction makes it difficulty to plan my Ext-using project.
And if the developers do not react on such very concret bug reports I can save my time to posting them in the future.

tryanDLS
13 Jun 2007, 8:20 AM
Someone will respond when they get a chance to read the threads and make a determination of whether something is a bug or a design decision - in most cases that Jack's call. There are limited resources attempting to handle all the tasks associated with development, support, doc, etc. Just because you don't get an immediate response doesn't mean it's being ignored. Please continue to post things you consider to be bugs. There is no standard timeframe in which you should be expecting a response. If you need to have more immediate feedback, you should consider a support contract, with guaranteed response times.

schmidetzki
20 Jun 2007, 12:53 PM
Someone will respond when they get a chance to read the threads and make a determination of whether something is a bug or a design decision.

OK, no response since 14 days.
I still have no idea wether the bug will be fixed or not in the final version.
I made a very clear and easy to analyse statement together with a surgestion to correct the code. This was no "something general went wrong"-post.
It should not take longer than 5 minutes to check.

To get a response to a bug report should not be limited to premium users!

jack.slocum
20 Jun 2007, 5:43 PM
Sorry for the lack of response. It was fixed in SVN a while back the first time it was reported.

TheQ
26 Jun 2007, 6:18 AM
Hey! ExtJs will cahange the world! Great job all!

This one cost me tho ...

If I understand it right ...

Was:
Ext.tree.TreePanel.prototype.proxyNodeEvent = function(){
this.fireEvent.apply(this, arguments);
};

Then Was:
Ext.tree.TreePanel.prototype.proxyNodeEvent = function(){
return this.fireEvent.apply(this, arguments);
};

Now is:
Ext.tree.TreePanel.prototype.proxyNodeEvent = function(){
this.fireEvent.apply(this, arguments);
};

My code likes 'Then Was:'. Is that where we're going?

Thanks for all!