Given some text and an item containing a Point geometry,
the `position` filter replaces occurences of @POS@ or
@POSITION@ with the item's geometry (it has to be lat/lon).
Occurrences of @DMS@ are replaced with the position in
sexagesimal degrees.
This can be used anywhere a Vue filter can. However, we
have used it in the event comments edit dialogue. The positions
are replaced before saving the comment to the database.
A ‘Set colour…’ option is available from the context menu;
it presents a dialogue allowing the user to choose a colour
that will be assigned to that preplot line and used as the
background colour for the corresponding row on the table
(may also be used for other things).
Because there is a good chance that the user may decide to
colour a large number of lines and it is cumbersome to do
it one at a time, a multiple selection option has also been
added. The context menu then shows options which will apply
to all selected rows. At this time only the change colour
option is available, but it can be extended easily.
A hopefully sensible default is applied, but if the
user changes it, the last selected value is saved
in the browsers localStorage.
Preferences are saved per user, project and table. And
per browser, of course, as those are only saved locally.
Closes#41.
If a test passes for all items, show the (single) check mark
and colour it green.
Leaf nodes always have their check mark in the default colour.
Related to #90.
A button in the help dialogue takes the user to the
/feed/… frontend URL, where the latest development
activity is shown, taken from the GitLab RSS feed
for the project.
By default, change just the number of the sequence
being edited. It is checked for conflict with other
planned sequences but not with anything already acquired.
If the user ticks the ‘shift all’ checkbox, then all
planned sequences are shifted by the same amount.
Shows whether the user is logged in and presents
appropriate options according to whether this is
a manual or automatic login (a manual login is
when the user explicitly logs in with a user name
and password).
This is a very basic implementation and doesn't
check that the points are indeed valid.
A proper solution is to request the list of preplots
for that line from the server and validate against those.
