I hope I’m just missing a particular method or property somewhere, but whenever I add a new foreground experience layer, or copy and paste one, it automatically is assigned to every scene. If I have 45 scenes and it only applies to five, I have to go and uncheck it in the Properties > Experience Layers 40 times, which seems redundantly unnecessary because it’s about 160 mouse clicks.
If there isn’t a faster way, then I think it would be a great feature for the foreground experience layer to have a Properties > Layers Included palette that lets you check or uncheck scenes in one place, that way the user could check the All Scenes checkbox, uncheck it to select none, then check the 5 they need (as an example).
As of today, you are correct, when you add an XP Layer (Foreground or Background) to an existing XP, that layer is by default made visible to all previously existed scene.
The reasoning was that an XP layer is “usually” made to be shared across a majority of scenes, then disabled in a just few.
Half-full / half-empty cup point of view / dilemma.
I agree that Composer should offer more flexibility, I’ll report your use case to our team.
hey @cullenb this may not be a perfect solution, but could you use conditionals and a naming convention to help in the future? This is off the top of my head, but bind the visibility to ‘current scene’ with a text manipulation, or some other modifier.
One idea - name each scene that should have the foreground layer with -True, then bind the visibility of your foreground layer to the “Current Scene” property of the XP, then use text manipulation with “Item at”, select the -, with item 1. That should strip out the “True” for the visibility.
If it works, all you have to do when you create scenes is name them with -True or -False and it will automatically show/hide the foreground layer. I have not tested this exact example, but I have done similar. Hopefully this at least sparks some other ideas to save you time.
