Fixed a mistake: the directory name should be ${CI_COMMIT_TAG#*-} while the filename use ${INISHELL_VERSION}

Key/values read from the GUI would not contain comments (as there is no
way to enter them in the GUI). Now, when an INI file is read the
comments are stored in the key's properties in addition to the value,
and therefore reproduced on output (but still tied to keys).

When multiple panels are loaded for the same key (e. g. via an
Alternative), any arbitrary one would be chosen. Now the correct active
one is hopefully identified.
This should fix issue #893, but not every possible scenario has been
tested...

I think this was only important when the settings file could fail schema
validation. Now that this is done from outside we do not need to be
careful here anymore. Might lose milliseconds but gets rid of a quite
unneccessary function parameter.

Since some special chars are now allowed in sections, the semantics of
the test file did not fit the result...

The version strings have a "spurious" 'v' in front that had to be removed when extracting the major.minor.patch components

Moreover, the year for the copyright notice has been pushed to 2022

This should now be enabled for all timeseries input plugins

This is a trick that can prove useful in order to select a base METEOPATH and
then pick individual files in subdirectories. The new behavior correctly returns
relative paths to METEOPATH (which only contain the filenames for files that are
directly located in METEOPATH).

Add mechanism to reference keys in the GUI

Closes #878

See merge request !3

Now at least a big chunk of the world's languages should be properly
matched by the regex for "normal" text (it matches any unicode letter
potentially combined with a unicode accentuation mark). A rule has been
introduced for dates, times and sections similar to ini files (as this
has been observed in csv files).

Now the base path panel will fire a signal to the file name panel
when it changes (to update the filename panel's properties).

A simple new check wrongly excluded this...

This should be quite rare (a user selecting a file outside of the base
path), and this way it is consistent that a FilePath with "path" set
does not contribute to the previous locations history. It is
"remembered" anyway in the "path" property.

Now, regardless of the last used folder if a base path is set then
clicking the "open file" button will start at that directory.
Re-add noexcept flag that went missing when I played around with
substitutions there.

This is done with a new "link" button which will highlight the
corresponding panel when pressed.

So far this is used in the FilePath widget to allow the "path" property
to reference other keys.
To build up upon.

This in itself is not so useful yet, but it will be once we can
reference other keys.
Minor enhancement in the schema: Paths can not be previewed, and an
obsolete check was removed.

buergiss authored Jun 07, 2022 and buergiss committed Jun 07, 2022

This reverts commit 2a2ff598.