Open tokejepsen opened 8 years ago
Sorry I'm not following, you want a publish to happen when the user resets?
Are we talking about this reset-button here?
Sorry I'm not following, you want a publish to happen when the user resets?
When a user, for example in TV Paint, wants to publish the scene, they hit a "Publish" button in TV Paint. The mechanism for this is George script, so its a hack to make it work with Pyblish. Basically writing a batch script to execute. When the user hits the reset-button in the GUI, they are getting the same information as before because the batch script hasn't been updated. With a callback to TV Paint to rewrite the batch script and execute, the Pyblish environment would be properly updated with new data from TV Paint.
Ah I see. Ok, sounds like quite a specific problem in this case, but having a callback for Reset either way sounds expected so why not!
sounds like quite a specific problem in this case
I think this might be the same for all extension that utilize pyblish-standalone, as I would do the same with After Effects.
Ah that's great!
In theory you could write a lot of callbacks to make Pyblish interact with TV Paint/After Effects in the same way as Maya/Nuke.
I like the sound of that.
Goal
To enable Pyblish to get a proper reset, rather than having to close down Pyblish/terminal and reissue a publish command from the host.
Motivation
A lot of confusion can happen when users hit the reset button, but still get failures of validation repairs they have already made.
Implementation
With callbacks, we could subscribe to a "reset" signal, which could in turn find the host and trigger the publish command. This would be implemented in each host separately.