Forum Discussion
Story View Slides Position Glitch - Slide Order Does Not Respect Numbering
In Story View, slide positions will sometimes randomly change when triggers link to those slides, as shown in this Peek 360 video.
I have all the slides numbered in the order I want.
I want t...
Hello Robert, would you be willing to share your project file (.story) here so that someone can take a look and assist you with a better solution?
I guess that the clickable buttons on the TOC slide are in randomized order and that's causing this issue. Try to recreate those clickable boxes on the TOC slide one after the other and then reassign those triggers and see if you can replicate the specified issue.
Make sure to add those clickable buttons in the correct order!! Let me know if you need any further help with this by sharing your SL file.
Thanks, Sandeep. On the TOC slide, I followed your tip and deleted the existing shapes (pseudo buttons) and added them in order, then added the triggers in order. After this in the Story View, the slides were in a logical order. However, as soon as I started messing with jump to triggers on other slides, the positions of the slides randomly changed. I deleted all the triggers that involved jumping to other slides, dragged the slides into the correct positions, then added triggers again. The positions are respecting my wishes for now, but I suspect, they'll randomly change when I add or edit triggers for other things. This approach (copying and pasting each shape one-by-one) took way longer before when I copied and pasted groups of shapes in a logical order.
It's a time-waster for me why the visual position of slides in Story View will change based on the order in which shapes/buttons on another slide were added. As I mentioned before, this wouldn't be as big a deal, except that it directly affects how an editor can page or click through thumbnails in the left panel in Story View, especially in branched scenarios, This can lead to errors in triggers that are harder to troubleshoot in Story View because the slides are not in a logical order and cannot be forced to remain in that logical order when I drag them into place.
Thank you for your detailed explanation of the issue you've encountered while working on the presentation. I understand your frustration with the unexpected slide reordering in Story View, especially when working with jump to slide triggers. It's clear that this behavior has had a significant impact on your workflow and the overall usability of the software. The order of the slides in Story view was totally dependent on the triggers associated with the clickable buttons on the other slides.
I appreciate the effort you've put into following the recommended steps on the TOC slide, such as deleting and re-adding shapes in order and applying triggers sequentially. It's unfortunate that despite your meticulous approach, the positions of slides still changed unpredictably when dealing with jump to slide triggers on other slides. I can see that you took the necessary steps by deleting triggers, manually rearranging the slides, and reapplying triggers, which led to a temporary resolution of the issue.
Your concerns about the potential recurrence of this problem when adding or editing triggers for other elements are valid. The added time and effort required for such manual adjustments, especially when compared to the previously used method of copying and pasting groups of shapes, is indeed a significant concern.
I wish Articulate could implement a permanent solution for this!!
Hello Robert,
Happy to chime in!
I did a simple test on my end and saw that the order in which the slides are displayed in Story View is initially controlled by the order of the triggers in the slides. Here's a screenshot so you can see what I mean:
I added the triggers to connect to the slides in this order: Slide 1.4, 1.6, 1.2, 1.5, 1.3, and this is the order that you see the slides in Story View.
Taking a look at your Peek 360 video, I couldn't immediately identify why Slide 1.9 was slotted in between 1.4 and 1.5, so we'll need to take a closer look at the triggers to figure out what's happening.
Would you be willing to share a copy of your project file here or in private by opening a support case for testing? We'll delete it when we're done!
Thanks, Joe. I just submitted a support case and linked it to this discussion.
