mirror of
https://github.com/OrcaSlicer/OrcaSlicer.git
synced 2026-10-14 11:21:18 +00:00
packerlschupfer
cb752d38a3
The startup probes for download_path and last_backup_path used the throwing boost::filesystem overloads, so a path that could not be probed at all, such as one whose parent is not searchable, raised filesystem_error instead of falling back. init_download_path() runs from the GUI_App constructor inside GUI_Run()'s try, which left the application showing a message box and exiting with no window and no log file, the throw preceding the log sink. has_restore_data() runs from the queued EVT_RESTORE_PROJECT handler, whose try starts after the call. Five probes in those three functions take the error_code overload instead. Nothing branches on ec, and readable or missing paths are unaffected because both overloads return the same value for them. A new test covers has_restore_data() against a backup directory whose parent has no search permission, and skips on Windows, as root, and where the mode change is refused or not enforced.
OrcaSlicer tests
Building, running and writing tests is documented on the wiki, under How to Test.
Two files here rather than there, because coding agents only read what is in the repository: