Community
Participate
Working Groups
Build ID: M20070212-1330 Steps To Reproduce: 1. Create two views with viewers to produce ISelection (StructuredSelection). Call them "View1" and "View2" respectively. 2. In "view2", register its viewer as selection provider. - "getSite().setSelectionProvider(viewer);" 3. In "view1", implements ISelectionListener and add lister to page. - "getSite().getPage().addSelectionListener(this);" - "getSite().getPage().addSelectionListener(View2.ID, this);" // don't use this. it works correctly. 4. run the application. 5. Select an element of view2's viewer. It works correctly. 7. select view1. (deactivate view2) 8. and select different element of view2's viewer. 9. selectionChanged(...) of view1 invoked twice. Once in activation of view2, and selection of new element. 10. But, when i register listener to a specific view. - getSite().getPage().addSelectionListener(View2.ID, this); 11. It don't invoke selectionChanged(...) when view2 is reactivated. It works correctly. 12. Both of them should produce same results. - "getSite().getPage().addSelectionListener(this);" - "getSite().getPage().addSelectionListener(View2.ID, this);" More information: Sorry for my bad English. You can get the working example of this bug from: - http://www.pragmatic.co.kr/QWERT.zip
*** Bug 181149 has been marked as a duplicate of this bug. ***
Could you please attach the example to this bug? For legal reasons, we cannot download code from other places. (By attaching something to a bugzilla entry, you license it under the EPL.)
Created attachment 63037 [details] Example about reported bug. I've attached the example file. (Sorry, I don't about this functionality.) It is a very simple example with two views. You may simply change comment statement on line 69 and 70 of src\qwert\View.java And you can get the difference.
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.
