Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 244918

Summary:	[Viewers] [JFace][ColumnViewerEditor] Allow different ColumnViewerEditorActivationStrategies
Product:	[Eclipse Project] Platform	Reporter:	Sebastian Fuchs <spacehorst>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	bokowski, tom.schindl
Version:	3.4
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Sebastian Fuchs

2008-08-22 03:53:52 EDT

Current implementation allows registration of only 1 EditorActivationStrategy. When using different CellEditors in one ColumnViewer, e.g. Text- and ComboCellEditors, clients need different activation strategies for each type.

A current workaround is to hold the different logic of the ActivationStrategies in your master Activationstrategy and delegate the activation decission to the correct one by investigating FocusCell.
Unfortunately
isEditorActivationEvent(ColumnViewerEditorActivationEvent event)
is protected so you cannot reuse ColumnViewerEditorActivationStrategy for your logic, instead you have write your own interface or similar.

Comment 1 Thomas Schindl

2010-01-28 17:12:17 EST

multi change because of intenion of stepping back as platform-ui committer

Comment 2 Eclipse Webmaster

2019-09-06 16:14:54 EDT

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.

Comment 3 Eclipse Genie

2021-10-19 18:33:15 EDT

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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.