How do I use the result of radio widget selection to "show" a textbox?

[nikolausm82011740]

Hello again,

I have a question regarding widgets.

What I want to do is to take the result of radio button widgets (in this case 1 of 2 rather longer sentences that were offered) and use that to make a text box appear on another screen.

Background: I have a series of slides where I ask the learner questions through Radio button widgets and hence I get a number of variables (= sentences) they choose.

The issue I have is that I want to display all the choices they made on 1 page. As the possible answers are relatively long I run of out space if I simply insert

the variables to be shown as such and/or the font gets too small.

So my idea is to use the answer they choose to make a text box with a shorter version of the same sentence appearo on that "results" slide.

So my idea is to have the learner make their selection and then use an advanced action to check which answer (= which radio button) they clicked on.

This I would do through "if variable XYZ" "contains (one key word of the long sentence)" then "show textbox YZ" etc.

Question 1: Is this the easiest/most practical way or can I save myself time somwhow?

2. Does "contain" in an adv. action mean the exact text or can it be just one of the words (out of the long sentence that could be selected)? I am asking because then I would have to use the exact same long sentence in the aa which seems clumsy.

3. I would have to create a separate advanced action for each radio widget I used. Is that correct?

4. If I then have say 5 adv. actions for the various questions I asked what should trigger these advanc. action? The aim is just to abbreviate the long sentences in the selections made?

If I use "on enter" for the whole screen I just have triggered one, haven´t I?

Lots of probably of wrong assumptions on my part I guess...

Any help is greatly appreciated!

[Lilybiri]

Give me a real sentence, and the abbreviation that you want to see, and I will try to offer you a step-by-step.

One wrong assumption is that you suppose you can trigger an advanced action with the radiobuttons interaction, which is NOT the case because it is a static interaction, not an interactive interaction (sorry but that is the Captivate terminology which I try to use in a consistent way but it can be very confusing). Download the table you can find here:

Tips - Learning Interactions - Captivate blog

[nikolausm82011740]

Hello again,

I did read your post on widgets of course! I wasn´t sure if some things had changed since then.

E.g.

"Not interrupt the class and ask the question after the class, if they ask at all"

should just become "no interruptions/questions asked after class" or such.

Thanks a lot!

[Lilybiri]

You had me smiling with the 'of course'! I always suppose nobody finds my blog. There is an issue for me with the forums at this moment, cannot see the 'nicknames', which means I don't recognize users as easily as I use to.

Can I suppose that each radiobuttons interaction is on its own slide? And that you have a button to go to the next slide? That button can be used to trigger the action. 

You create a variable for each radiobutton interaction. I will label the one for this example v_class. If you have quite a lot of interactions, I would suggest using two dummy variables v_one and v_two that will store the short version of the sentence to be preserved. Those variables could be reused on each slide, if you use the On Enter action of the slide, something like this:

• Assign v_one with 'no interruptions/questions asked after class'
• Assign v_two with 'lorem ipsum'

If you convert this two line standard action in a shared action, with the two short sentences as parameters, you can reuse that shared action on each slide. The end result of a slide would be that the specific variable for that slide, which is associated with the radiobuttons gets the proper value. This can be done with a conditional a action like this:

   IF  v_class contains interrupt  AND

        v_class contains question

     Assign v_class with v_one

  ELSE

     Assign v_class with v_two

Again, I would recommend to use a shared action, for which you indicate both literals (in this case 'interrupt' and 'question') as parameters. You'll have to choose good literals, that will not appear in the other choice, that is the reason why I choose to have at least two conditions combined with AND.

[nikolausm82011740]

Thanks a lot for your time!

a. Can I suppose that each radiobuttons interaction is on its own slide? And that you have a button to go to the next slide? That button can be used to trigger the action. 

Yes, but I already use that "continue" button to check whether the user made any selection at all using your "null" variable trick!

Any ideas how to prevent them from just moving to next slide without any choice while at the same time doing your "assign with" thing?

b. I understand the shared action approach.

Am I correct in understanding that the v_one for each slide I get through this approach is then simply inserted by me on the final slide as "$$v_one$$"?

c. If so, how do I (and CP9) distinguish between the different slides each of which has different answer at the end?
Stupid question I know but I am stuck at this juncture...

[Lilybiri]

For the Next button, combine both conditions in one conditional action. Sequence will be important!  I want to try it out, suspect we'll need three decisions to avoid that v_class is populated with v_two if the user didn't choose any button. I now want to prepare/have lunch first, is that OK?

You misunderstood partially. The unique variable, associated with each radiobuttons interaction will have the text you show on the final slide, not v_one or v_two who will be redefined on each slide.

[nikolausm82011740]

Good lord, please go eat your lunch in peace and quiet!

I will try the v_one thing and see where it takes me.

Yes, I also feel that I haven´t fully grasped it yet. But I will get there!

[Lilybiri]

OK, worked it out and will give you some screenshots (maybe a new blog post?):

Here is the On Enter action:

The two dummy variables need not to be defined as parameters.

For the Next button:

Three decisions will be needed as you can see. I converted it into a shared action, and here you see parameters for your example. I wrote 'word' but it can also be a sequence as you see in this example:

End result, that can be inserted in a text container is for this slide the content of v_class. Because that content is changed by the action, the radio buttons answers will be unchecked immediately.

[nikolausm82011740]

Thank you so much.

To recap, we have the learner choose an answer, then this long sentence gets exchanged with a short version in the var (=container for text).

So after that when I insert $$answer1$$ for example I get the short version for that answer on the final summary screen?
Is that correct?

Wow...brilliant.

[Lilybiri · Accepted solution]

In my example the var that will get the short sentence is v_class. It is always the variable associated with the radio buttons interaction. You will have as many of those variables to be inserted on the final slide as you have radio button interactions. Please, never type in the variable to insert, but use the X button in the Character part of the Properties panel for the text container. Variables are case sensitive, that way you'll avoid typos.

[nikolausm82011740]

I see! For me it is $$answer1$$.

Actually I always use the X!

Will try and report back!

Thanks.

[Lilybiri]

You could see that I created the example and tested it thoroughly.

[nikolausm82011740]

It worked! Thank you so much!

[Lilybiri]

Congratulations!