Skip to main content
Known Participant
June 4, 2024
Answered

Is There a Limit to the Number of Advanced Actions on a Slide?

  • June 4, 2024
  • 3 replies
  • 7281 views

Hi All,

 

I have gotten wolf-howling-at-the-moon crazy with a Captivate Classic (11.5.5.553) project that has a lot of text and audio being toggled via Advanced Actions. I am trying to initially HIDE a Continue button and then have this appear if certain criteria are met.

 

The way the Continue button is set to initially hide is to have the slide Advanced Action set to HIDE this button based on an IF criterion. I am actually using this slide AA, that is needed for navigation later, to serve a dual purpose.

 

Issue I have is when I have this HIDE button action set, along with several other HIDES, the slide breaks and automatically goes to the next slide when the Continue button is clicked, in violation of AA rules set for that button.

 

If I take this HIDE Button away from the slide AA, then the slide behaves as expected, but it appears on screen at an undesired time.

 

Have I maxed out the system?

 

Thank you for any thoughts.

 

    This topic has been closed for replies.
    Correct answer RodWard

    I find the best way to debug complex interactions like this where you have multiple variables that affect multiple conditional decision blocks is to make the current values of all variables visible to you (the developer) at runtime.

     

    You just need to find a spare spot on the problem slide to insert a text caption or smart shape in which you display the custom user variables that are influencing the Conditional Advanced Actions. 

     

    If the interaction is not working as expected, it will either be due to a flaw in your logic.  And the usual reason for that is that one of the variables you assume will have a certain value does not actually have that value.  So, by making the variable values visible at runtime you can have better visibility of what is happening "under the hood".

     

    I would reiterate my earlier instruction that you do not always need to make every decision block have a condition at the top.  If certain objects will always need to be hidden on enter to that slide, just use the first decision block in the Advanced Action to hide them all.  Then if some are going to be unhidden later based on variable values, do that via conditions in the subsequent decision blocks.

     

    Lilybiri is correct that Shared Actions can be very useful.  But I would not suggest trying to convert this interaction to Shared Actions until you have debugged the current way it is working.

    3 replies

    Known Participant
    June 5, 2024

    Thank you Rod and Lilybiri!

     

    I do have the On Enter Execute Advanced Actions to control the slide opening. But a conditional statement is needed to control a navigation control later. 

     

    And to compound things.....part of the desired operation of this slide is:
    Click 4 buttons to view content.

    If each of the 4 topics buttons are not clicked, and the Continue button is visable,display message.

    If each of 4 topics are clicked, go to next slide.

     

    I have this constructed with four variables, one for each topic, and that variable is incremented by 1 upon click.

    By way of test, if I click on one topic 2 or 3 times, then click a second topic, I get the warning message. This is as expected.

    If I click the rest of the topics I still get the warning when the Continue button is clicked and the slide will not advance.

     

    That is illustrated in the "Continue.png" screenshot, and ignore the blue rectangle. I have played with using a mask to hide the Continue button until needed, but that isn't working either. There is something amiss with the way the Continue button is evaluating. I suspect it is the PAUSE in the ELSE but Continue sends the project to the next slide, so I am out of ideas for this. See the AA for THIS in the "Continue-AA.png".

     

    Youall are wonderful, thank you again for the time and expertise you are sharing. Over the years, I would have been lost without this resource.

     

     

    RodWard
    Community Expert
    RodWardCommunity ExpertCorrect answer
    Community Expert
    June 5, 2024

    I find the best way to debug complex interactions like this where you have multiple variables that affect multiple conditional decision blocks is to make the current values of all variables visible to you (the developer) at runtime.

     

    You just need to find a spare spot on the problem slide to insert a text caption or smart shape in which you display the custom user variables that are influencing the Conditional Advanced Actions. 

     

    If the interaction is not working as expected, it will either be due to a flaw in your logic.  And the usual reason for that is that one of the variables you assume will have a certain value does not actually have that value.  So, by making the variable values visible at runtime you can have better visibility of what is happening "under the hood".

     

    I would reiterate my earlier instruction that you do not always need to make every decision block have a condition at the top.  If certain objects will always need to be hidden on enter to that slide, just use the first decision block in the Advanced Action to hide them all.  Then if some are going to be unhidden later based on variable values, do that via conditions in the subsequent decision blocks.

     

    Lilybiri is correct that Shared Actions can be very useful.  But I would not suggest trying to convert this interaction to Shared Actions until you have debugged the current way it is working.

    Known Participant
    June 5, 2024

    Ahh...great ideas, thank you!

    Yeah, I was on overkill mode when it came to hiding content. I will thin the herd and see what happens.

    Now, how do I display the variable values visible? I had been hoping for this type of feedback but had no idea it was available.

    Lilybiri
    Legend
    June 5, 2024

    You are using the most stable version ever,  keep it like a treasure. 

    I agree partially with Rod about his suspicion that some logic flaw will probably be the cause. However I have seen projects (and debugged them) which started to choke on the amount of variables and advanced actions. I remember one with hundreds of variables and advanced actions, which I reduced to about 20 variables and almost exclusively shared actions to replace the tons of duplicate advanced actions. But it is true that I never have experienced a limit to the number of actions on a slide. From your description it looks like they'd better be multiple instances of one shared action.

    If you don't post a preview of the used actions (use the Preview button in the AA dialog box) + a screenshot of the timeline, it is difficult to help you out.

    Shared actions take a little shift in mindset. Look at this blog post, where I explain a situation which is a little bit similar:

    Tips and Tricks: Advanced to Shared action (intermediate) - Captivate blog (lilybiri.com)

     

    RodWard
    Community Expert
    Community Expert
    June 5, 2024

    It is extremely UNLIKELY that your issue is due to having maxed out the number of Advanced Actions on a slide.  I have never encountered a limit of that type with Captivate 2019.

     

    The most likely reason for your issue is that you have inadvertently created some kind of endless loop with the logic in your current Advanced Actions.  The fact that everything works when you just remove one action would tend to support that view.

     

    Personally, if all you need to do is have the button hidden from the beginning of the slide then I would suggest you just use the On Slide Enter event to hide the button, or if there are several other things that also need to be hidden at that time then just use the On Slide Enter event to execute an Advanced Action that does everything required to set the slide up.  You probably do not need to have a Conditional statement attached to the block that hides the button.  Other blocks in the AA might need to have conditions, but you can opt NOT to have a condition by simply not selecting that checkbox on the decision block.