Are you looking to prevent the end-user from advancing to the next slide until certain conditions are fulfilled? There's many ways to do that. Here's a few examples:
I guess what happened here was I looked at the Captivate worked example, and thought "Jeez! From what I know of Storyline, I wonder how many pages the most elegant example of doing exactly the same would take?". It was specifically the "selecting in a specific order" part that I was wondering about.
It just looked like a heck of a lot of work to achieve something that, i suspect, is doable in SL, and wanted to place the two examples side-by-side, almost as a comparative "sales" document, but did not have the time to actually figure it out myself.
Thanks for the examples anyway, and if anyone wants to have a try I'd appreciate seeing the difference!
I have to admit that I do not understand the logic of this, that's my brain rather than anything else, however...what I CAN see is the ease with which this has been achieved compared to the Captivate solution.
I have to admit that I do not understand the logic of this, that's my brain rather than anything else, however...what I CAN see is the ease with which this has been achieved compared to the Captivate solution.
I guess some brains are just wired in different ways!
I do not "see" how these things work, and am certainly not able to "imagine" them without a lot of hard brain-work. I can see (vaguely) what's going on, but will need to sit and dissect this over coffee.
7 Replies
Hi Bruce,
Are you looking to prevent the end-user from advancing to the next slide until certain conditions are fulfilled? There's many ways to do that. Here's a few examples:
https://player.vimeo.com/video/204929624
https://player.vimeo.com/video/145578741
Thanks Brian,
I guess what happened here was I looked at the Captivate worked example, and thought "Jeez! From what I know of Storyline, I wonder how many pages the most elegant example of doing exactly the same would take?". It was specifically the "selecting in a specific order" part that I was wondering about.
It just looked like a heck of a lot of work to achieve something that, i suspect, is doable in SL, and wanted to place the two examples side-by-side, almost as a comparative "sales" document, but did not have the time to actually figure it out myself.
Thanks for the examples anyway, and if anyone wants to have a try I'd appreciate seeing the difference!
Bruce
Hi Bruce,
There are many ways to do a "click in a specific order" interaction. I've attached a sample to this reply.
That is a great solution Brian! Many thanks for sharing this.
Best regards,
Mark
Brian,
I have to admit that I do not understand the logic of this, that's my brain rather than anything else, however...what I CAN see is the ease with which this has been achieved compared to the Captivate solution.
That's what I was looking for, so many thanks.
Bruce
The logic was explained here:
http://www.articulate.com/support/contact/screencast.php?screencastid=d7d3fcb913e8498f8b4d6e6a817a318e
(Note: The screencast was recorded during the beta and I've lost a lot of sleep since then. Thus, my logic might not be as logical as I thought.)
Thanks for that Brian.
I guess some brains are just wired in different ways!
I do not "see" how these things work, and am certainly not able to "imagine" them without a lot of hard brain-work. I can see (vaguely) what's going on, but will need to sit and dissect this over coffee.
Many thanks
Bruce
This discussion is closed. You can start a new discussion or contact Articulate Support.