[bsoriano]

I tried with this:

xml:


[$EXP[Exp_View_54] + Skin.HasSetting(Enable.NewViewSelector)] | [!Skin.HasSetting(hide.lowlistview)]

You also need to check that the "Enable.NewViewSelector" setting is not set in the second half of your condition - otherwise the view is always visible as long as "hide.lowlistview" is not set.

It needs to be:

xml:
[$EXP[Exp_View_54] + Skin.HasSetting(Enable.NewViewSelector)] | [!Skin.HasSetting(hide.lowlistview) + !Skin.HasSetting(Enable.NewViewSelector)]

I saw on GitHub that your latest commit adds a condition to disable the view lock, how does that work?

It basically adds a condition like your "Enable.NewViewSelector" to the Expressions.

To the top of your json file you add

xml:
"condition": "Skin.HasSetting(Enable.NewViewSelector)",

That will basically construct conditions like so:

xml:
[Skin.HasSetting(Enable.NewViewSelector) + NORMALEXPRESSION] | [!Skin.HasSetting(Enable.NewViewSelector) + ALLOWEDRULES]

The "normalexpression" part will be the same as what the script normally makes. The "allowedrules" part will be any rule that has the viewtype ID specified in the rule's viewtype list. For instance, if in my script you normally permit the user to choose ID 54 for Container.Content(movies) and Container.Content(episodes) then the condition will look like this:

xml:
[Skin.HasSetting(Enable.NewViewSelector) + NORMALEXPRESSION] | [!Skin.HasSetting(Enable.NewViewSelector) + [Container.Content(movies) | Container.Content(episodes)]]

But that's not that much use to you if you also want to have the "hide.lowlistview" in the condition.

@jurialmunkey , thank you so much! I appreciate your explanation and I apologize if I asked something that should have been obvious.  This works perfectly!

Regards,

Bart