Bug 79188 - [Viewers] (Table)Viewer should allow update of a known (Table)Item
Summary: [Viewers] (Table)Viewer should allow update of a known (Table)Item
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2004-11-22 10:21 EST by Marcel CLA
Modified: 2019-09-06 16:12 EDT (History)
2 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 Marcel CLA 2004-11-22 10:21:49 EST 
The motivation for this is simple:
There are cases (simplest being a TableViewer) in which the user has a 
TableItem in hand and would like to update changes to it.

The user could of course set any fields of the item, but best way would be to 
do exactly what is done in one of the currently available update methods AFTER 
finding the item.

findItem() takes O(n) worst case if mapping isn't used or can't practically be 
used (large tables - memory waste).

If for example the user would like to update items 10000 to 11000, this might 
take a few seconds since EACH find would go over all the items, but the user 
knows what items he's like to update ...

Implementation is straight forward: check that the item's parent is the 
viewer's control, that the item is not disposed and invoke the update on the 
item as if found by find.

Marcel
Comment 1 Boris Bokowski CLA 2009-11-26 09:49:48 EST 
Hitesh is now responsible for watching bugs in the [Viewers] component area.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:12:37 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.