Skip to main content
A
adami48858293
Participating Frequently
April 1, 2015
Answered

Adusting a dynamic page counter

  • April 1, 2015
  • 1 reply
  • 378 views

I'm having a real headache getting a page counter to work in a module. It is a long course - 120 slides - and it features a dynamic menu and a sidebar menu that allows navigation to different sections from anywhere. It also has a glossary, available from anywhere in the course, which has a Back button that goes to the last slide visited.

I need to change the cpinfocurrentslide variable by -2, to account for two screens before the menu (one of which is the glossary). I've created a variable, display_currentslide, which is in a text caption timed for the rest of the project. I have an Enter action on the menu which has an expression display_currentslide = cpinfocurrentslide. The result is that it shows Slide 1 of 120 on every slide. I can see that the issue is that this action does not happen on every single screen - only on the menu. So one solution would be to add this as an action to every screen, on top of whatever other actions are already there. This is feasible but would take ages. I've also seen a method of adding one or subtracting one for the cpinfocurrentslide using the forward and back buttons, which would work fine for me, except that there is a glossary which you can jump to from any screen in the course. Is there any method of making it work that doesn't involve adding a new action to every single one of 120 screens?

Many thanks in advance for any advice or tips! I'm using Captivate 8.1, fully updated.

    This topic has been closed for replies.
    Correct answer Lilybiri

    I suspect you are using 8.0.1.242, because there is no 8.1 available AFAIK.

    If you want to have the variable v_CurSlide (sorry for my translation, this is my labeling way) updated on each slide, you'll have to run an action on each slide of course. Since that action never changes you can attach it to all the slides in one work flow: select all the slides in the Filmstrip (CTRL-A on Win), and enter the action name in the Actions tab, On Enter.

    However I would recommend to use a shared action (better for file size), same work flow because you'll not need to turn anything into a parameter.

    Another tip: why not display the Glossary interaction for the rest of the project as well, and use a toggle button to turn it on/off. Lot less navigation which will speed up the experience for the user since you have a long course.

    1 reply

    Lilybiri
    LilybiriCorrect answer
    Legend
    April 1, 2015

    I suspect you are using 8.0.1.242, because there is no 8.1 available AFAIK.

    If you want to have the variable v_CurSlide (sorry for my translation, this is my labeling way) updated on each slide, you'll have to run an action on each slide of course. Since that action never changes you can attach it to all the slides in one work flow: select all the slides in the Filmstrip (CTRL-A on Win), and enter the action name in the Actions tab, On Enter.

    However I would recommend to use a shared action (better for file size), same work flow because you'll not need to turn anything into a parameter.

    Another tip: why not display the Glossary interaction for the rest of the project as well, and use a toggle button to turn it on/off. Lot less navigation which will speed up the experience for the user since you have a long course.

    A
    adami48858293Author
    Participating Frequently
    April 1, 2015

    Sorry - 8.0.1.242, quite right.

    Unfortunately I already have lots of enter actions on various screens already, so I would have to go and manually add the action individually to all of those. Although, actually maybe about 2/3 of my screens still have no enter actions so I can select those only and follow your method. I didn't realise shared actions were better for file size.

    On the glossary - brilliant! That's exactly what I was trying to do but I couldn't work out how. Thanks a lot!

    Lilybiri
    Lilybiri
    Legend
    April 1, 2015

    I have several articles about shared actions on my blog. Discovered, when preparing a presentation about mobile two years ago, that shared actions replacing duplicate advanced actions do save a lot on file size. For a small app (about 100kB), that had few slides but lot of advanced actions, I could reduce file size by 35% when replacing by shared actions. Here is one link, you'll find the other articles easily

    Parameters in Shared Actions - Captivate 7 vs. 8 - Captivate blog

    For the Glossary, use a toggle shape button that can be put on master slides or timed for rest of project as well:

    Toggle Shape buttons - Captivate 6 - Captivate blog

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices