Bugzilla – Full Text Bug Listing
| Summary: | [CommonNavigator] Project Explorer does not refresh or function like the Navigator View | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Mark Melvin <mark.melvin> |
| Component: | UI | Assignee: | Francis Upton IV <francisu> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.3 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Mark Melvin
Apparently my 4MB movie is too big. I'll see what I can do to attach a smaller version. You might be able to see it here: http://picasaweb.google.com/mark.melvin/MyVideos/photo?authkey=TT8u8soz0xg#5072687202346169042 After picasaweb is finished cranking on it. I think it is currently trying to convert it. Hopefully it will be available shortly. Note: #1 is logged previously as bug #189682. Feel free to add to CC. I CC'd myself on bug #189682 but I don't think this is the same issue. What I am describing here is the the actions are not contributed or visible *at all* in the Project Explorer. Bug #189682 is talking about the JDT Package Explorer (a different view) and action *enablement* as far as I can tell. (In reply to comment #4) > I CC'd myself on bug #189682 but I don't think this is the same issue. What I > am describing here is the the actions are not contributed or visible *at all* > in the Project Explorer. Bug #189682 is talking about the JDT Package Explorer > (a different view) and action *enablement* as far as I can tell. Hi Mark, There's also bug #189493 which is perhaps a better match to you what you were commenting on. With respect to bug #189682, what its describing is that the menu bar action doesn't enable on its own for the project explorer, but curiously if you go to the package explorer then *back to* the project explorer the action does enable. Hi Kevin. I'll agree that bug #189493 describes the same behaviour with regards to the "Go Into" actions being missing described in my point #1. This bug is still valid for the refresh issues described in my original points #2 and #3, however. Is the common navigator being worked on anymore? There a TON of issues against it with relatively no response. I'd like to move away from the Navigator View and start contributing custom content to the Project Explorer view, but the number of show-stopping bugs against it (like this one) doesn't really make it usable yet. Are you looking for help? For me this bug is HUGE and is still the reason we cannot move our product to the Project Explorer view. Is there any plan to look at this at all?? Once again, you can clean and re-build a project, or cause some other type of workspace modification and the Project Explorer simply refuses to refresh. I can easily get it into this state within a few seconds and refreshing projects and working sets in the view does absolutely nothing. It basically is showing you completely false information. Files that don't even exist in the workspace! And there seems to be no way to get it out of this mode short of closing and re-opening Eclipse, which is ridiculous. In fact - I was just trying to prove this with another movie or screenshot and in Eclipse 3.4M5 I cannot get the Project Explorer view to show anything at all when working sets are selected! Every other view - Navigator, Package Explorer, etc. all show working sets just fine, but the Project Explorer view is completely empty and I cannot get it to show me anything! Turns out - my working sets are "Java Working Sets" and I cannot find a way to get them to appear in the Project Explorer view at all!! Why can the simple Navigator view cope with this, but not the uberific Project Explorer!?!? Hmm... it is possible that #3, by far the worst bug of the three here has been fixed with the fix for bug 213891. I'll give it a try when 3.4.1 is out. (In reply to comment #7) > Is the common navigator being worked on anymore? There a TON of issues against > it with relatively no response. I'd like to move away from the Navigator View > and start contributing custom content to the Project Explorer view, but the > number of show-stopping bugs against it (like this one) doesn't really make it > usable yet. > Are you looking for help? > Yes we are looking for help, I'm the committer on it, but I'm only part time. As you can see I have gotten to many of the more critical issues for 3.4.1, but there is still quite a bit of work to be done to get the CN to be more robust and that's what I would like to have the focus on for 3.5. One of the areas we need help in is expanding the current test suite. It's very small and can use lots of additional test cases. Let me know if you are interested in working on any area of the CNF and I would be happy to guide you. I'm hoping that both issues #2 and #3 are solved by the many fixes that went into 3.4.1. (I'm interpreting issue #2 to be just a part of refresh problems), let me know if I'm wrong. (In reply to comment #9) > Hmm... it is possible that #3, by far the worst bug of the three here has been > fixed with the fix for bug 213891. I'll give it a try when 3.4.1 is out. > Can you report on the results of this? Hi Francis, I tried to reproduce the issue in 3.4.1 and could not, so I assumed that the fix for bug 213891 resolved the issue. To prove this I tried to reproduce the issue in Eclipse 3.4.0...and also failed. Hrmph. So I was hoping to try and pinpoint exactly what *did* fix the issue, but haven't had the time. In any case, I haven't been able to reproduce my original refresh issue on either 3.4 or 3.4.1 so I guess until further notice it can be considered fixed. ;) Seems like it got fixed somewhere along the line. I just saw it again on an Eclipse 3.4.0, upgraded to 3.4.1 and the problem went away. I'll continue to monitor it on 3.4.1 for awhile in case it is a transient thing. |