Community
Participate
Working Groups
Build ID: I20070625-1500 Steps To Reproduce: In the CVS view 1. Expand a CVS repository 2. Expand HEAD 3. Right click and click Expand All The tree doesn't expand all the way down More information: The deferred content provider should possibly have a call back once it completes loading the children so the expand all can know when to expand the next level. Alternatively an event listener for items added to a node in the tree could be registered by the expandAll method and as child nodes are added they could be expanded? This is perhaps just the desired behaviour, but it would be nice to right click expand all on my tree in my RCP app and have it expand all levels, each in turn in their own Jobs.
I'm not sure that we want to support this in the framework, as it will easily lead into a very long-running operation that cannot be canceled by the user. I'm pretty sure that there is a way for you to implement this yourself?
Sorry, I didn't read the description properly and assumed that you were talking about a tree that you implemented yourself. Given that you are asking for a feature in the CVS UI, I can route this request to the appropriate team to let them decide about the feature.
I am talking about my own tree implementation. I used the CVS tree as an example of where you could see it happening. I have managed to find a work around for my use, although I'm not sure there is a proper way to implement this well.
Moving back to UI
If you attach an example plug-in with your workaround, I could have a look to see if there is a better way to implement this.
Hitesh is now responsible for watching bugs in the [Viewers] component area.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
