You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please describe the feature you have in mind and explain what the current shortcomings are?
In Houdini addon we faced a problem when ROP node's parameters needs to be updated to match user selection in the publisher.
e.g. changing the render target requires updating some parameters on the ROP node respectively.
Currently, The logic responsible for setting ROP's attributes to favorite values, lives in the extractors.
which is against pyblish concepts.
How would you imagine the implementation of the feature?
We need to figure out a way to sync the ROP's state with the selected options in the publisher.
Are there any labels you wish to add?
I have added the relevant labels to the enhancement request.
Describe alternatives you've considered:
There was an experimental PR ynput/ayon-core#418 but it increased the complexity of the plugin.
Its idea was to set node's parameters when clicking save in the publisher and set the options to match the node when resetting the publisher.
Additional context:
No response
The text was updated successfully, but these errors were encountered:
I'd like to mention that #2 implements a logic that achieves the mentioned enhancement request in this issue.
As the node parameters and the publisher attributes are synced.
From the node to the publisher and from the publisher to the node.
That logic is implemented in collect_instances by reading the rop parameters, creating the instance manually and adding it to the context and update_instances by the imprint method that propagates the changes from the publisher to the node.
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
In Houdini addon we faced a problem when ROP node's parameters needs to be updated to match user selection in the publisher.
e.g. changing the render target requires updating some parameters on the ROP node respectively.
Currently, The logic responsible for setting ROP's attributes to favorite values, lives in the extractors.
which is against pyblish concepts.
https://github.com/ynput/ayon-core/blob/6df1a97446d485badcd91c5ae353c5a7962ac757/server_addon/houdini/client/ayon_houdini/plugins/publish/extract_render.py#L25-L43
How would you imagine the implementation of the feature?
We need to figure out a way to sync the ROP's state with the selected options in the publisher.
Are there any labels you wish to add?
Describe alternatives you've considered:
There was an experimental PR ynput/ayon-core#418 but it increased the complexity of the plugin.
Its idea was to set node's parameters when clicking save in the publisher and set the options to match the node when resetting the publisher.
Additional context:
No response
The text was updated successfully, but these errors were encountered: