| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Fonts were looking a bit to thick on when using `Text.NativeRendering`, so using `Text.QtRendering` instead. After this the font weight looks identical to figma (as far as I can see).
In this commit I also changed all `Label`'s to `UM.Label`'s and removed default properties where I could.
CURA-9154
|
|
This reverts commit f0e3c19a34d1fde3b7ec4fd95677fbefa2028b26.
|
|
Fonts were looking a bit to thick on when using `Text.NativeRendering`, so using `Text.QtRendering` instead. After this the font weight looks identical to figma (as far as I can see).
In this commit I also changed all `Label`'s to `UM.Label`'s and removed default properties where I could.
CURA-9154
|
|
|
|
CURA-8640
|
|
|
|
No idea why this was even done, but there just isnt' a reason to use these.
|
|
The new links also have campaign identifiers. Because apparently the website doesn't read the HTTP metadata information saying that it redirected from Cura, and it adds information which button it came from.
The old links will remain working via redirects, for older Cura versions.
Contributes to issue CURA-8528.
|
|
We created a new set of icons for Cura. These icons had to be reverted though because they weren't working out in the interface for the last release yet.
This unreverts them, basically adding them back hoping that we'll get them fixed in time for the next release.
Contributes to issue CURA-8342.
Revert "Revert "Fix merge conflict""
This reverts commit bb20e3307f43edc1ff53cb154d2351ddfe39e158.
Revert "Revert "Merge pull request #9716 from Ultimaker/CURA-8010_new_icons""
This reverts commit 70e4e9640e561e18a12870f30c905203ce8ccee7.
Revert "Revert "Fix typo in icon name""
This reverts commit 38ce22ba7c3f40b971bc6e1e0a8e776ca9d51512.
Revert "Revert "Add list for deprecated icons""
This reverts commit 119a957e7f978dbf1ddbcb3b0005bf38e8fed943.
Revert "Revert "Add Function icon""
This reverts commit 760726cf0bb953bb1b0fc277b448f419d4bd2544.
Revert "Revert "Switch out inherit icon""
This reverts commit 26afff609381e2004d194c280f504b6226859bd3.
Revert "Revert "Merge branch 'CURA-8205_Introduce_new_icons_in_Cura' of github.com:Ultimaker/Cura""
This reverts commit 6483db3d47ee052c1a966cdee3af7190577a5769.
Revert "Fix incorrect icons"
This reverts commit 02a4ade2a50a943ff36fd4895bdc9261cf2133eb.
|
|
We want to keep it this way so people can still make plugins work for older versions of Cura, like 3.6, where the 'api' field with just a single major version, instead of the 'supported_sdk_versions', which can be either a version-string like '7.6.0' or a list of version strings.
|
|
CURA-8320
|
|
This reverts commit 6120d8a054b8c04bf90b8b3d3cb219d691bece2f, reversing
changes made to 95652556fef90f70adbf25bfa9bd3b8af7220d4a.
|
|
Subdivided the new icons in 3 size categories. As requested by UX
Used the company naming scheme for uniformity and easy recognition.
Known issues:
- Top/Bottom category wasn't taken into account by UX at the time. Since
this is a recent addition. Both the Walls and Top/Bottom will be updated.
- Cloud/Network connection icons 12px don't render correctly. Due to the
theme-ing.
- Extruder Icons do not render correctly.
CURA-8010_new_icons
|
|
network-connected
There could be other methods of connecting than the network connectivity of the UM3NetworkPrinting plug-in. For instance, perhaps other network connection plug-ins can provide information in this monitor stage. Or the user might want to use a USB cable.
I'm explicitly quite vague about how it should be connected because this label should work for all types of connections except UM3NetworkPrinting.
Fixes #9444.
|
|
The Cura 4.9 release will have expanded functionality. If you have a plug-in that uses this functionality, marking it as using SDK 7.5.0 will notify older Cura releases that they can't use that plug-in.
|
|
In preparation for release of the 4.8.
CURA-7795
|
|
It's so close to the text one that it really doesn't make sense to keep it.
Boyscouting the code a bit here
CURA-7745
|
|
CURA-7641
|
|
It was messing with the dark side. Theme. I mean theme.
part of CURA-7627
|
|
|
|
CURA-7383
|
|
We've added new things to our API. This allows plug-in developers to use them.
Contributes to issue CURA-7205.
|
|
CURA-6858
|
|
CURA-6858
|
|
In theory it should be possible to add stages, but there is no possiblity to add any other stage in between. Therefore I moved the weights by 10+n*10. So we can add 10 before prepare and 9 stages between those 3 known stages.
It is probably possible to set the same weight to multiple stages, but I'm not sure how Cura decides, which stage to take first then. By the moment the plugin's init is called? Or by alphabet?
Therefore putting some space in between the weights should give some clearity.
|
|
|
|
We shouldn't hardocode machines in QML in any case. It also created issues
for other monitor / connection flows.
|
|
|
|
|
|
|
|
|
|
Contributes to CL-1154
|
|
Contributes to CL-1154
|
|
Contributes to CL-1154
|
|
Contributes to CL-1154
|
|
Contributes to CL-1154
|
|
This is not the worst hack ever, but it's quite a hack.
Contributes to issue CURA-6054.
|
|
CURA-6038
|
|
Increment API version to 6
|
|
CURA-6019
|
|
|
|
All plug-ins now have to re-check whether they are still compatible with the current version of Cura.
Contributes to issue CURA-6019.
|
|
CURA-5943
|
|
CURA-5943
|
|
CURA-5943
- Add rounding
- If there's no sidebar, use full width
|
|
CURA-5943
|
|
Since we are going to move all the views into a seperate stage, we need to add another stage to do that.
CURA-5829
|
|
|
|
CURA-5627
|
