| Class and Description |
|---|
| org.eclipse.nebula.widgets.nattable.edit.ActiveCellEditorRegistry
Storing the editor in a global registry has certain drawbacks as
outlined in the documentation and the bug report. In order to
resolve that the active editor is now an instance field of the
table. The methods provided in here to register or retrieve the
editor are available on the table itself.
Therefore this registry is obsolete and should not be used any
more.
|
| org.eclipse.nebula.widgets.nattable.ui.matcher.BodyCellEditorMouseEventMatcher |
| org.eclipse.nebula.widgets.nattable.edit.action.CellEditDragMode
since 1.6 the intention of this drag mode is obsolete. The correct
handling is done inside
DragModeEventHandler |
| org.eclipse.nebula.widgets.nattable.group.config.ColumnGroupMenuItemProviders
Use
MenuItemProviders or the PopupMenuBuilder
directly |
| org.eclipse.nebula.widgets.nattable.extension.glazedlists.GlazedListsDataProvider
Use a default
ListDataProvider instead as the performance
boost can not be verified with current Java and GlazedLists
implementations and as this implementation is not thread-safe it
introduces more issues than it tries to solve. |
| org.eclipse.nebula.widgets.nattable.selection.RowSelectionPreserver
Use SelectionLayer.setSelectionModel(new RowSelectionModel(...))
instead
|
| org.eclipse.nebula.widgets.nattable.selection.event.SelectionLayerStructuralChangeEventHandler
ISelectionModel is now itself a ILayerEventHandler
|
| Field and Description |
|---|
| org.eclipse.nebula.widgets.nattable.fillhandle.action.FillHandleDragMode.startIndex |
| org.eclipse.nebula.widgets.nattable.extension.nebula.richtext.RichTextCellEditor.toolbarConfiguration
Only exists for backwards compatibility to avoid API
breakage. The
RichTextEditorConfiguration should be
used instead! |
Copyright © 2019. All rights reserved.