Marker issue: Initial hidden markers fail upon revisiting the page,

Dec 11, 2017

Hi All,

I am using Storyline 360 and am using markers to present additional information to the learner. In order to have some control over the learning path I have decided to hide the markers first and show them one at the time. The user must read them all before going to the next page.

During testing I found that upon first visiting the slide everything works as advertised. But when you go back to the slides, the markers are unhidden (as they should) but you cannot click on them to show the labels.

If I set 'Return to initinal state' all is okay.

I cannot see what I am doing wrong here, it is very simple Storyline logic.

Thanks for your help.

Regards,

Menno

13 Replies
Alyssa Gomez

Thanks for sharing your file, Menno! I took a look, and I'm seeing some buggy behavior here. When you set the initial state of a marker to "Hidden" and add a trigger to change the marker to Normal when another object is clicked, the marker won't work correctly when the slide is revisited.

I'm really glad you brought this up since I don't see that this has been mentioned before in the forums. I'll create a report for this so my team can begin looking at next steps.

In the meantime, could you use a white rectangle to hide the markers instead of setting the initial state to "Hidden"?

Menno Verhorst

Hi Alyssa,

Thank you for getting back to me. Glad I canbe of some help making the product beteer.

The white square is not an option for me because the slides I've uploaded are just an example off an online course of 80+ slides. All which have similar functionalities and thus issues.

I there any way you can give me an ETA of a fix?

Regards,

Menno

 

 

Alyssa Gomez

I completely understand, Menno. I don't have an ETA on a resolution at this time, but our team is looking at how many customers the bug affects and how seriously those customers are impacted. Those factors will help us to prioritize a fix. In case you're interested, here's some more information on our process for tackling bugs.

 

KiKi Denee

Hi, I am fairly new to this but have been trying to use markers as buttons to initiate "pop-ups" with explanatory information... I have been reading through questions and posts and watching the tutorial videos but my problem is that I never see the labels. They never show up for me to enter info into them. I have previewed the slide and they DO show up there but look like long, deflated balloons! I've already checked to make sure the audio only button is not checked. 

Any advice on what to do to bring out the labels so I can add text to them? 

Thank you!

Ashley Terwilliger-Pollard

Hi Kiki,

While you're viewing a slide to edit it, you can click on each marker and the label should pop up to allow you to add text. The first line will be the title, and the next section will be the label itself. 

If you wanted to let me know which version of Storyline you're using I can point you to a specific tutorial or record a quick video for you! 

Katie Riggio

Hi, Colton. So sorry you've come across this problem!

Although there isn't an update on a fix just yet, we promise to update everyone in this discussion as soon as new information is available. 

For now, would any of these workarounds work for your design?

  • Do not set the initial state of the marker to 'Hidden'
  • Set the slide to 'Reset to initial state' when revisiting

Let me know, and we're also happy to dig into your setup to explore any other solutions!

Charlotte Bibby

I'm hitting this issue also and there is yet another storyline bug with having the page reset to initial state which makes this painful. I have logic to change the 'next' button state to normal when the last object enters the slide. For some reason if you come back to the slide again, even though the animation replays and the object enters the slide the trigger doesn't re-enable the next button, hence the reason I had it on 'resume saved state'.

I have to say Storyline is the most buggy software I have ever used, half of knowing how to use it is knowing how to avoid and work around the many many bugs. The vast majority of which have been known about for years. I understand needing to prioritise issues to fix, however it seems to me there are too few resources put on fixing bugs and that this should be scaled up to make Storyline a tool that is pleasant to use, and hitting a bug is the exception not the norm. It is seriously making me consider changing to a different software platform.

Math Notermans

First of all, not that i donot understand you. I do, and in fact partly agree with you. Further im in no way affiliated with Articulate, im just another user that knows not only Articulate tools well ( been working with it since version 1 ) but as i work with several of the major competetitors tools too ( being Trivantis / Elearningbrothers Lectora and Adobe Captivate ) i can compare realistically.

So are they better then Storyline, especially in the fixing of existing bugs ?

On this i can answer quit honestly NO.

Both Lectora and Captivate have bugs in it that exist for years and users complaining about for years. Lectora development last years was mostly focused on CenarioVR and Lectora itself got minor attention and development time. Since shortly Trivantis has been sold to Elearningbrothers. Uptill now that has not brought much change and because Elearningbrothers has more tools under his wings it doesnot look like it is getting better. And infact the same counts for Captivate. It has always been buggy, and still is. Old bugs never got fixed, and i dont feel that Adobe cares a lot about the tool.

So if the choice is limited to these 3 competitors. Articulate wins. But i agree with you they should open up their development flow and internal bugfixing priority for customers, so we better know what to expect when.

Charlotte Bibby

Thanks for your reply Matt. I have inherited Storyline so haven't had any experience with the other products out there yet, though disappointing to hear they're not any better. It sounds like there is little incentive for Storyline to up their game then, at least until someone else invests a whole lot of money in another software platform :)

I do love some of the features of Storyline, and overall find it a pretty good tool, it's just the incessant bugs that really grate on me and make the overall experience poor. It's not uncommon for it to crash once, or more, in a day. I've lost hours of work due to these crashes and now have a rigorous save and version routine to compensate for it. Then there's the weird behavioural bugs which I can easily waste hours on trying to find workarounds. Thankfully once I've identified them I can avoid them next time. Hopefully there will be some investment in this space at some point and we see a shift to companies polishing their software a little more!

Math Notermans

Competitors for the rapid authoring tools like Storyline, Lectora and Captivate are tools like Elucidat, Adapt, Gamoteca, DominKnow One and Gomo. Alas i do think most of those are either clumsy to work with when acquainted with the Storyline workflow or are as limited as Rise. Or just to pricey... But i would advice always keep eyes open on tools like this. Depending on customer questions some might be a better fit.

This discussion is closed. You can start a new discussion or contact Articulate Support.