| Summary: | [Viewers] [JFace] setUseHashLookUp() and multiple occurrences of same domain object in TreeViewer | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Mário Guimarães <mljrg> |
| Component: | UI | Assignee: | Boris Bokowski <bokowski> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | ob1.eclipse |
| Version: | 3.4.1 | Keywords: | helpwanted |
| Target Milestone: | 3.5 M5 | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
|
Description
Mário Guimarães
Do you have a suggestion how the Javadoc should be changed? I suggest the following javadoc: --------------- Configures whether this structured viewer uses an internal hash table to speed up the mapping between elements and SWT items. This must be called before the viewer is given an input (via setInput). Note: when using an ITreePathContentProvider with a TreeViewer, the internal hash table should be enabled to support the update and refresh of multiple occurrences of the same domain objects in the viewer. --------------- Regard that I'm not aware of other uses of an internal hash table. However, if they exist, they should be documented too. I decided to instead copy the following paragraph from AbstractTreeViewer into the JavaDoc for TreeViewer as well: * <p> * As of 3.2, TreeViewer supports multiple equal elements (each with a * different parent chain) in the tree. This support requires that clients * enable the element map by calling <code>setUseHashLookup(true)</code>. * </p> Would you have found this if it had been on TreeViewer (and not just the superclass)? Maybe, but to be sure, this feature should also be documented in the javadoc for setUseHashLookup() and ITreePathContentProvider. |