Library linked rig workflow

[clembu]

I have found that most if not all of the properties and operators in the UI are not library-overridable.
Meaning, when one links the rig in another file, and makes either a proxy or a library override, this UI is simply disabled because the properties it controls are not editable.

• the layers visibilities
• the setting checkboxes, with masks, etc

meaning that this UI is only friendly to appending the rig. Which, in all regards, is functional and makes things work, but it also means a lot of data duplication.

[Mustard2]

Yes this is how it works now. I'm planning a major revision of the code in order to solve this and a lot of other problems/limitations.

(I started this as a small first Blender script project, and since I'm dumb I started adding stuffs without rewriting it properly. In the end there were too many things in the UI for rewriting everything from scratch. But I'm aware of the issues, and planning to revisit everything soon.)

[Mustard2]

#5 I am working on this, it will be "fixed" in the new version. I am busy porting all old functionalities on the new code, so it won't be a fast process. :)

[Mustard2]

I might need some help here.

I saw that there is a
override = [‘LIBRARY_OVERRIDABLE’]
option for all properties. Should this be enabled to all properties to achieve what you firstly asked in this issue?

Ref. https://docs.blender.org/api/current/bpy.props.html

[clembu]

I think all properties directly accessible via UI should be overridable.
I haven't handled a linked MustardUI file in a while so i forgot exactly what was blocked ; i'll check when i have time, to jog my memory.
But typically things like the debug mode or the advanced toggles, or the subdivision modifier checkboxes.

[Mustard2]

Thank you!
I'll try myself, if that's the solution it should be simple to implement it everywhere.

[clembu]

None of the controls seem to be active, actually. This is what the menu looks like when making a library overdrive from the Tifa collection.

If it helps to understand, the debug info on the description tooltip for the outfit list (for example) gives me this

To be fair, I just realized the Tifa i'm using right now is bundled with the 0.11.3 version of the script, so that's why the property is still outfits and not outfits_list, but still, i think the idea is that if there's a button to edit that property, it'll need to be overridable

[Mustard2]

OK, thank you very much for the test. :)

I didn't change the options of the properties in version 0.20.0, so I expect the issue to be also there. I will try to set the override option and check if the problem is solved.

[Mustard2]

Partial solution for this issue has been implemented in 0.21 and 0.22, enabling library override for custom properties.

[Mr-Lux]

Is there any update on the progress to make enums and bool locks properties library overridable within the script?

[Mustard2]

I have to find the time to go through all the properties and set the override. :(

If this is a priority, I can do this before other things.