67 Replies
Tim Shelton

As a developer using this tool day to day hour by hour... I use 'currentScreen' of 'totalScreens'. I prefer to manually set the page number on each slide so its an absolute number set in stone and can never go wrong [as long as you add it to each slide and dont lose the count].

We do use the method of using an addition variable as long as its set up properly on a master slide it can prove very useful as it saves time manually setting a current number.

However depending on how the course jumping in between scenes can confuse a total screen count. Just something to be aware of.

Jerry M

I am a big proponent of non-linear navigation and I also believe that I owe it to my learners to let them see how far they have gone and how far they have left to go. 

I have designed a very clunky work around that uses variables to change the state of a progress bar as the learner progresses. All "required" or main slides include a slide_X_viewed variable that is set to 0 on course entry, and set to 1 when that slide is opened. There is then another trigger that adds that value to the number_of_slides_viewed variable whenever the slide_X_viewed variable changes. This allows the # viewed to increment when the slide is first seen, and only when it is first seen. An added bonus of this approach is that when I have A and B options that are just different ways to present the same content THey can share a slide_x variable value so that either one will count as one, and both sill count as one. 

There is also a variable that is set manually to equal the number of required slides, and a trigger to divide the #_of_slides_viewed by total_#_of_slides to produce the %_complete value, which in turn is tied to the 10%, 20%, 30%, etc. states of the progress bar. Most of this code lives on the slide master so it is relatively easy to maintain. 

I told you it was clunky. 

Tim Fisher

I hope that the Articulate creators are aware of how much time and energy the community is exerting in creating "clunky" workarounds. It seems as if the time spent paradigm shifting that was referenced earlier in the thread is actually spent creating features that should be built into the program as a default...

Steve Flowers

Hey Jerry - 

I have a similar method that uses a JavaScript trigger on the master slide to calculate by adding to an array. The bonus of this method is I can use the same Javascript trigger to check for a custom array state for completion, checking the array positions for completed / visited.

I use the same setup for slide number per slide with a trigger that sets a cslide number variable. It's not tough to setup and slide view makes updating the numbers a breeze. A listener on the master triggers a JS trigger whenever this number variable changes. The JS trigger takes the number and sets the address of the array equivalent to the slide number to 1. 

1,,1 is the result of slide 1 and slide 3 visited. Using this, you can then calculate the length of the array and create a function to add up the values to create a progress value.

Leslie McKerchie

Hi Phillip! 

Not by default, which is why there are so many variations and suggestions here. Due to all the branching and triggers options within Storyline, page numbers would be difficult.

Hopefully some of the community suggestions will be able to assist you.

You are welcome to share your thoughts with our product development team here.  

Steve Flowers

Quick answers:

  • Automatic page numbering is not available in Storyline 1 or 2. 
  • Custom elements (like a page number) can't be added to the player.

However, adding your own custom page numbers to the slide area is not difficult or complicated.

I usually add a temporary element to the master slide containing a variable reference %pageNumber%. This allows for moving the page number or simply deleting it when it's no longer needed.

In Story View, it's easy to add triggers to each slide to adjust the variable pageNumber when the timeline starts. Most frequently, I'll simply make the slide number value match the slide value in story view (1.2, 2,1, 2.2, etc..)

Having the slide reference is really critical for targeted review feedback. Would be nice to have the page number available as a system variable. Not a reality in this version. 

 

 

Phillip Robinson

Your spot on Steve. That is exactly why I want to  display the screen number - for targeted review feedback. As easy as it may sound to instruct reviewers to simply click the Menu tab for the screen number, it rarely happens and you continually get the feedback "I couldn't tell what screen I was on but, this didn't look right."

If I place "Screen number: %PageNumber%" at the top of each slide in the Slide Master, will it display what ever the slide vale is? 

 

Alex Young

Hi folks:

This is only four years late but hey....
Add a variable called pgn with default value of 1 and add it to each slide in a text box %pgn%.

Starting on page two add the following triggers to the Triggers section of each page. 
Ensure that the 'subtract' trigger appears first in the Player Triggers section or it will not work. 
This is a workaround. The only issue with it is that when you select the previous button the page number will flash (nano-second) the page number minus one. After this brief flash the page number will appear properly. 

 

Trigger Page

Best Regards
Alex
Toronto

 

Matthew Bromwich

I managed to get the correct page numbers in when jumping around by assigning the %PageNum% variable that I created with a specific value at the beginning of each scene.  For example, if you started at the very beginning of the course it was set at 1, and next/prev would add or subtract it.  If you jumped to scene 3, then I adjusted the variable on start of that scene to be 3, so that counting would start from there (in this example each scene was only 1 page).  It does mean that if you add more pages in later you will have to adjust the default value at the beginning of each chapter which could be a pain.  I also added these page number onto the master slides, as well as the increment and decrement triggers to the master so I only had to do it once, instead of on each slide as some people have discussed.