139 Commits

Author	SHA1	Message	Date
Jaime van Kessel	00078fd659	Remove a bunch of unused imports	2019-11-08 13:38:42 +01:00
Nino van Hooff	c62ff262ed	Change SDK version to 7.0.0 ... CURA-6858	2019-10-21 14:51:34 +02:00
Lipu Fei	6992fd2991	Update plugin versions to match package versions ... CURA-6019	2018-12-17 13:03:21 +01:00
Ghostkeeper	c235f339ae	Increment API version to 6 ... All plug-ins now have to re-check whether they are still compatible with the current version of Cura. Contributes to issue CURA-6019.	2018-12-14 17:29:02 +01:00
Aleksei S	088b2f6f28	Added an extra import module, did not pass coding style test ... CURA-5936	2018-11-22 11:36:32 +01:00
Ghostkeeper	8ec7d6dba3	Fix type issues in old version upgrade plug-ins ... The one actual change was this: To give a KeyError when stuff can't be found in a dictionary, rather than returning None there and then getting a TypeError later. Contributes to issue CURA-5936.	2018-11-14 13:56:46 +01:00
Ghostkeeper	b67d8d4103	Fix type of fallback variable ... These have to be strings because the configparser getter can only return strings. Contributes to issue CURA-5936.	2018-11-14 13:46:13 +01:00
Ghostkeeper	ae2b312472	Add typing for all version upgrade plug-ins ... Hopefully we'll take this typing along when we next copy-paste the stuffs. Contributes to issue CURA-5936.	2018-11-14 13:41:23 +01:00
fieldOfView	9ac744b9ba	Remove unnecessary import and declaration of i18n in plugins	2018-10-03 22:00:24 +02:00
Aleksei S	fe9cada459	Increase plugin API version to 5 ... CURA-5627	2018-08-27 13:59:00 +02:00
Diego Prado Gesto	b309e93767	CURA-5330 Fix typing in the VersionUpgrade plugin	2018-06-14 16:54:22 +02:00
Lipu Fei	d80e66af02	Fix 21to22 upgrade ... CURA-5440	2018-06-04 15:18:33 +02:00
Lipu Fei	7de43e71e0	Fix legacy profile upgrade ... CURA-4075 Only for single-extrusion machines just like before.	2017-12-01 11:06:14 +01:00
Mark	9a193ad5c5	Changing AGPLv3 to LGPLv3	2017-09-28 13:00:43 +02:00
Ghostkeeper	cd4bffb380	Set author to Ultimaker B.V. instead of Ultimaker ... To be consistent with the rest of the plug-ins and with the material files. Contributes to issue CURA-3857.	2017-06-28 13:50:37 +02:00
Lipu Fei	4ea8cc448a	Use semantic versioning for all plugin.json ... CURA-3712	2017-06-22 08:57:47 +02:00
Lipu Fei	73f598ff9f	Fix code style ... CURA-3712	2017-06-22 08:54:04 +02:00
Jaime van Kessel	e3629cec39	Replaced catalog metadata entry with i18n-catalog ... CURA-3712 & Cura-3856	2017-06-21 14:24:00 +02:00
Jaime van Kessel	44125d3275	Moved certain meta data entries to seperate file ... CURA-3856 & CURA-3712	2017-06-21 11:22:35 +02:00
Lipu Fei	d02d004986	Correct profile_translations in VersionUpgrade21to22 ... CURA-3777	2017-05-17 13:44:34 +02:00
Jaime van Kessel	e40f60a52b	Changed profile names ... CURA-3777	2017-05-15 16:52:25 +02:00
Ghostkeeper	55b2392a1d	Load setting version from metadata ... I'm not really awake today, am I? The functionality happened to still work because of how our real data is structured right now, but the tests still failed. Those are successful now. Contributes to issue CURA-3427.	2017-05-12 14:55:19 +02:00
Ghostkeeper	9820dac4a6	Actually use setting_version to get the setting version number ... This was sort of hidden because we've always incremented the normal version number up until now. Contributes to issue CURA-3427.	2017-05-12 14:51:44 +02:00
Ghostkeeper	0a84a181c4	Track cfg version numbers with major-minor, sorta ... We now have a (format) version and a setting version. Ideally we'd like major-minor version numbers in our profiles. However, introducing major-minor version numbers requires substantial changes to the version upgrade manager to compare version numbers, find a path towards the current version, or even keeping track of the current version. Therefore we just collapse the two version numbers into one: Multiply the major version number by a million and you'll never exceed it in the minor versioning. The only problem is that we now have to update the versioning for all of our three upgrade plug-ins, because they all need to know locally how to find the version number of their file types (because the upgrade manager has no knowledge of the file types) and they have no access to each other because a plug-in may be disabled. Contributes to issue CURA-3427.	2017-05-11 17:31:37 +02:00
Simon Edwards	4ab6b74930	Fixed a bunch of error which were reported by PyCharm's code analysis.	2017-02-26 21:05:09 +01:00
Simon Edwards	cf85831d87	Also check the upgrade plugins.	2017-01-17 20:56:28 +01:00
Simon Edwards	98a6568313	Merge branch 'master' into python_type_hinting	2016-11-22 11:15:04 +01:00
Simon Edwards	14afd9eab7	Heaps to changes to get the Cura code through the type checker (with minimal checking). ... CURA-2917	2016-11-21 21:36:08 +01:00
Jaime van Kessel	1a2138de5a	Moved warning to VersionUpgradeManager ... CURA-2883	2016-11-21 11:21:20 +01:00
Jaime van Kessel	ac708d54b6	Importing invalid filetypes now gives proper error messages ... CURA-2883	2016-11-18 16:46:54 +01:00
Arjen Hiemstra	bfec96f584	Set encoding to utf-8 when writing files ... Since we assume utf-8 in a lot of places. Contributes to CURA-2692	2016-10-24 14:28:20 +02:00
Ghostkeeper	2d41a992f1	Remove splitting profiles for each material ... The material is no longer listed in the profiles and no longer filtered for, so we don't need to create a new profile for each material. Contributes to issues CURA-844 and CURA-2320.	2016-10-06 11:41:39 +02:00
Ghostkeeper	7d57e90260	Remove debug statements ... Oops. Contributes to issue CURA-844.	2016-09-29 13:24:15 +02:00
Ghostkeeper	d29c817289	Actually apply translated settings ... Don't know when this changed or why it hasn't propped up until then... Contributes to issue CURA-844.	2016-09-29 11:56:46 +02:00
Ghostkeeper	4ec380ffd9	Quality-changes now have a quality_type instead of referring to quality ... This field was just renamed, I think for CURA-2320. This updates the name for the upgrade process. Contributes to issue CURA-844.	2016-09-27 15:12:29 +02:00
Ghostkeeper	3f85ac264c	Properly serialise the machine instance name ... Otherwise we get spaces and unescaped plusses in the file name of the user profile. Contributes to issue CURA-844.	2016-09-21 17:34:22 +02:00
Ghostkeeper	ebb9507083	Add extension to new file ... The upgrade plug-in can do this because he know that he's upgrading to version 2.3. Contributes to issue CURA-844.	2016-09-21 17:34:22 +02:00
Ghostkeeper	7d41c1dcb3	Give canonical name to user settings ... All user profiles are named Current settings, so we should just give it the same name as well. Contributes to issue CURA-844.	2016-09-21 17:34:22 +02:00
Ghostkeeper	d962cad347	Ensure directory exists to store user profile in ... Create it if it doesn't exist. Also fix up the directory to be absolute instead of relative. Contributes to issue CURA-844.	2016-09-21 17:34:22 +02:00
Ghostkeeper	c1a593c3d8	Create new user profile upon upgrading machine instance ... This defines a new configuration type: 'user', for the user profile. Contributes to issue CURA-844.	2016-09-21 17:34:22 +02:00
Ghostkeeper	d391639b48	Translate Fan Speed Full At Layer to one-based counting ... All layer counts should increment by 1. Contributes to issue CURA-2314.	2016-09-16 16:50:27 +02:00
Ghostkeeper	ef3b6905b7	Translate skin overlap properly ... From this dict it also gets updated in other places, such as the preferences. Contributes to issue CURA-844.	2016-09-15 12:47:39 +02:00
Ghostkeeper	c223044541	Don't modify original dict while iterating over it ... Just store the results in a new dict and return that one.	2016-09-15 12:47:39 +02:00
Ghostkeeper	5c5d188889	Remove support_area_smoothing setting ... Contributes to issue CURA-2296.	2016-09-14 15:41:32 +02:00
Ghostkeeper	5c49adc52e	Also return tuple if upgrading failed ... It is checked if the file data is None or empty (the upgrade is then considered 'failed'). But to unpack the file data, it needs to be a tuple. Contributes to issue CURA-844.	2016-09-14 15:41:32 +02:00
Ghostkeeper	89fb92edbd	Disable upgrading current settings altogether ... The current settings in 2.1 specified a machine instance. In 2.2 they specify a machine definition. There is not enough information in one file to be able to translate that. Contributes to issue CURA-844.	2016-09-13 14:58:13 +02:00
Ghostkeeper	03c3b2ac2f	Make empty profile for current settings when upgrading from UM2+ ... This change causes the stack to make a new profile at the top to store current settings in. Contributes to issue CURA-844.	2016-09-09 17:23:13 +02:00
Ghostkeeper	1e23141b18	Fall back to different quality depending on stack ... Falling back to normal.inst.cfg isn't enough. That profile may be filtered out by the machine, variant and material. We need to fall back to a different quality profile depending on the machine, variant and material. Contributes to issue CURA-844.	2016-09-09 16:20:06 +02:00
Ghostkeeper	ba6ce52d29	Use translation of built-in profiles instead of constructing it ... Makes the code much simpler, though some repetition is hard-coded now. Contributes to issue CURA-844.	2016-09-09 16:20:06 +02:00
Ghostkeeper	e77ab83084	Set quality to normal, not quality type ... Even though this key says it's quality, it's not a quality profile, it's a quality type. Contributes to issue CURA-844.	2016-09-09 16:20:06 +02:00