Closed marshr32 closed 1 year ago
In version 2.0.12 and earlier we had a setting that should have placed configurations files according to this: https://github.com/winder/Universal-G-Code-Sender/wiki/Configuration#configuration-files
Unfortunately this setting was wrong which sometimes led to configuration files being placed in random places. The issue is fixed as of 2.0.13 and the configuration files should be retained between upgrades. There is no way for us to automatically migrate them to the new location so they are unfortunately lost...
Closing as "won't fix".
No worries, it's not a huge job to set them again, just thought I'd mention it. Thanks for all your awesome work on UGS 😁
Jan 13, 2023 10:02:40 AM Joacim Breiler @.***>:
In version 2.0.12 and earlier we had a setting that should have placed configurations files according to this: https://github.com/winder/Universal-G-Code-Sender/wiki/Configuration#configuration-files
Unfortunately this setting was wrong which sometimes led to configuration files being placed in random places. The issue is fixed as of 2.0.13 and the configuration files should be retained between upgrades. There is no way for us to automatically migrate them to the new location so they are unfortunately lost...
Closing as "won't fix".
— Reply to this email directly, view it on GitHub[https://github.com/winder/Universal-G-Code-Sender/issues/2119#issuecomment-1380990058], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AVFQ6P3ZHVOMHZA2F2QTF3DWSBWOVANCNFSM6AAAAAATZVWV2Q]. You are receiving this because you authored the thread.[Tracking image][https://github.com/notifications/beacon/AVFQ6P4RGZRUCHAWPMVRUJTWSBWOVA5CNFSM6AAAAAATZVWV2SWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSSKA6GU.gif]
For anyone who sees this later, you can export settings from the old version and import them in the new one. This gets most things sorted.
Version
2.0.13
Hardware / Firmware
GRBL 1.1
What happened
Both 2.0.13 and the latest nightly are not bringing across my visualiser and joystick settings from 2.0.12. Window positions seem to be read OK (but only on the second startup with 2.0.13)
How to reproduce
No response
Operating System
Win 10
Anything else
No response