Skip to main content
A
annek33152065
Participating Frequently
June 7, 2016
Answered

Recursive Actions?

  • June 7, 2016
  • 2 replies
  • 790 views

First of all: Sorry for my bad english

Second: Is it possible make an advanced action recursive?

The problem in detail:

I have to design an alternative memory game. So I made the slide 3 with a pattern of about 24 buttons.

A short peek-view shows the 3 right buttons. Goal of the game is to klick all 3 buttons in about 10 seconds.

If this happens the user should get to slide 5. If he klicks 1 wrong button he will get to slide 4.

I made 3 variables Button01 and gave them the literal "FALSE" - I hope this makes them boolean-like.

By klicking the right Buttons i made advanced actions, which allocats their values to the literal TRUE.

For the whole slide i made the advanced option:

IF (Button01 == TRUE && Button02 == TRUE && Button03 == TRUE)

     go to layer 5 slide 5

The problem is, that this advanced action just starts if the user reaches slide 3 and after this it won't start again.

Is there a possibility to make this advanced action recursive or can I trigger it within the advanced actions of the buttons?

Thanks a lot

    This topic has been closed for replies.
    Correct answer Lilybiri

    Ah, I see. You're right. It's my quasi my first day with AA.

    Now I understand the condition and it makes sense, but something still isn't working.

    In the meantime I cleared all the other faults like the one in the timeline, included a timer etc etc

    Everything works fine now except the right buttons. Is it possible, that the preview doesn't allow AA?

    I know a similar problem in Articulate Storyline.

    The current Buttons-AA:

    Like You said. Duplicated for the other buttons and changed the assignments, but in the preview I just see all 3 activated Buttons till the time is up and navigating to the new slide 5 (success is slide 6 now).


    Do not compare SL with Captivate, please, they do not have advanced actions, which are converted to JS or AS on runtime depending on the output.

    Not at all, everything should work perfectly, there must be another cause.

    It has no sense at all to make that slide that long. Keep to the default 3secs, with a pausing point at 1.5secs.

    Check in the Advanced Interaction panel (F9) if the correct advanced action is triggered by the correct button.

    To debug: add a text container on that slide (shape of caption), time if for the rest of the slide (Continue) and insert the three variables: (mine were labeled v_one, v_two, v_three) using the X-button in the Character part of the Properties panel. When previewing: you should see the variables change. Do you realize that variables are case sensitive, that is one of the reasons I would NEVER use 'TRUE/FALSE'. Are you sure you have exactly the same value for the variables as you are checking in the second decision? Use numbers, so much easier, less risk for typos.

    You should be careful with labeling as well. You cannot use the same name for an action and a button, nor for a variable and an action/button. I don't see it in your screenshots, but it is a tip. That is the reason why I start any object (not actions/decisions) with at least one character defining the type: v_ for variables, SB for shape buttons (I didn't use normal buttons, but shape buttons in the example).

    2 replies

    Lilybiri
    Lilybiri
    Legend
    June 7, 2016

    Although I totally agree with Rod about CpExtra's extension of Captivate functionality and time saving, I have been creating some games long ago. It would now be already a lot easier in Captivate 9 (you don't tell which version you are using?) by using states and shared actions. Here is a link to such an old game. (I am busy writing out the modern alternative for a future ebook about advanced/shared actions at this moment):

    http://blog.lilybiri.com/concentration-game-created-exclusively-with-c

    If you want help, you have to offer more details: which events are you using exactly for each action and screenshots of the complete actions. For conditional actions, use the Preview button (looks like a play button, first top right of the AA window) to see the total action with all decisions.

    As for Booleans, I will mostly go with 0/1 instead of False/True, but maybe I'm just lazy. Normally both would work.

      A
      annek33152065Author
      Participating Frequently
      June 7, 2016

      Thanks for Your offer. I am using the current Captivate CC-Version. My Screens are in german, but I hope you can see what I mean

      First the Overview:

      The Preview of the action on the slide:

      The variables:

      The button:

      Lilybiri
      Lilybiri
      Legend
      June 7, 2016

      German is not a problem, I'm Flemish, my mother tongue is Dutch.

      I don't see the complete picture, I think you misunderstand the meaning of a pausing point of interactive objects as well. You cannot force that 10 seconds with the timeline at all!  Your buttons have all one-line advanced actions which means that the playhead will never be released but remains at 10 seconds. The user will get as many time as he wants. That is my first remark. You should need the Timer or Hourglass interaction to force that time limit.

      Secondly: be careful because you attach the end point of the buttons to the end point of the slide (red triangle). More often than not, this is not what you want at all. You cant to extend the button timelines till the end of the slide, use CTRL-E but first get rid of the red triangles.

      I suspect the 'wrong' buttons have the navigation to slide 4. Did you set up 24 buttons? Or do you use the Last attempt actions for the correct buttons?

        RodWard
        Community Expert
        RodWardCommunity Expert
        Community Expert
        June 7, 2016

        Default Captivate behaviour does not allow one Advanced Action to trigger another Advanced Action.

        However, if your output is HTML5, the CpExtra widget does make it possible to trigger an action from within another action.

        If you are publishing to SWF, you may need to use one action to jump to another slide where the On Slide Enter event can trigger your desired Advanced Action and then jump back to your original slide again.  It's a workaround, not a perfect solution.

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