Marker Challenge

Hello Philip -
Looks like lots of people have had similar results as you have when using markers with audio: https://community.articulate.com/search?utf8=%E2%9C%93&q=stop+marker+audio

The following links look similar to what you're trying to do:

https://community.articulate.com/discussions/articulate-storyline/using-audio-with-markers
https://community.articulate.com/discussions/articulate-storyline/audio-in-a-marker-hover

Hi Thor,

Thanks for your reply. However, that's not the issue I am having. I read through the linked threads and it doesn't solve what I am looking for.

What I need is:
1....for all markers to be unclickable/disabled while the audio on one is playing.

2...100% completion required for all audio on all markers before being allowed to move to the next slide.

3...autonomy to be left in tact for users to click whichever marker they desire in whichever order they please.

4...the slide to auto-advance when all audio for all markers is 100% complete. At the moment I am using a NEXT button and am trying to remove all NEXT buttons from all courses when possible,.

Thanks in advance!

Hi Philip,

You can certainly do step 1 and 3, but to achieve 2 and 4 would require the use of triggers and variables. If the audio is placed within a marker you do not have access to trigger events based on that audio. All of what you want could be achieved using shapes/images that mirror the look of the markers and abandon using markers. Then you would have complete control over the audio, the variables and triggers to achieve the result you are after. What specific functionality do you need from the markers? If just to play audio then I would use shapes/images and a click-reveal with audio sitting on the layers to do this. Then just trigger the events you need to happen using states and information captured in variables.

Thank you, Ray!

I don't really need anything from the markers. I haven't actually found them helpful in any courses thus far. I was exploring them here but they didn't work out once again.

I already abandoned them and started making shapes and layers with triggers. Almost done.
Thanks for confirming that was the best route for what I need. I wasn't sure so this is helpful.

Hi Philip,

I created a sample using another project I have been working on. Here's a link: https://360.articulate.com/review/content/371422d9-8da7-418a-bb1f-77b8ed449ede/review. Let me know if this is what you had in mind and I'll send you the Story File. Put simply, you have to leverage the power of states, layers, triggers, and variables to make this work well.

Cheers,
Ray

Hi Philip. No worries. I played with your first slide and got it to do what you need - removed the detestable NEXT button. See attached. You can then replicate that approach for your second slide. I would suggest you don't have a menu if you want the learner to interact with your content in this way.

Thank you, Ray!
I am grateful you took the time to correct this. This is perfect.

I'm studying the setup and noticed the trigger on the main slide that stops the intro audio when the user clicks the duration marker. This assumes they will click that one first. If they click a different one first would I simply need to add this same trigger to each of the other markers as well to avoid multiple audios playing at once?

In all likelihood, they'll probably click that one first, but no guarantee especially on the second slide that has nine markers spread out over the slide. 

Hi Ray,

So, I've tried duplicating what you did and have come to a point where I am stuck.
It all works amazing except I cannot figure out how to make the markers disabled/unclickable while it switches layers.

In the file you sent me, when on other layers the markers show up and the one that has been clicked shows as visited whilst none of them are clickable.

On the slide I am applying this to, the markers are all visible and clickable on the layers even though they only exist on the base layer.
How were you able to solve for this?

Thanks in advance!

I believe I found the solution!

Layer properties had to be set to 'Prevent user from clicking items on base layer'.
It seems to be working now.

Hi Philip,

Sorry, I thought I would be notified when this thread has an update but alas I didn't. Glad you found the solution. There are many ways to skin this cat. Preventing base layer click was the quickest solution for this scenario, but not always suitable. Alternatively, you could have used triggers to turn items from hidden to normal. Attached my sample Storyline to help out with options here.

Cheers,

Ray

Hi Ray,

Thanks for sharing that example. I've used that method for some things previously. Regarding the challenge I posted this time preventing base layer clicking was easier and more elegant.

Thank you!