The proposed diff is linked via the URL field of this issue. The diff is for release50 branch, it will be slightly
changed for 6.0.
Assigning to myself. Petr who is responsible for the TreeView? If it is not you please put the person on Cc: of this report.
6.0 is feature frozen and this doesn't look like a bug fix...
Yes, I know. But taken into account the length of the release cycle I would still like to consider it for 6.0. I did
mark it as ENH ;-) Also please note that the code will do exactly the same as it did before if the special flag will not
I am trying not to fork our release for 6.0 - if it will not be possible I will most probably have to. Bad karma (too
late, I know). This is not user visible feature, although it is an API change (adding a protected field to a public class).
Created attachment 44931 [details]
I have uploaded the proposed patch. I have added one public method to the TreeView class.
Considering the feature freeze status is there any chance this could be applied to the trunk now?
We had this reported by our testers as a fault (NOK - Not OK) but I am aware that this is a feature in TreeView (and API
Please let me know whether I can (or cannot) apply it. Adding Jesse and Jarda on Cc: ...
No personal objection from me, but it needs to go through apireviews (wait a week).
Checking in apichanges.xml;
/cvs/openide/explorer/apichanges.xml,v <-- apichanges.xml
new revision: 1.14; previous revision: 1.13
Checking in manifest.mf;
/cvs/openide/explorer/manifest.mf,v <-- manifest.mf
new revision: 1.13; previous revision: 1.12
Checking in src/org/openide/explorer/view/TreeView.java;
/cvs/openide/explorer/src/org/openide/explorer/view/TreeView.java,v <-- TreeView.java
new revision: 1.25; previous revision: 1.24