Is there any way to group objects, that are placed all over the project and then hide them with just one single action-script line? Thx in advance, Philip

[philipg81907466]

I am working in CP 9 and I'm trying the following: the user should be able to make ALL highlight boxes invisible or visible by clicking the respective button on the first layout. So for example if the user doesn't want the highlight boxes to appear, he clicks on "Hide Boxes" and the boxes are hidden for the rest of the project. I managed to get to that point by using Actions... but it still is plenty of work for me to manually type in all the different names of those boxes into the action-script. So my question is: is there any way to group objects, that are placed all over the project and then hide them with just one single action-script line? Thx in advance, Philip

[Lilybiri]

No, that is not possible.

If you explained more, maybe could offer some tips. You can use shared

actions, time objects for more slides....

[RodWard · Accepted solution]

Actually...when the CpExtra HTML5 widget is released, this WILL be possible.

It has a feature called @syntax that allows you to perform an action (e.g. HIDE) automatically on any object throughout a Cp9 project simply based on the object's name.

So, for example, if you named all of the Highlight Boxes that you want hidden this way to have the suffix _HideMe, and you tell CpExtra you want all of them hidden if a user variable is assigned a certain value, then that's what will happen.

That's the good news.  The bad news is that the widget is still in final BETA testing at present, so you may have to wait a little before you can achieve your idea.

[Widget King]

Actually, speaking as the developer, that's only half true.

@syntax will allow you to hide multiple objects with a single line of code, but at the time of release it will only apply to all matching objects on the current slide. We were worried if @syntax applied across the whole project, it might lead to some unexpected hidings or showings later on in the project on objects that unintentionally matched the @syntax query.

Though looking at it now, this is definitely a valid use case. So I've put down a note to implement a preference in a future version which allows you to take off the training wheels if you will.

That said, @syntax could still be of use in this case. You would only have to execute a single line of code at the start of each slide (though a conditional action would still have to be used), which makes it easier to add and remove these objects as you wish.

Tristan,

[philipg81907466]

Thats great news!

Thx for your help and support - and for writing these little helpers 🙂

Philip