Bug 276697 - [Viewers] JFace Custom Tooltip not in sync with Viewer data
Summary: [Viewers] JFace Custom Tooltip not in sync with Viewer data
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-18 09:14 EDT by Frank Rydzewski CLA
Modified: 2019-09-06 16:07 EDT (History)
1 user (show)

See Also:


Attachments
Snippet Demonstrating Issue (3.64 KB, text/x-java)
2009-05-18 09:14 EDT, Frank Rydzewski CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Rydzewski CLA 2009-05-18 09:14:37 EDT
Created attachment 136182 [details]
Snippet Demonstrating Issue

Build ID: M20080911-1700

Steps To Reproduce:
1.  Run the provided Snippet
2.  Hover over a cell
3.  After 2 seconds, the cell's data will change
4.  The tooltip will remain populated with information from the previous data load

More information:
I'm using the custom tooltip logic for the JFace TableViewer in order to extend the amount of time a tooltip is being shown to a user.  A problem I have is that the Viewer's data may be reset by an asynchronous process while the tooltip is being displayed.  This results in the table's cell displaying vastly different information than what is described by the tooltip.

The desirable behavior would be for the Viewer to force any of the table's tooltips to close when it is in the process of re-populating the table's cells.  An alternative would be for the tooltip to be updated with the information for the new cell, but this would seem to be a more complex change.

Snippet to recreate is attached (based on the JFace Snippet 011)

Hover over a cell and after 2 seconds, the cell's data will change, while the tooltip will remain populated with information from the previous data load.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:07:03 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.