Describe the bug
PathPlanner app/GUI does not automatically write new .path files unless we explicitly edit the file to change e.g., some waypoint. This means the "New Path" and "Duplicate path" GUI commands do not write new .path files to reflkect those options, unless we manually enter the editing pane and change at least one element of the path itself. Similarly, editing the path name in the GUI does not cause the file to save.
(This doesn't apply to Autos, which seem to have exactly the expected GUI behavior.)
To Reproduce
Steps to reproduce the behavior:
- Go to the PathPlanner GUI
- Click on any existing path file
- Hit "Duplicate" to duplicate the path
- Change the path name in the main project viewer
- Look to see if the new path files are present in the repository
Expected behavior
The .path files in the file system mirror the paths shown in the GUI project browser, both before and after duplicate and/or rename.
Versions: (please complete the following information):
Describe the bug
PathPlanner app/GUI does not automatically write new .path files unless we explicitly edit the file to change e.g., some waypoint. This means the "New Path" and "Duplicate path" GUI commands do not write new .path files to reflkect those options, unless we manually enter the editing pane and change at least one element of the path itself. Similarly, editing the path name in the GUI does not cause the file to save.
(This doesn't apply to Autos, which seem to have exactly the expected GUI behavior.)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The .path files in the file system mirror the paths shown in the GUI project browser, both before and after duplicate and/or rename.
Versions: (please complete the following information):