| Modifier and Type | Field and Description |
|---|---|
| public static final String | |
| private final ObservableSet |
| Access | Constructor and Description |
|---|---|
| public |
| Modifier and Type | Method and Description |
|---|---|
| private void | |
| protected void | updateItem(GuiPushToApplication application, boolean empty)
Overrides javafx. The updateItem method should not be called by developers, but it is the best method for developers to override to allow for them to customise the visuals of the cell. |
| DETECTED_APPLICATION_STYLE_CLASS | back to summary |
|---|---|
| public static final String DETECTED_APPLICATION_STYLE_CLASS | |
| detectedApplications | back to summary |
|---|---|
| private final ObservableSet<GuiPushToApplication> detectedApplications | |
| PushToApplicationCell | back to summary |
|---|---|
| public PushToApplicationCell(ObservableSet<GuiPushToApplication> detectedApplications) | |
| updateDetectionStyle | back to summary |
|---|---|
| private void updateDetectionStyle() | |
| updateItem | back to summary |
|---|---|
| protected void updateItem(GuiPushToApplication application, boolean empty) Overrides javafx. Doc from javafx. The updateItem method should not be called by developers, but it is the
best method for developers to override to allow for them to customise the
visuals of the cell. To clarify, developers should never call this method
in their code (they should leave it up to the UI control, such as the
It is very important that subclasses of Cell override the updateItem method properly, as failure to do so will lead to issues such as blank cells or cells with unexpected content appearing within them. Here is an example of how to properly override the updateItem method:
protected void updateItem(T item, boolean empty) {
super.updateItem(item, empty);
if (empty || item == null) {
setText(null);
setGraphic(null);
} else {
setText(item.toString());
}
}
Note in this code sample two important points:
| |