-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancement, fix #281, #274 and #119 #304
Conversation
This is intentional. The instances are displayed in the order they are processed, and it's a feature of Pyblish to be able to arrange (and re-arrange) the instance order inside the context. class MyCollector(...):
...
def process(self, context):
context[:] = sorted(context, key=lambda i: i.data["someKey"]) |
This reverts commit 5e7042b.
:O sorry, didn't know that ! Will update those gif later :) |
Comment updated. GIF replaced and the PR description also renewed. |
Loving it! Welcome to merge and release once you're happy :) |
This is great stuff David! |
Fix #304, increase QML initialization waiting time
User operation will not be able to continue if the validation failed during the publish, since the logic to interrupt publish when validation failed is taking place in the beginning of extraction. In the state machine, `extracting` state will need to transition to `finished` when the validation failed, and since it's not able to do so, operation can't continue, due to the stop button didn't change to reset button. This commit fixed that.
Fix state machine transision bug from PR #304
This PR provide 2 fix and 1 extra feature:
Before
After