Summary: | Activities are not Dynamic-Aware | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Zouaoui Anis <anis.zouaoui> |
Component: | UI | Assignee: | Kim Horne <eclipse> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | Keywords: | needinfo |
Version: | 3.2 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Zouaoui Anis
2007-06-22 10:07:58 EDT
Have you asked about this on the eclipse.platform newsgroup before opening a bug? *** Bug 193989 has been marked as a duplicate of this bug. *** *** Bug 193990 has been marked as a duplicate of this bug. *** *** Bug 193994 has been marked as a duplicate of this bug. *** moving to Platform UI The activity support only reacts to changes for the activitySupport extension point, not the activity extension point. I'm wondering if it's simply not a matter of it not doing what you expect it to. When activities come into the system existing realized contributions (views, for instance) wont disappear - activities aren't supposed to be aggressive like that. The pattern bindings should take affect on any new view, editor or perspective you try and open but it should affect those that are already open. Is this what you were expecting? Here is my scenario; My application is connected to an LDAP server. It has a cache that refreshes access rights on views depending on changes on server. I have two main cases: 1- Non authorized views are already opened on the activePage : I'm hiding them using activePage.hideView(IViewReference view). 2- Non authorized views belong to non opened perspectives (not alreay created): I create/register an activity extension point and its pattern binding with the correct regexp. Since my activity is disabled by default, I'm expecting that my activity enter in the game and filter the restricted views (before there creation) when opening perspectives. But the newly created activity has no effect, it was not registered in the activity. It would be appreciated if activities API take in consideration non non-persisted activities. Regards As near as I can tell it's working. Could you attach a sample plug-in that clearly demonstrates the defect please? |