Community
Participate
Working Groups
Build Identifier: The documentation of the class notes "Clients may customize by subclassing and overriding update(ViewerCell)." But within that method, a subclass would need to access the attributeMaps variable, just as the default update(ViewerCell) method does. A subclass can create it's own attributeMaps varriable, override the constructor ObservableMapCellLabelProvider(IObservableMap[] attributeMaps), and the dispose() method to get the desired functionality, but that requires overriding two methods that will see no changes in the subclass. Reproducible: Always
(In reply to comment #0) > Build Identifier: > > The documentation of the class notes "Clients may customize by subclassing and > overriding update(ViewerCell)." But within that method, a subclass would need > to access the attributeMaps variable, just as the default update(ViewerCell) > method does. A subclass can create it's own attributeMaps varriable, override > the constructor ObservableMapCellLabelProvider(IObservableMap[] attributeMaps), > and the dispose() method to get the desired functionality, but that requires > overriding two methods that will see no changes in the subclass. > > Reproducible: Always I forgot to state the obvious that attributeMaps should be marked protected to resolve this.
Ryan, which version of DataBinding are you using? The attributeMaps fields of the ObservableMapCellLabelProvider and ObservableMapLabelProvider classes have already been changed to be protected as part of bug 302860. *** This bug has been marked as a duplicate of bug 302860 ***
