I can't get my custom 'next' button to submit a 'pick one' freeform interaction (set up triggers for the button to first 'submit interaction - pick one' and then 'jump to slide - next'.
When I enable the player's 'submit' button on that slide, everything works fine.
I would happily upload, but the module is in Hebrew, so I doubt it will help.
There are 11 pictures, all 100% transpartent (but up front) that are possible choices for this interaction. They all sit on a background image which is not a choice and is in the background. Each of the choices has a 'selected' state with a blue circle on to give the user feedback.
My custom 'Next' button has been tested with the 'submit interaction' trigger, and with the 'jump to next slide' trigger after it, with no luck.
When i enabled the actual player's 'submit' button - everything worked as expected.
PS. These 11 images were all shapes (rectangles, L-shapes, and groups of shapes) But were converted to pictures after I read some of the boards here recommending to do so.
There are 11 pictures, all 100% transpartent (but up front) that are possible choices for this interaction. They all sit on a background image which is not a choice and is in the background. Each of the choices has a 'selected' state with a blue circle on to give the user feedback.
I have created a sample of what I think you are describing but I don't understand how the user knows where the 11 images are if they are 100% transparent?
In my sample, I know which is the correct answer and I can by using a custom Next button, submit the transaction and move to the next slide. I have then put in a result slide to confirm that my interaction is being submitted and it is. My submit transaction trigger is first then the jump to next slide trigger.
I must be misunderstanding what you are trying to achieve.
Thanks for reproducing and good news that it's working on your end!
Apologies if I wasn't clear, here's the crucial bit of information I missed:
the question is addressing a background picture of one octave of a piano keyboard. each of the 11 keys (minus a starting key) are options for the 'pickone' interaction, and they all have 'selected' states that include a blue circle marking.
Sorry Erez I'm tapped out - without seeing the file I can't think of what else to check. Perhaps someone else will chime in to help you or you could log a support ticket with Articulate.
I'm not staff just a forum user trying to help - happy to take a look if you want to email me privately but if not you'd need to log a ticket with support with the link I supplied above.
Looks like you were able to get your issue submitted to our team (00741746) and you should be hearing from someone soon. I will be happy to follow along as well.
I actually worked around it by placing the 'next' button on a seperate layer, which would show up only after the user has selected an option. Can't explain why it didn't work on the base layer, but it's working now...
14 Replies
Hi Erez
can you upload your story file - easier for someone to help you if they can see the setup
Hello Wendy,
I would happily upload, but the module is in Hebrew, so I doubt it will help.
There are 11 pictures, all 100% transpartent (but up front) that are possible choices for this interaction. They all sit on a background image which is not a choice and is in the background. Each of the choices has a 'selected' state with a blue circle on to give the user feedback.
My custom 'Next' button has been tested with the 'submit interaction' trigger, and with the 'jump to next slide' trigger after it, with no luck.
When i enabled the actual player's 'submit' button - everything worked as expected.
PS. These 11 images were all shapes (rectangles, L-shapes, and groups of shapes) But were converted to pictures after I read some of the boards here recommending to do so.
I have created a sample of what I think you are describing but I don't understand how the user knows where the 11 images are if they are 100% transparent?
In my sample, I know which is the correct answer and I can by using a custom Next button, submit the transaction and move to the next slide. I have then put in a result slide to confirm that my interaction is being submitted and it is. My submit transaction trigger is first then the jump to next slide trigger.
I must be misunderstanding what you are trying to achieve.
Hello Wendy,
Thanks for reproducing and good news that it's working on your end!
Apologies if I wasn't clear, here's the crucial bit of information I missed:
the question is addressing a background picture of one octave of a piano keyboard. each of the 11 keys (minus a starting key) are options for the 'pickone' interaction, and they all have 'selected' states that include a blue circle marking.
Ok are you saying the keys are in initial state of 'selected'?
Can you upload a screenshot of the slide and also the states of one of the 'transparent' keys.
Nothing has an initial state of 'selected'.
The 11 options (100% transparent png in the shapes of the keys) are initally 'normal' and their 'selected' state contains the blue circle
Erez
in the form view of the Pick One do you have those 11 images listed and then the correct button against the 'correct response'?
That's correct, I did that. Also clicked 'remove freeform' and then 'convert to freeform' and repeated the process.
Sorry Erez I'm tapped out - without seeing the file I can't think of what else to check. Perhaps someone else will chime in to help you or you could log a support ticket with Articulate.
Thanks Wendy. I would happily share the .story privately if you are interested.
Hi Erez
I'm not staff just a forum user trying to help - happy to take a look if you want to email me privately but if not you'd need to log a ticket with support with the link I supplied above.
Hi Erez!
Looks like you were able to get your issue submitted to our team (00741746) and you should be hearing from someone soon. I will be happy to follow along as well.
Hello,
I actually worked around it by placing the 'next' button on a seperate layer, which would show up only after the user has selected an option. Can't explain why it didn't work on the base layer, but it's working now...
Thanks for popping in with an update Erez and for sharing your solution with the community.
This discussion is closed. You can start a new discussion or contact Articulate Support.