Closed epmog closed 1 week ago
Maya 2025 support was just added that uses PySide6. PySide6 changed how they handle enum values: https://doc.qt.io/qtforpython-6/considerations.html#the-new-python-enums. So the way we're checking does not enable the frame list properly.
PR for inspiration: https://github.com/aws-deadline/deadline-cloud-for-blender/pull/90
It works!
hatch run lint hatch run test
Will test manually first before merging.
N/A, this is for the UI, not the job bundles.
N/A
Nope
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Issues 0 New issues 0 Accepted issues
Measures 0 Security Hotspots 0.0% Coverage on New Code 0.0% Duplication on New Code
See analysis details on SonarCloud
What was the problem/requirement? (What/Why)
Maya 2025 support was just added that uses PySide6. PySide6 changed how they handle enum values: https://doc.qt.io/qtforpython-6/considerations.html#the-new-python-enums. So the way we're checking does not enable the frame list properly.
What was the solution? (How)
PR for inspiration: https://github.com/aws-deadline/deadline-cloud-for-blender/pull/90
What is the impact of this change?
It works!
How was this change tested?
Will test manually first before merging.
Did you run the "Job Bundle Output Tests"? If not, why not? If so, paste the test results here.
N/A, this is for the UI, not the job bundles.
Was this change documented?
N/A
Is this a breaking change?
Nope
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.