Now it calls checkToken correctly. However now this _parseJWT is not called correctly since there are things calling this one in an attempt to be synchronous again.
There is the additional issue that we can't call getAccessTokenUsingRefreshToken synchronously now, because this runs on the main thread and it will then block the main thread until the request is made, which is never because the request is also done on the main thread via Qt's event loop.
Contributes to issue CURA-8539.
This involves returning the user profile via a callback.
No longer use the Requests library, which doesn't properly use the SSL certificates locally on the computer like the QNetworkManager does.
Contributes to issue CURA-8539.
The QImage.pixel() function should only get integers.
In theory an input position of -2,-2 would get rounded to 0 now. However that shouldn't occur because the user can't click outside of the window. And if it does occur, it's not really a problem either that it's theoretically picking a position inside of the window when you click slightly next to it.
Fixes#10785.
We removed the limit of density for the first bridging layer, but there are more settings for that, and there's a similar arbitrary limit for flow in place.
Contributes to issue CURA-8639 and #10736.
This is a re-write from a previous attempt. Instead of requests, which doesn't properly use SSL certificates installed on the computer among other things, we'll now use the HttpRequestManager which uses QNetworkManager under the hood and properly uses system settings.
The QNetworkManager is asynchronous which would normally be very nice, but due to the nature of this call we want to make it synchronous so we'll use a lock here.
Contributes to issue CURA-8539.
In the fdmprinter definition the 'infill' is created by 999999 bottom layers to change to infill pattern to lines. This hack is reverted for ultimaker printers. More info: PP-25
In the fdmprinter definition the 'infill' is created by 999999 bottom layers to change to infill pattern to lines. This hack is reverted for ultimaker printers. More info: PP-25
We can't change this index to an integer, because varying variables can't be integer, even though this variable will only really be tested on vertex level. Not sure if varying was the right choice, but I don't want to change that.
This prevents a crash, probably only occurring on certain GPUs.
Contributes to issue CURA-8657.
Instead of the minimum. So previously a value of 2 would make it spread the error over 2 walls for an even number, or 3 for an odd. Now it makes it spread the error over 2 walls for an even number or 1 for an odd. This means that the minimum allowed value becomes 2, because for an even wall count it needs to place the error somewhere.
Done as a 5 minute fix.
Conflicts:
resources/definitions/ultimaker2.def.json -> Additions in Arachne around a place where we fixed an enum setting.
resources/definitions/ultimaker3.def.json
resources/definitions/ultimaker_s3.def.json
resources/definitions/ultimaker_s5.def.json
This variable makes more sense to as a Ratio.
This was discussed during the eCCB 12/11/21
and implemented as a 5 min fix.
Note: The current default values were 0.5 there
is a new PR which change these 1.0. These values
should be multiplied with a 100
