Progressbar not working

Oct 17, 2017

Hello everyone,

Hopefully, someone can help me figure out what I am doing wrong. For a new project, I want to create a progress bar at the bottom of each sheet so the student can see how far in the course he or she is. This example: https://cooeeproductions.wordpress.com/2013/03/24/showing-the-learner-a-course-progress-meter-in-storyline/ is something that I wanted to recreate. 

I managed to recreate the concept but something goes wrong. When I return to a page the number of sheets visited is increased by one although the flag that should prevent this is in a selected state. 

For testing purposes, I activate the triggers at the end of the timeline so I can see what happens. When it works I want it to change it back to the start of the timeline. 

The radio button I use to check if the particular sheet has been visited already is changed correctly: the first time it is not selected, until the end of the timeline (then the state of the radio button becomes 'selected') and when revisiting the same sheet the radio button is still in 'selected' state (as can be seen during the beginning of the timeline). 

However even though the trigger must only add one to varScreensVisitedCount if the radio button is not selected, still each visit increases the number of visited sheets. This is something I do not understand. 

The strange thing for me is that when I set the radio button as selected in the master slide, the whole system works in the sense that the variable varScreensVisitedCount is not being increased by one on every visit. 

When searching this forum I noticed that I should check if in the properties of the slide the 'resume saved state when revisiting' is selected. For all sheets this is selected. 

When this concept works I want to create a progress bar of 100 states so that I can reuse it for all the e-learning modules we want to create. Now only increments of 20 percent are available as states of the progress bar because I want to test if it works first. 

By the way, I am working with the latest build of Storyline 3.

Can anyone please help me with this? Any help is greatly appreciated!

Kindest regards,
Rob

5 Replies
Rob Willemse

Hello,

Today I found out a bit more about what is causing the problem. Because the example I used was quite old I tried to recreate the same setup in Storyline 2 to see what would happen. In Storyline 2 the whole thing works perfectly. So I seem to have figured out that something goes wrong in Storyline 3: the trigger does not take into account the state of a radio button if this state has been changed previously by a trigger

The original state of the radio button is taken into account because if I change the state of the radio button on the slide master into 'selected' before previewing, the counter that counts the total number of sheets visited is not increased.

Is there anyone who can help me figure out if this idea is correct?

Thak you very much!

Kindest regards,

Rob

Rob Willemse

Hello everyone,

It seems I have found a solution to the problem and will mention it here just in case someone stumbles upon the same issue. When I recreated the triggers in SL2 and found out the mechanism works in SL2 but not in SL3 I also started wondering if it was related to states in general or state of the radio button in particular.

When I created a simple shape with 2 states the mechanism worked also in SL3. So it seems that if the state of a radio button is changed by a trigger it is not taken into account by other triggers (or something similar). However, if you change the radio button for a shape the problem is solved. To me, this seems an error in SL3 software.

Kindest regards,

Rob

Rob Willemse

Hello Ashley,

That is correct. The issue is more or less solved in the sense that I know what the problem is with the triggers and found a workaround. I just wanted to update my original question just in case someone would stumble upon it was also wondering what the cause of the problem is. It took me quite some hours to find a solution so I wanted to save someone else the effort.

There is still a minor other problem that is perhaps related to the triggers but I am hoping that Wilbert can help me to find a solution for that.

 Kind regards,

Rob

 

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