Bug report: Added checkbox for project files and log file. Added extra information in additional information and file uploads.
Changed the textarea to markdown so files can be uploaded.
Updated the placeholder to 4.9 in application version.
Feature request:
Changed textarea to markdown.
One of our engineers found experimentally that his 60mm model was crashing into the gantry. And indeed it is confirmed with the designs of the UM3/S5 print head that the space between the nozzle tip and bottom of the gantry is 57mm. Allowing for some play in the dimensions of the print head and the positioning of the nozzle in the print head, 55mm is agreed as a safe distance.
Fixes issue CURA-8182.
Removed issue-body in bugreport.yaml and featurerequest.yaml
Added config file: can't create a blank issue and added contact link to ultimaker community.
When Cura is starting up, it reads the authentication data from the preferences (cura.cfg). If
the auth tokens have previously been stored in the keyring, it means that their values will be null
in the cura.cfg file. Therefore, on startup, Cura reads the tokens as none from the preferences and
then sets the empty values in the keyring as tokens. This leads to the user being signed off every
time Cura restarts on Mac.
On Windows, the access token was still stored in the preferences, so on startup it was safe. The
refresh token, on the other hand, had the same issue as on Mac, which means that on startup it was
read as None from the cura.cfg and was stored in the keyring as an empty string. This meant that,
even though on startup (on windows) the user was kept signed in, the next time Cura was attempting
to refresh the access token (after 7-8 minutes), it wouldn't be able, since its refresh token was
read as "" from the keyring. Also, if the user would close Cura and reopen it after 10 minutes
(so after the access token had expired) then they would be signed off on windows too.
This commit fixes that by making sure that if the given value of the refresh and access tokens are
empty, then they will not be stored in the keyring.
CURA-8178
There could be an environment error when saving that file because of access rights or insufficient disk space. Catch that error and display an error message to the user. The log then contains more information on exactly why it failed, but the user just knows it fails.
Fixes Sentry issue CURA-21W.
