inishell issueshttps://gitlabext.wsl.ch/snow-models/inishell/-/issues2024-02-12T21:21:00Zhttps://gitlabext.wsl.ch/snow-models/inishell/-/issues/912Different behavior between snowpack outputs in Alpine3D or in Snowpack applic...2024-02-12T21:21:00ZMathias BavayDifferent behavior between snowpack outputs in Alpine3D or in Snowpack applicationsGoing into "Output" > "PROF_WRITE = TRUE" from the Snowpack or the Alpine3D applications does not show the same content: in Snowpack, PROF_ID_OR_MK and PROF_AGE_OR_DATE are shown, not in the Alpine3D applicationGoing into "Output" > "PROF_WRITE = TRUE" from the Snowpack or the Alpine3D applications does not show the same content: in Snowpack, PROF_ID_OR_MK and PROF_AGE_OR_DATE are shown, not in the Alpine3D applicationhttps://gitlabext.wsl.ch/snow-models/inishell/-/issues/910Missing globe icon for coordinates in a textfield2024-03-13T10:29:34ZMichael ReiseckerMissing globe icon for coordinates in a textfieldSomewhere along the line the button that leads to an online map tool went missing for valid coordinates.Somewhere along the line the button that leads to an online map tool went missing for valid coordinates.Michael ReiseckerMichael Reiseckerhttps://gitlabext.wsl.ch/snow-models/inishell/-/issues/907implement a system to distribute versionned xml files2024-03-11T13:54:01ZMathias Bavayimplement a system to distribute versionned xml filesWhen a software that relies on Inishell gets some new options, they are quickly implemented in the XML files. But the problem is that most users will rely on pre-compiled versions of Inishell that are irregularly released. Thus we need t...When a software that relies on Inishell gets some new options, they are quickly implemented in the XML files. But the problem is that most users will rely on pre-compiled versions of Inishell that are irregularly released. Thus we need to find a robust way to distribute updates to the XML files that match the exact software version that a given user has. This means:
* the XML files need to clearly show the user which version they are;
* there must be an easy way for the user to update the XML files independently of the precompiled Inishell binaries
The best way would be that each software distributes its XML files and that Inishell can find those automatically on the system. The said XML files must have some version information that could be shown in Inishell. The tricky part (as if the previous was not tricky enough) is to support cases such as Snowpack using MeteoIO where the user might update MeteoIO but keep another version of Snowpack and so the XML includes should pick the right combination of XML files from MeteoIO and Snowpack...leiberspleibersphttps://gitlabext.wsl.ch/snow-models/inishell/-/issues/902Wrong numbering in preview editor2023-07-07T12:18:42ZMathias BavayWrong numbering in preview editorSomehow we have messed up the title property of the tabs in the preview editor: now when opening multiple times a preview, the number gets incremented but on all tags instead of keeping their original names on all older tabs and only inc...Somehow we have messed up the title property of the tabs in the preview editor: now when opening multiple times a preview, the number gets incremented but on all tags instead of keeping their original names on all older tabs and only incrementing the number on the newly opened tab...https://gitlabext.wsl.ch/snow-models/inishell/-/issues/901Preview window handling comments2022-11-09T08:04:54ZMathias BavayPreview window handling commentsNice funny experiment: edit a text filed in Inishell, open in the preview editor and comment the line. Then choose "save and load in...". Interestingly, the field in Inishell keeps its value and is thus not commented out...Nice funny experiment: edit a text filed in Inishell, open in the preview editor and comment the line. Then choose "save and load in...". Interestingly, the field in Inishell keeps its value and is thus not commented out...https://gitlabext.wsl.ch/snow-models/inishell/-/issues/900Saving edits from preview window2022-11-09T08:04:53ZMathias BavaySaving edits from preview windowCurrently the default behavior consists in saving the file but not loading it back into Inishell. I think this is counter-intuitive (Charles came to my office for this "weird behavior") and instead the default should be to save and load ...Currently the default behavior consists in saving the file but not loading it back into Inishell. I think this is counter-intuitive (Charles came to my office for this "weird behavior") and instead the default should be to save and load in Inishell. DO you have any reason not to do it this way? (or should we even drop the ability not to load edits after saving?)https://gitlabext.wsl.ch/snow-models/inishell/-/issues/899Inishell for Web2022-10-03T09:52:39ZMichael ReiseckerInishell for WebFor the record, here are the steps which gave me some results:
```bash
git clone https://github.com/emscripten-core/emsdk.git
cd emsdk
./emsdk install 3.1.14
./emsdk activate 3.1.14
```
* Use Qt Maintenance tool to install WebAssembly ...For the record, here are the steps which gave me some results:
```bash
git clone https://github.com/emscripten-core/emsdk.git
cd emsdk
./emsdk install 3.1.14
./emsdk activate 3.1.14
```
* Use Qt Maintenance tool to install WebAssembly toolchain
* In QtCreator -> Preferences -> Devices -> WebAssembly point SDK path to emsdk root directory
* The emscripten version must match the one Qt was built with, QtCreator will give a warning if this is not the case (and indeed installing "latest" did not work properly)
```
python3 -m http.server
firefox localhost:8000
--> navigate to inishell.html
```
Restrictions:
- For a quick try I could not use the CMake build. An error was thrown and the first Internet solution did not work, so I switched to qmake and it succeeded.
- I could not do it with command line tools, although I'm sure somebody else could. I was happy to let QtCreator pick all the right compiler flags for me.
- All references to QProcess need to be removed, everything else is fine.
- Unable to open local files (XMLs must be bundled I suppose), but building bundled XMLs works (as seen in the help browser). But how to open local inis?
![main](/uploads/ef72b7111d48a377c052d7c8f2323615/main.png)
![help](/uploads/6fb11b22fd2ff56f3b8fc251062d7c89/help.png)https://gitlabext.wsl.ch/snow-models/inishell/-/issues/896GUI cannot find station files2023-09-21T08:53:51ZFierzGUI cannot find station filesRunning on MacBook Pro with Apple M1 Pro (masOS Monterey Version 12.4)
When running the latest version (commit 2d179ecc) the GUI does not find the station files ("File does not exist" indicated in GUI). However, ini-file runs w/o problem...Running on MacBook Pro with Apple M1 Pro (masOS Monterey Version 12.4)
When running the latest version (commit 2d179ecc) the GUI does not find the station files ("File does not exist" indicated in GUI). However, ini-file runs w/o problems with MeteoIO.
Sorry, I have no screen shot as I crashed my inishell (Qt problem while compiling)!Mathias BavayMathias Bavayhttps://gitlabext.wsl.ch/snow-models/inishell/-/issues/894Preserve comments2022-07-11T21:16:57ZMathias BavayPreserve commentsAlthough normally Inishell should keep the comments present in an ini file when reading it, there are some cases where this is not the case. So far, I don't see the difference between an ini file where all comments are preserved and one ...Although normally Inishell should keep the comments present in an ini file when reading it, there are some cases where this is not the case. So far, I don't see the difference between an ini file where all comments are preserved and one where this is not the case...
io_statfilter.ini is properly read while io_before.ini gets striped of all its comments.
[io_before.ini](/uploads/582b6b3263e61e03b01dce3ab283c1a6/io_before.ini)
[io_statfilter.ini](/uploads/21742db6ef990ecf6074d4ea413e2224/io_statfilter.ini)Michael ReiseckerMichael Reiseckerhttps://gitlabext.wsl.ch/snow-models/inishell/-/issues/892Passing special character file names to external programs fails2022-06-06T21:31:50ZMichael ReiseckerPassing special character file names to external programs failsFor example, if I select `testüng.ini` in a FilePath, then preview it, then context-click on "open in external editor" I get the following error due to character encodings:
> gio: file:///home/mir/Desktop/test%25C3%25BCng.ini: Error whe...For example, if I select `testüng.ini` in a FilePath, then preview it, then context-click on "open in external editor" I get the following error due to character encodings:
> gio: file:///home/mir/Desktop/test%25C3%25BCng.ini: Error when getting information for file “/home/mir/Desktop/test%C3%BCng.ini”: No such file or directory
See https://doc.qt.io/qt-5/qurl.html#ComponentFormattingOption-enumhttps://gitlabext.wsl.ch/snow-models/inishell/-/issues/891DEM Input Key for 2D-Interpolations is missing2022-05-18T23:30:11ZAltenbacDEM Input Key for 2D-Interpolations is missingThere is no option in INIshell Input to select the DEM-file necessary to use some 2D interpolations (which for example calculate slope and curvature). It has still to be edited manually in the Ini-File.There is no option in INIshell Input to select the DEM-file necessary to use some 2D interpolations (which for example calculate slope and curvature). It has still to be edited manually in the Ini-File.https://gitlabext.wsl.ch/snow-models/inishell/-/issues/882Section tooltips2021-06-05T21:20:44ZMichael ReiseckerSection tooltipsSections could accept a `<help>` node like everything else and show that as a tooltip for its tab.Sections could accept a `<help>` node like everything else and show that as a tooltip for its tab.https://gitlabext.wsl.ch/snow-models/inishell/-/issues/881Unify GUI and Workflow panels2022-06-16T15:04:09ZMichael ReiseckerUnify GUI and Workflow panelsNow that XMLs can be built anywhere, it should be investigated if the Workflow could meaningfully utilize the main panel parser.
The other way around, Inishell could then be a full canvas describing experiments where for example buttons ...Now that XMLs can be built anywhere, it should be investigated if the Workflow could meaningfully utilize the main panel parser.
The other way around, Inishell could then be a full canvas describing experiments where for example buttons to run the experiments could be integrated within the main text describing a simulation.https://gitlabext.wsl.ch/snow-models/inishell/-/issues/880Allow multi-language help texts2022-06-27T20:00:43ZMichael ReiseckerAllow multi-language help textsIn the future there may be efforts to utilize that we can easily parse our XMLs for help texts and feed them through e. g. DeepL.
Maybe check the set language string of Inishell (e. g. "de") and then display <help_de> if available?In the future there may be efforts to utilize that we can easily parse our XMLs for help texts and feed them through e. g. DeepL.
Maybe check the set language string of Inishell (e. g. "de") and then display <help_de> if available?Michael ReiseckerMichael Reiseckerhttps://gitlabext.wsl.ch/snow-models/inishell/-/issues/879Help system overhaul2022-06-27T20:00:43ZMichael ReiseckerHelp system overhaulRevisiting the help files (user guide and developer help) is overdue and now luckily a few hours are available.
- [x] New text panel tailored to showing Inishell syntax
- [x] XML syntax highlighting
- [x] New panel to show images
- [ ] ...Revisiting the help files (user guide and developer help) is overdue and now luckily a few hours are available.
- [x] New text panel tailored to showing Inishell syntax
- [x] XML syntax highlighting
- [x] New panel to show images
- [ ] User guide
- [ ] Describe new features and appearance
- [ ] Clarify workflow
- [ ] Dev help
- [x] Table of content
- [ ] Uniform description of panels with options
- [ ] Copyable code snippets
- [x] Symbol table
- [x] Solarized color pickerhttps://gitlabext.wsl.ch/snow-models/inishell/-/issues/877no possibility to revert to default2022-07-07T15:44:21ZMathias Bavayno possibility to revert to defaultOnce a value has been entered in a field, it is not possible to revert back to the default value (ie have the key being skipped in the generated ini file).Once a value has been entered in a field, it is not possible to revert back to the default value (ie have the key being skipped in the generated ini file).https://gitlabext.wsl.ch/snow-models/inishell/-/issues/876Numeric INI values are sometimes not displayed correctly2023-09-21T20:14:26ZMichael ReiseckerNumeric INI values are sometimes not displayed correctlyCurrently on my computer there is a bug where in some circumstances numbers coming from an INI file are not displayed correctly. This is very bad, because e. g. a MIN filter with minimum = 0 does not work.
The reason is a culmination of...Currently on my computer there is a bug where in some circumstances numbers coming from an INI file are not displayed correctly. This is very bad, because e. g. a MIN filter with minimum = 0 does not work.
The reason is a culmination of annoyances we unfortunately have little control over:
1) The whole thing with a QSpinBox not supporting empty values, but we have to support them. Now we hide the value by setting the font color to the background color, but this is a hack and needs to be handled with care.
2) Since the font color is a matter of stylesheets, this is inherently problematic. Within submodules we need to apply them from "outside" with a tiny delay, see e. g. [Number.cc@514](https://gitlabext.wsl.ch/snow-models/inishell/-/blob/v2.0.6/src/panels/Number.cc#L514). Otherwise the change is just not registered. For me here increasing this to 3 ms solves the bug but obviously this can not be the right way. Will try to commit a minimal effort hotfix though when the new repo is open. (`qApp.processEvents()` instead of the timer does not help.)
3) If a QSpinBox is set to the same value it already displays, no "changed" signal is emitted, so in this case (an INI delivers the same value as currently displayed) we need to trigger the signal manually. This in itself is not really a problem, but it convolutes the whole thing with more special cases. Since a QSpinBox must have a number set, this can also apply to hidden values.
The question now is if there is a better way for all of this...https://gitlabext.wsl.ch/snow-models/inishell/-/issues/871XML files provided by the models2023-09-12T11:56:46ZMathias BavayXML files provided by the modelsIt would be much more logical if the numerical models relying on Inishell for the configuration to release their XML files themselves. Then a user of, say MeteoIO, would always have an up-to-date XML file for his/her version of MeteoIO.
...It would be much more logical if the numerical models relying on Inishell for the configuration to release their XML files themselves. Then a user of, say MeteoIO, would always have an up-to-date XML file for his/her version of MeteoIO.
In this cases, a few issues must be tackled:
* Inishell must find the applications and then find their XML files -> maybe a predefined list of applications names, then building fixed search paths to search for the applications and then a few fixed paths to search for XML files within each application;
* Inishell must offer a way for the user to add extra applications or directly extra paths to search for XML files (this one already exists);
* Inishell must then handle includes across applications.leiberspleibersphttps://gitlabext.wsl.ch/snow-models/inishell/-/issues/867Save --> Save As2021-01-18T20:19:52ZMichael ReiseckerSave --> Save AsCurrently the ""Save"" menu is rightfully disabled when Inishell can not know a file name yet, and ""Save as..."" must be used.
Other programs switch to ""Save as"" automatically here, which may be considered a small usability enhancement.Currently the ""Save"" menu is rightfully disabled when Inishell can not know a file name yet, and ""Save as..."" must be used.
Other programs switch to ""Save as"" automatically here, which may be considered a small usability enhancement.https://gitlabext.wsl.ch/snow-models/inishell/-/issues/835The precision of numeric fields should accomodate what the user provides2021-05-05T09:37:03ZMathias BavayThe precision of numeric fields should accomodate what the user providesThe problem is that by filters, the precision depends on the meteo parameter more than the filter itself (ex: a MAX on TA is fine with no decimal while on RH it will require 2 decimals at least).
The way to go would be to accept whatev...The problem is that by filters, the precision depends on the meteo parameter more than the filter itself (ex: a MAX on TA is fine with no decimal while on RH it will require 2 decimals at least).
The way to go would be to accept whatever precision the user provides in his/her input.