1. 02 Mar, 2021 1 commit
  2. 09 Feb, 2021 1 commit
  3. 08 Feb, 2021 2 commits
    • Ghostkeeper's avatar
      No longer always add Cura namespace before all metadata keys · dce304c9
      Ghostkeeper authored
      There might be metadata entries that are not from Cura. Those should not get a namespace. The Cura front-end now needs to decide which metadata entries get a namespace and which don't. It should put a cura: namespace before any settings that it recognises.
      
      Contributes to issue CURA-7615.
      dce304c9
    • Ghostkeeper's avatar
      Don't filter metadata entries with unknown namespace · 5f498896
      Ghostkeeper authored
      We'll just remove the cura: namespace then, to make Cura's settings still parse correctly.
      This is a compromise. Basically this removes any 'cura:' namespace even though it is not a real namespace. This is not conformant to 3MF which would say that these names need to be preserved. This means that we'd need to pass on the 'cura:' namespace to Cura itself and let them handle it. However the Cura front-end code doesn't know the namespace aliases any more. It doesn't have access to them from there, since they are not actual XML namespaces but just a convention of the name attribute of metadata tags we have. The front-end doesn't even have access to the XML, let alone the namespaces in there for each tag.
      The front-end needs to add the 'cura' namespace back if it recognises the name as a setting key, when writing the 3MF.
      
      Contributes to issue CURA-7615.
      5f498896
  4. 02 Feb, 2021 11 commits
  5. 23 Dec, 2020 2 commits
  6. 21 Nov, 2020 1 commit
    • StefanBruens's avatar
      Update long deprecated sip type conversion functions · 95680287
      StefanBruens authored
      sipConvertToInstance and the like have been deprecated since Sip 4.8.0
      and are removed with Sip 5.
      
      As the old functions are already implemented as typedefs to the new
      functions in Sip 4, there are no functional changes.
      95680287
  7. 26 Oct, 2020 1 commit
    • Kostas Karmas's avatar
      Fix crash occuring when the faces have wrong vertex ids · a38a40ca
      Kostas Karmas authored
      It can happen that the triangles in the object-to-be-loaded refer to vertex id's that do not exist
      in the vertices table. This means that either Cura made a mistake in saving these objects or that
      the triangles of the objects have been manually changed. In any case, this was causing a crash.
      
      This is now fixed by valdiating whether the vertex id's are within limits. Even if one of them is
      not, it means the triangle will not be loaded and we will end up with a possibly non-manifold and
      overall wrong object (especially if there are multiple mistakes like that). So, in such cases,
      refrain from loading the object by returning an empty bytearray.
      
      CURA-7790
      a38a40ca
  8. 09 Oct, 2020 2 commits
  9. 18 Aug, 2020 2 commits
    • Ghostkeeper's avatar
      Remove exception for modern CMake versions · 85abbec0
      Ghostkeeper authored
      The new FindPython3 script finds the wrong Python version. It finds the Python3.6 installed on the CI server from the OS, rather than the Python3.5.7 that we built manually. I'm going to try this as it seems to be the only difference between our build server (where it works) and our CI server (where it doesn't).
      85abbec0
    • Ghostkeeper's avatar
      Remove exception for modern CMake versions · e9390ec4
      Ghostkeeper authored
      The new FindPython3 script finds the wrong Python version. It finds the Python3.6 installed on the CI server from the OS, rather than the Python3.5.7 that we built manually. I'm going to try this as it seems to be the only difference between our build server (where it works) and our CI server (where it doesn't).
      e9390ec4
  10. 04 Aug, 2020 4 commits
  11. 29 Jul, 2020 2 commits
  12. 27 Jul, 2020 5 commits
  13. 17 Jul, 2020 1 commit
  14. 16 Apr, 2020 1 commit
  15. 03 Apr, 2020 3 commits
  16. 20 Mar, 2020 1 commit