Publisher: Display overridden vs default values of attributes

[iLLiCiTiT]

Changelog Description

Visualy display if value of attributes on instance does not match default value.

Additional info

It should also behave correctly on multiselection of instances even if they don't have same default values. But if at least one of selected instances does not use default value it is shown as overriden.

Testing notes:

1. Open Publisher in host of your choice.
2. Create an instance (or use existing one).
3. Change any attribute value.
4. It should change color of it's label.

Resolves #139

[BigRoy]

I love this!

I do think this should absolutely come with a means to "reset to defaults" so that one could easily learn also that the color hinting means that it's "not at default value". But it does work very nice! Great work. Here's a good reference on revert to defaults.

I would almost go as far as saying it should be part of this PR - but I'm technically fine with it as a follow up PR.

[BigRoy]

@iLLiCiTiT should we somehow dim the color if it's 'disabled'?

(This is e.g. after publishing, before reset)

And, the orange color is relatively 'negative'. Should we use the "green" color for saved studio override settings on web frontend instead?
Or the blue color for unsaved overrides?

[LiborBatek]

Works nicely, the only occasion which throw some traceback is when trying to switch settings for context and Validate outdated containers

resulting in

// Traceback (most recent call last):
//   File "C:\Work\REPO\ayon-core\client\ayon_core\lib\events.py", line 332, in process_event
//     callback(event)
//   File "c:\Work\REPO\ayon-maya\client\ayon_maya\plugins\create\create_maya_usd.py", line 30, in on_values_changed
//     if instance["creator_identifier"] != self.identifier:
// TypeError: 'NoneType' object is not subscriptable

Not failing but worth mentioning imho....

[BigRoy]

resulting in

// Traceback (most recent call last):
//   File "C:\Work\REPO\ayon-core\client\ayon_core\lib\events.py", line 332, in process_event
//     callback(event)
//   File "c:\Work\REPO\ayon-maya\client\ayon_maya\plugins\create\create_maya_usd.py", line 30, in on_values_changed
//     if instance["creator_identifier"] != self.identifier:
// TypeError: 'NoneType' object is not subscriptable

Not failing but worth mentioning imho....

Thanks - that's actually a bug outside of this PR then. I'll fix it. 👍

[iLLiCiTiT]

should we somehow dim the color if it's 'disabled'?

I've changed color to the "greenish" one, and with that I would keep it even if is disabled. But I don't have strong opinion about this, should be easy to change.

I would almost go as far as saying it should be part of this PR - but I'm technically fine with it as a follow up PR.

Separate issue, this was easy, reverting might be a little but more complicated.

[BigRoy]

Just adding some screenshots with latest changes:

Looking really nice. I'd say, ready to merge - except maybe last debate on the chosen color?

---

I do wonder whether Green or Orange is the best color pick here. Artist here said "looks like an approved value".

Maybe the blue tint would still be better?

@mkolar @Innders thoughts?

[iLLiCiTiT]

For comparison adding how it would look with the blue color

[BigRoy]

Yes - blue is much better!

Ready for me. 🚀

[iLLiCiTiT]

I like blue the most.