Metadata field in coordinate.json - bug or not supported?

[sharoncy]

A new "metadata" field has been implemented in the coordinate.json output from Nutil (Nutil v0810). The files no longer open in Meshview. Is there a bug in the way it was implemented, or is it not supported to have extra parameters in Meshview?

[Tevemadar]

Bug in the file. @leuat version.txt may have a line break at its end, then

• loaded into Data::data.version here: https://github.com/Neural-Systems-at-UIO/nutil/blob/b64cf2ef1e59802b5c5800a890ef64b61686816a/mainwindow.cpp#L43
• passed to reports.m_nutil_version here: https://github.com/Neural-Systems-at-UIO/nutil/blob/b64cf2ef1e59802b5c5800a890ef64b61686816a/source/ProcessManager/processmanagerpcounter.cpp#L538
• and gets to the JSON here: https://github.com/Neural-Systems-at-UIO/nutil/blob/b64cf2ef1e59802b5c5800a890ef64b61686816a/source/ProcessManager/report.cpp#L831 A trim() call or its Qt equivalent could presumably do the job, though I couldn't tell if data.version or m_nutil_version is the better place.

[leuat]

Added a trim when loading the string. hopefully this will have fixed the issue, please reopen if not