Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 351142 - [Workbench] addSelectionListener(ISelectionListener listener) and addSelectionListener(String partId, ISelectionListener listener) have incosistent behaviour
Summary: [Workbench] addSelectionListener(ISelectionListener listener) and addSelectio...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.6.1   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-05 03:51 EDT by Ralph Gerbig CLA
Modified: 2019-11-14 03:17 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ralph Gerbig CLA 2011-07-05 03:51:18 EDT 
Build Identifier: 20100917-0705

I have a GMF editor to which I want to add a SelectionListener. addSelectionListener(ISelectionListener listener)works as expected. When using addSelectionListener(String partId, ISelectionListener listener) my SelectionListener only reacts if the diagram was not open when eclipse starts. In this case I have to close and open the diagram to get things working. If I use a NullSelectionListener this one is only called when the diagram is closed but not on selection changes. Here again I have to close and open the diagram.

Reproducible: Always
Comment 1 Lars Vogel CLA 2019-11-14 03:17:02 EST 
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.