I could be oversimplifying this - and if so, just tell me! I'd love to see your .story file if so and then we could work within your specifics.
Have you tried applying the slide transitions to slides 3, 4, 5, and 6? As each of those slides could have it's own transition and that would appear when arriving on that slide, no matter what slide you were at before.
Yeah, as always, going forward is fine, it's going back to try a new direction that's the tricky bit. I want the user to "Go" to one page, then "Go Back".
Duplicating pages in itself is not troublesome, but every time it goes through testing you are increasing your work 5 fold when updates to a page are required (and let's hope we don't miss one).
The solution to going back is pretty much the same as what Ashley suggested going forward. Instead of going back, you need to navigate to a new slide that has your animation to go back, and the when can jump back to the beginning page when the animation completes.
Yes, keeping up with multiple copies of an image can be a challenge. Sometimes I keep a list of where each image is used in a separate unused layer that I call developer's notes. When you swap out images, be sure to keep the new image the same size if possible, and use change image to do a direct swap of the image.
4 Replies
There may be an easier way, but you could try this.
Make 4 copies of your compass page, with no transition (so it looks exactly the same).
Then have your different transitions on those identical secondary pages.
Hi George,
I could be oversimplifying this - and if so, just tell me! I'd love to see your .story file if so and then we could work within your specifics.
Have you tried applying the slide transitions to slides 3, 4, 5, and 6? As each of those slides could have it's own transition and that would appear when arriving on that slide, no matter what slide you were at before.
Yeah, as always, going forward is fine, it's going back to try a new direction that's the tricky bit. I want the user to "Go" to one page, then "Go Back".
Duplicating pages in itself is not troublesome, but every time it goes through testing you are increasing your work 5 fold when updates to a page are required (and let's hope we don't miss one).
Hi George,
The solution to going back is pretty much the same as what Ashley suggested going forward. Instead of going back, you need to navigate to a new slide that has your animation to go back, and the when can jump back to the beginning page when the animation completes.
Yes, keeping up with multiple copies of an image can be a challenge. Sometimes I keep a list of where each image is used in a separate unused layer that I call developer's notes. When you swap out images, be sure to keep the new image the same size if possible, and use change image to do a direct swap of the image.
This discussion is closed. You can start a new discussion or contact Articulate Support.