Open ahobeost opened 7 months ago
Is this issue mainly there to document the work-around? Or would you like to see something particular be done? Medium-term, we could maybe get rid of the restriction on the name of the project json <project-name>/<project-name>.json
- I can't think of any good reason for it off the top of my head. Also - but that's really a different issue - I'd like to change the .json
extension of our project JSON files to something more specific, say .pytrngui
, or something. I think that would just be cleaner overall. Also, I sometimes misclick on the placeholders JSON file when I really want to open the project JSON file.
The description of the workaround was the first priority. Ultimately, I would propose a decoupling of such files from the folders they come in. As I cannot think of a reason for this restriction myself, I was thinking it might have been implemented as a reaction to a past bug/issue.
Some users encounter the following when opening an old json file.![image](https://github.com/SPF-OST/pytrnsys_gui/assets/122869062/d7a2483c-74a8-4cd8-a678-8dbc46df1bec)
The main culprit for this is copy/pasting of existing projects by hand. This is best left up to pytrnsys (copy to new folder):![image](https://github.com/SPF-OST/pytrnsys_gui/assets/122869062/b73071d1-6de2-4aee-9010-77003753dc70)
However, for users to recover such a broken GUI diagram, the following steps should fix the problem.