WSL/SLF GitLab Repository

  1. 08 Feb, 2021 1 commit
  2. 30 Jan, 2021 1 commit
  3. 29 Jan, 2021 1 commit
  4. 28 Jan, 2021 1 commit
  5. 22 Jan, 2021 1 commit
    • Michael Reisecker's avatar
      Scroll to flashed help index, better performance · c16ea84e
      Michael Reisecker authored
      When opening context help the topic can now be anywhere on the page.
      Also: QTabWidget::clear() clears the tabs but does not delete
      anything... oops. Now we do this manually potentially saving big amounts
      of memory and lookups.
      c16ea84e
  6. 10 Dec, 2020 1 commit
    • Mathias Bavay's avatar
      A bug has been found where the user manually edits the run path in a workflow... · 13c391f2
      Mathias Bavay authored
      A bug has been found where the user manually edits the run path in a workflow and makes it invalid...
      
      The problem is that the command that should run does not run and we show
      an error message saying that the command could not be found when it fact
      it was an invalid run path... A hacky way of catching this kind of
      errors has been implemented, but it wold be better to be able to show an
      error message in the log window instead of only in the status bar.
      13c391f2
  7. 29 Aug, 2020 2 commits
  8. 19 Aug, 2020 1 commit
  9. 28 May, 2020 1 commit
    • Mathias Bavay's avatar
      Fixed a very nasty bug · 30f07dd0
      Mathias Bavay authored
      After hours of fighting, I managed to implement a workaround. The
      problem is that when creating an ini file from scratch (for example for
      MeteoIO) and running it directly (after saving it to a file), the
      workflow output path can not be read (${key:OUTPUT::METEOPATH} can never
      be read, it is actually empty). This comes from the fact that
      MainWindow.getINI() does not contain the same keys as in the INIParser
      just after saving... So the dirty fix is to copy this content to
      MainWindow.ini_ just after saving so the WorkFlow object has access to
      the user provided configuration. Hopefully, a clean fix can be developed
      at some point.
      30f07dd0
  10. 17 Mar, 2020 1 commit
  11. 10 Mar, 2020 2 commits
  12. 07 Mar, 2020 1 commit
  13. 06 Mar, 2020 1 commit
    • Mathias Bavay's avatar
      Tweaking the output and application paths. · 4b4cf566
      Mathias Bavay authored
      Unfortunately, the Snowpack provided examples require to run on level higher than the config files. This is now possible but made me realize that relative paths should not be expanded against the path of the ini file but against the current working directory (the other convention makes sense for include files but not for the inputs/outputs)
      4b4cf566
  14. 05 Mar, 2020 2 commits
  15. 04 Mar, 2020 6 commits
  16. 03 Mar, 2020 1 commit
  17. 02 Mar, 2020 1 commit
  18. 01 Mar, 2020 2 commits
  19. 29 Feb, 2020 5 commits
  20. 28 Feb, 2020 3 commits
  21. 27 Feb, 2020 1 commit
  22. 26 Feb, 2020 1 commit
    • Mathias Bavay's avatar
      Now proper hints for application search paths are provided · 822ee3ad
      Mathias Bavay authored
      This means that the PATH variable receives more locations where to look for the application that should be launched by the workflow. It is assumed that the workflow name is also used (all lowercase) in some potential directory names that could contain the executable for the said application.
      822ee3ad
  23. 25 Feb, 2020 1 commit
    • Mathias Bavay's avatar
      Improvements to the workflows · bc19c8cf
      Mathias Bavay authored
      Now the user can chose to either use as working directory the one of the ini file or the current one. The first elements of an enhanced way to find applications even not in the PATH have been laid out, it will now be customized for each platforms.
      bc19c8cf
  24. 24 Feb, 2020 2 commits