Representation dependency of loaded rig can go "out of sync" when updating

[BigRoy]

Issue

When a rig is loaded using the RigLoader it automatically adds an instance for publishing the animation and adds a "dependency" attribute linking to the representation it houses (the rig).

The problem there is that if the animator later updates the rig this dependency is not updated along, since it's not triggering the RigLoader again. As such, the representation id that is set in the dependency might not match correctly when the rig is updated.

Example issue

With the representation dependency going out of sync the CurvesLoader might try to load the wrong (older) rig version for the published animation.

[mottosso]

Could the update mechanism handle updating this too?

[BigRoy]

Could the update mechanism handle updating this too?

Maybe. Would that only be possible if the "Loader" would also be used to decide how it updates? As such update is implemented on the Loaders?

Because we wouldn't know "what" needs "additional updating".

[mottosso]

Interesting. That could be an option. Let's investigate that.

[mottosso]

On a related, but separate note, I was thinking of making methods on plug-ins into event callbacks.

class MyLoader(...):
  def on_load(self):
    pass
  def on_update(self):
    pass

It'd mean readability is improved, where you know when things are called (and not called), and make room for more events to be implemented, such as update.