Bug 1820 - [Viewers] Very hard to implement row-based cell editing (1G9ODD7)
Summary: [Viewers] Very hard to implement row-based cell editing (1G9ODD7)
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All Windows All
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Kevin Haaland CLA
QA Contact:
URL:
Whiteboard:
Keywords: investigate
Depends on:
Blocks:
 
Reported: 2001-10-10 22:19 EDT by Dejan Glozic CLA
Modified: 2002-08-29 17:37 EDT (History)
0 users

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 Dejan Glozic CLA 2001-10-10 22:19:55 EDT 
The platform now allows custom property sheet views linked to the active editor in the similar way to
outline view. However, TableViewer API has been simultaneously changed to make this almost
impossible. 

In the old code, column-related objects (modifiers, cell editors etc.) were grouped into
viewer table column objects. It was good and it was object-oriented. The new code
scattered that functionality into several method calls (setCellEditors, setProperties etc.).
In addition to being a step back (IMHO) because it brings us back into the age of C language,
it made it impossible to override 'activateCellEditor' on the column and provide
row-specific cell editors. 

NOTES:
Comment 1 DJ Houghton CLA 2001-10-24 06:47:00 EDT 
PRODUCT VERSION:

VAME022
Comment 2 Kevin Haaland CLA 2002-01-21 19:12:33 EST 
There are no plans to change the current API in this development cycle.
Comment 3 Randy Giffen CLA 2002-08-01 11:43:13 EDT 
Reopened for investigation. 

Dejan if you have any more specific requests about changes to TableViewer API, 
it would be helpful.
Comment 4 Dejan Glozic CLA 2002-08-01 15:56:30 EDT 
This is a very old defect. I opened it because I needed a property sheet-like 
behaviour in a dialog. Since I opened it, I managed to use the actual property 
sheet component (and use property descriptors) so I don't need this any more. 
You are free to close the defect (although I am still less than 100% happy with 
the column-related calls described above).
Comment 5 Kevin Haaland CLA 2002-08-29 17:37:08 EDT 
Closing based on reporters comments.