Forum Discussion
How to find master slides being used?
In the slide master if you mouse over any of the slides a pop-up shows how many slides are using the slide layout. How do you find out which slides are using a specific layout? I have some duplica...
It's hard to believe this "ask" has been around for over 8 years! How can we finally get a quick way to search for slides that use an obscure master?
I think the suggestion, to put a mark, like a big red box, on the master, is brilliant. But, I've done that, but still can't find the last slide. So, I'm guessing something is on top of it.
I know, Peggy -- this is still frustrating. My main method is to go to the slide master in question and put a big red circle in the middle of the master slide. I might do the same for other masters -- green circle, blue circle, etc. From the Story View, MOST of the slides will then be easily identifiable. When the circle isn't visible (hidden by a slide element), I have fewer slides I have to check manually.
Not ideal, but it has been working in lieu of a real solution.
Thanks for the quick response, David. I'm trying to create a new template, based on slides from previous courses. So, as you can imagine, Storyline is pulling in multiple masters, that I want to get rid of. I also find that I have to save, and close Storyline, occasionally, for the masters that I have deleted, to really go away.
I will get there. It's just more time-consuming that I'd like.
Understood -- I feel your pain. When I pull in slides, I always pull them into a separate scene, replace each slide's master, delete the orphaned master and then put them where I want them in existing scenes. They do sneak in, though, and it is time consuming!
I used David's method, and it worked for spotting an eluding layer that was defaulting to the feedback master. I wish Articulate were more responsive with essential feature requests like this one.
Glad I was able to help; I agree, it's frustrating to have to use a lot of the same tricks, but we're still using Storyline here. My team and I have created our own Style Guide that captures a lot of our 'workaround' techniques that specifically try to avoid known issues (some native to Storyline, some thanks to our LMS.)
