Please review and merge #56 before merging this PR.
View model as a simple table.
A new view is added by this PR. It reuses the MamutView framework already used for the BDV and TrackScheme views.
There is two flavors of the table view, that can be found in the Window menu:
The data table shows the full model as a two tables. They list object label, id, feature values and tags. There is one table for vertices:
And one for edges:
The columns are updated live when features are computed or when the tag structure is changed. The rows are changed when the graph is edited.
Selection, Focus and Highlight view.
The table is in sync with the selection model:
And with the focus and the highlight models. The focused object is shown with a special font. The highlighted object with a thick border:
Table navigation.
Using the group locks, the table can receive and send navigation events:
Table editors.
The table lets the user edit tags and the vertex labels:
Table context.
The table is a context listener. When a BDV context is chosen, it only displays the context content at current time-point:
Selection Table.
The second flavor of the table is the selection table. It only displays the current selection and does not edit it:
API changes.
For the context handling, I added a method in the Context interface that returns the current time-point:
public interface Context< V >
{
public Lock readLock();
public Iterable< V > getInsideVertices( final int timepoint );
public int getTimepoint();
}
Tags and feature-based coloring.
There is now tag-set and feature based coloring for the table views:
Please review and merge #56 before merging this PR.
View model as a simple table.
A new view is added by this PR. It reuses the
MamutView
framework already used for the BDV and TrackScheme views.There is two flavors of the table view, that can be found in the
Window
menu:The data table shows the full model as a two tables. They list object label, id, feature values and tags. There is one table for vertices: And one for edges:
The columns are updated live when features are computed or when the tag structure is changed. The rows are changed when the graph is edited.
Selection, Focus and Highlight view.
The table is in sync with the selection model:
And with the focus and the highlight models. The focused object is shown with a special font. The highlighted object with a thick border:
Table navigation.
Using the group locks, the table can receive and send navigation events:
Table editors.
The table lets the user edit tags and the vertex labels:
Table context.
The table is a context listener. When a BDV context is chosen, it only displays the context content at current time-point:
Selection Table.
The second flavor of the table is the selection table. It only displays the current selection and does not edit it:
API changes.
For the context handling, I added a method in the
Context
interface that returns the current time-point:Tags and feature-based coloring.
There is now tag-set and feature based coloring for the table views: