Skip to main content
M
MicaOli
Known Participant
June 30, 2016
Answered

Any idea what is going on with the advanced actions panel? See img below

  • June 30, 2016
  • 1 reply
  • 267 views

Whenever I try to add a variable action for my script, when I save, all the fields where the variable is supposed to be end up like this, and I have no idea why. It does this with standard actions too.

This topic has been closed for replies.
Correct answer Lilybiri

You are on the very first release of 9. That bug was patched very quickly (in September or October 2015). Please install the update to 9.0.1.320 released a couple of months ago, that includes the patch as well. This happened to upgraded conditional actions: some were converted to shared actions.

Why do you use a conditional action instead of a standard action in this case? Or do you have multiple decisions?

Be careful with names: you cannot use same name twice, even not for totally different things. Maybe it was not a typo, but I see 'opcion22' for an action and 'option'22' for an object with states. It is much better to keep to a naming convention to avoid having issues.

1 reply

Lilybiri
LilybiriCorrect answer
Legend
June 30, 2016

You are on the very first release of 9. That bug was patched very quickly (in September or October 2015). Please install the update to 9.0.1.320 released a couple of months ago, that includes the patch as well. This happened to upgraded conditional actions: some were converted to shared actions.

Why do you use a conditional action instead of a standard action in this case? Or do you have multiple decisions?

Be careful with names: you cannot use same name twice, even not for totally different things. Maybe it was not a typo, but I see 'opcion22' for an action and 'option'22' for an object with states. It is much better to keep to a naming convention to avoid having issues.

M
MicaOliAuthor
Known Participant
June 30, 2016

I have update 9.0.1.320... I intalled it a few months ago, not last year. I use conditinal actions in case I have to include an if. You can "convert" a contitional action to a standard, but not the other way round.

Lilybiri
Lilybiri
Legend
June 30, 2016

Is this an action updated from an older project? What you are seeing is how a shared action would look, but not totally since I would have expected more parameters.

I will not discuss about unnecessary use of conditional actions for standard actions. To me it is as easy to copy all statements of a standard action to a new conditional action as the reverse. My feeling is that I shouldn't not add another condition when it is not necessary. Just a personal opinion.

It the problem continues, I suspect corruption of the Preferences folder. Do you have a lot of customisation? If not, run the CleanPreferences file for your OS which you can find in the subfolder 'utils' under the Captivate installation folder. The application has to be closed.

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