TUTORIAL: Use states to hide/reveal multiple objects (no triggers)

Hi all, 

I picked up this great trick for changing states of groups of objects and made this Screenr to show you how. I found this technique MEGA USEFUL and I hope you do too. 

Use this technique to change the state of large amounts of content without triggers or layers - just states. 

Screer link: https://player.vimeo.com/video/149188565

[Or watch video in my post below]

Feel free to ask any questions / comment. I'll do my best to get back to you.

Rich

11 Replies
Alexandros Anoyatis

This technique is useful in a couple of scenarios :

A) When you utilise the menu on Master slide layers, makes using elements on Slide layers more difficult (you can't display a master slide layer and a (regular) slide layer at the same time - it is either one or the other).
B) Less triggers on your slides.
C) In certain cases, with a little tinkering, you can have animation-out's between states.
However, the disadvantage of this is that if you use images and any SL generated effects (shadows etc) on images, those image (in non-normal states) can become blurry.

Phil Mayor

I get the less triggers, but that is something I never worry about and dont see the need for reducing the number of triggers on my slides.

I have projects with slide layers and master slide layers open at the same time, just need to ensure the master layer is not set to hide other layers.

I would not build something like this, it is fiddly and makes editing slower, not saying it isn't a nice trick (it is).  Just seems like the standard functions deliver this without the need for workarounds.

Rich Calcutt

Fair comment that you can achieve the exact same thing with layers/triggers. My logic is pretty much the same as Alexandros' in terms of application - for me, reduced numbers of layers and triggers is always a benefit in terms of editing. I just find this makes sense within my workflow. 

I think the biggest thing for me was that I never really considered that states could store loads of objects like this. It means that I can, in my opinion, reduce the complexity of slides where I'm using a master with multiple layers already. 

Alexandros Anoyatis

Phil Mayor said:

I have projects with slide layers and master slide layers open at the same time, just need to ensure the master layer is not set to hide other layers.



You are right on this, but it is rarely an option for me as I usually have to create a lot of layers in the Master.


Agreed that it is not a "Be-all, end-all" solution, though. There's an example I have lying around somewhere in my hard drive that shows point C for example. I'll post it here once i find it...

Judy Nollet

There are obviously differences in people's programming preferences. I side with the folks who prefer content on layers. After all, it only takes one trigger to show a layer. Still, this trick might be useful in some situations.

However, there is one big drawback to maintaining content within states: When you publish to Word (e.g., for reviewing), the non-normal states aren't included. Thus, if you want a screenshot of the state variations, you'd have to publish the slide for the web, and then step through the interaction and capture the image for each state.