It seems that the LiveReload system does not trigger in certain circumstances.
I'm on Windows and the path that the system uses points to D:\Spiele\steamapps\common\Delver\delver, which is the top-level folder containing e.g. /generator etc.
DelvEdit is executed with a working directory of ${workspaceFolder}/../../Spiele/steamapps/common/Delver/delver, which points to the same path.
The system is triggered however, when changing a file in the top-level folder.
Case 1
Try editing section.dat of Dungeon
LiveReload is not triggering an update
Case 2
Try renaming a folder under /generator
LiveReload is not triggering an update
Additional Features
[ ] Allow trigger to happen also on mod changes
[ ] Use an ActionListener pubsub implementation for propagating reloads
PythooonUser
commented
4 years ago
It seems that the LiveReload system does not trigger in certain circumstances.
I'm on Windows and the path that the system uses points to
D:\Spiele\steamapps\common\Delver\delver, which is the top-level folder containing e.g./generatoretc.DelvEdit is executed with a working directory of
${workspaceFolder}/../../Spiele/steamapps/common/Delver/delver, which points to the same path.The system is triggered however, when changing a file in the top-level folder.
Case 1
section.datof DungeonCase 2
/generatorAdditional Features
ActionListenerpubsub implementation for propagating reloads