hide/unhide icon

I'm having a love-hate relationship with the hide/unhide function (eye icon) of objects on the timeline.

https://community.articulate.com/series/articulate-storyline-2/articles/working-with-the-timeline#hiding

I love it because it makes it possible to hide an object which is covering another object which I like to edit.

I hate it (somehow ;-) because if an object is hidden on the timeline it is also hidden in the published file unless I do not forget to unhide it. If I forget to unhide it after editing the other object will remain hidden 'forever' even after opening and closing the file... :-(

For me this is not logical... If I want an object to be hidden in the published file... I will just give it the state hidden. My perfect functionality would be that the object is only hidden in the editig mode. In that way it works the same as the lock-icon which locks an object only in the edit mode.

But maybe everybody else is very happy with the way it is? In that case I'm okay with it, but then my main question is: Is there a way to unhide all objects in a storyline file with one click or a change this behaviour with a setting?

If you have a lot of slides with a lot of layers with a lot of objects. It is quite a lot of work (and error sensitive) to go through all the timelines of all the layers of all the slides to check if there is not an object on a timeline which I did not unhide.

4 Replies
Walt Hamilton

The one eye to rule them opens and closes them all. If they are in a mixed state, first click hides them all, and second shows them all.

 Beware, there was a time when it would show a group as showing, but when you expanded the group the children were hidden. That may or may not have been fixed.

UP Learning

Hi Walt,

Thanks for you reply and screenshot. Your answer is very clear.

But... (sorry ;-) even with that option I still have to go through all my slides and through all the layers to do this action (hide all-show all). There is a estimated total of more than 400 layers distributed over all the slides. So still a lot of work and still the risk of forgetting a layer and missing a hidden object.

So my question is: Is there one single action which makes all the objects on all the layers on all the slides visible with 1 click? Without going through all the slides and layers.

UP Learning

Hi Phil,

Thanks a lot for your answer and another interesting way of approaching this. I really appreciate the effort and time you put in answering all the forum questions.

I thought a bit about it and in my opinion there are differences between tools like Photoshop/Illustrator (design tools) and tools for creating interactive content.

The output of Photoshop/Illustrator is static content. There are no actions (triggers) which change the content and make objects visible or invisible after it is published.

The output of Storyline is dynamic. Interactions of the user can change the objects on the screen. Therefore I would like to compare Storyline with editing tools like Lectora and Flash (Animate). If you hide an object in those tools in the editing mode (also with an eye-icon ;-) the objects are only unvisible in the editing mode but visible in the output. If you change the property of an object to hidden (like changing the initial state in Storyline) it will be hidden in the output.

In most projects you HAVE to use the eye-icon because there are always objects covering other objects. And when you want to edit the 'lower ones' you have to hide  ones which are on top, because it is the only way you able  to edit them. It is not because I want them to be unvisible.

(By the way if I select an 'lower object' in the editing mode in Lectora it kind of goes through the top so I'm able to edit it, after de-selecting it goes back. So it is not even necessary to hide and unhide objects just for the sake of editing. This makes editing of objects much easier than in SL.)

As far as I know Storyline handles this in a different way than the (many) authoring tools I worked with. And IMHO this is not logical and can create a lot of extra work because you have to check all the layers (in my project 400) to be sure that there is not an accidentally hidden object...