Bug 186794 - [Viewers] [CellEditors] EditingSupport.getCellEditor(ViewerCell)
Summary: [Viewers] [CellEditors] EditingSupport.getCellEditor(ViewerCell)
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks:
 
Reported: 2007-05-14 10:25 EDT by Peter Centgraf CLA
Modified: 2019-09-06 15:31 EDT (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 Peter Centgraf CLA 2007-05-14 10:25:39 EDT 
The EditingSupport API for initializing and saving values of a CellEditor provide access to a ViewerCell, but other methods are given only the data element for the row.  New variants of getCellEditor() and canEdit() that pass a ViewerCell would enable client code to use a single EditingSupport object per Viewer instead of one per column, since the ViewerCell can be used to distinguish columns.  This would simplify setup code for applications that use dynamic techniques to generate GUIs, for example using JavaBeans introspection.
Comment 1 Boris Bokowski CLA 2008-05-02 14:57:04 EDT 
Mass update - removing 3.4 target. This was one of the bugs I marked for investigation (and potential fixing) in 3.4 but I ran out of time. Please ping on the bug if fixing it would be really important for 3.4, and does not require API changes or feature work.
Comment 2 Boris Bokowski CLA 2009-11-26 09:49:03 EST 
Hitesh is now responsible for watching bugs in the [Viewers] component area.
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:31:49 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.