This will hopefully prevent people from messing with the installed files (and then getting confused when they upgrade) when they should be using the configuration (sub-)folder(s) instead. If I read cura-build correctly, just placing the files here will already copy them to the right directory, since that happens for all folders (and hopefully files) for those directories anyway.
> The clip-rule property is not supported by Qt.
> The fill-rule property is not used in this image since there are no self-intersections.
> The fill property is not used in this image, since it is always recoloured. The colour shown here is incorrect (different from what we actually use in the interface).
CURA-7278
Co-Authored-By: Ghostkeeper <Ghostkeeper@users.noreply.github.com>
Instead of updating the storage path every time you add or remove a removable drive, we now update the storage path every time you press the button to sync. That way this detail has no impact on performance of other parts of Cura if they don't use this button. It also makes the code a bit simpler.
The only downside is that this FileDialog then contains state, instead of automatically syncing with the MaterialManagement property for its folder property. I see that as a lesser of two evils.
Contributes to issue CURA-8055.
This background colour is the same as the main background, on which these buttons almost always are situated. However in the cases where they are not, such as the post-processing scripts button, this makes the text easier to read than a completely transparent background colour.
Done as a 5 minute fix.
* Update anycubic_i3_mega_s.def.json
Adapted Deviation to ATMega2560 of Anycubic Mega S
* Update resources/definitions/anycubic_i3_mega_s.def.json
Good points. Thanks!
Co-authored-by: Konstantinos Karmas <konskarm@gmail.com>
Co-authored-by: Konstantinos Karmas <konskarm@gmail.com>
There's a suspicion that this is causing a crash on exit. From the traceback it seems like it's attempting to find a certain property on a deleted item. I'm thinking it might be trying to update properties on an item that was already deleted by the system here because the item got moved to a system-specific menu. Qt doesn't realise that. By not translating that property, it's not necessary to update and hopefully this prevents the need to look up data on the deleted item.
Not translating it is not an issue anyway, since the menu will also be renamed by Qt to some system-specific name, which is then also translated to the user's system-language by MacOS itself.
It's not at all sure if this will fix it. Tests are necessary.
Contributes to issue CURA-8245.
* Added prelim support for the BX
* Revert "Added prelim support for the BX"
This reverts commit 923fbdbbb617d000663f04d08d468ed0c560517c.
* Added prelim support for the BX
* Revert "Added prelim support for the BX"
This reverts commit 923fbdbbb617d000663f04d08d468ed0c560517c.
* Added BIQU BX printer def
* Updated the platform name.
* Minor update to the start code. Ready for merge.
* Initial FLSun Super Racer profile setup.
* flip has_machine_quality to false as suggested by @konskarm.
* tabs vs spaces! Space is the final frontier!
* Enumeration value should be in inner single quotes as requested by @konskarm.
