Summary: | [Viewers] DeferredContentProvider doesn't update UI for changed elements | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Jeff Magill <jeff_magill> |
Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | P5 | Keywords: | helpwanted |
Version: | 3.2 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: | stalebug | ||
Bug Depends on: | |||
Bug Blocks: | 509006 | ||
Attachments: |
Description
Jeff Magill
2005-11-18 18:14:46 EST
Created attachment 30271 [details]
testcase with a small application
this is the testcase mentioned in the bug description
Created attachment 30273 [details]
ConcurrentTableUpdator workaround
added the updateCleared method
Created attachment 30274 [details]
BackgroundContentProvider workaround
the invocation of ConcurrentTableUpdator#updateCleared is in this file
I found something else in the ConcurrentTableUpdator that seems to cause SetData to be ignored when the table should be updated. The ConcurrenTableUpdator#replace() method references the sentObjects array to decide if it's already sent the table the new data. However, there is a loop where it is using the wrong index into the sentObjects array. I will create another attachment that illustrates this. Search for the FIXME tag in the replace method. I attached another testcase that helps in identifying this particular version of the update problem. Run the testcase in the elements_not_updated attachment: - Click on the "Text" column header to sort by that column. - Scroll down to item "text_5000" and select it. - Hit the "Change to->" button over on the left side. Created attachment 31992 [details]
Testcase for larger sets of items and the sentObjects issue
Created attachment 31993 [details]
FIXME tag identifies suspicious code
The third FIXME tag is placed at the spot where I question the index usage. The second FIXME tag is at the place where I think the pendingClears array is being resized improperly.
Hitesh is now responsible for watching bugs in the [Viewers] component area. 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. -- The automated Eclipse Genie. |