I get the same thing, it submits but marks incorrectly. Not sure if this is a bug or I am missing something, you can set it to submit on click instead of submit button, but I cannot get this to work, I did duplicate the button and tried other ways of submtting.
The reason why the custom button is not working is because the whole slide is an active area for your hotspot interaction. Once you click on the custom button, you automatically select it as your hotspot answer.
They suggest that I remove the custom button and use the predefined "submit" button in the player instead....
Not the answer I hoped.
A future solution should be to use the hotspot image as the active area for the interaction and not the whole slide. But that's probably not that easy to develop...
Not sure if this would work, can you add a layer that prevents clicking on the base layer add your button to that layer, add a trigger to show layer when user clicks hotspot, (you could have a transparent shape under the hotspot with a trigger to show incorrect). May not work at all
Phil's idea sort of worked (I'm using Storyline 2) but beware the underlying issue here:
The reason why the custom button is not working is because the whole slide is an active area for your hotspot interaction. Once you click on the custom button, you automatically select it as your hotspot answer.
I made a hotspot interaction manually - it was a safer option!
Hi all - I hope this thread is still active. I have an issue with freeform hotspot that I cannot figure out. First I'll say what doesn't work; then I'll describe what I'm doing. If anyone can help, it would be greatly appreciated.
I have the learner click on an image, and I supply correct & incorrect feedback. I do not use a Submit button; I just use On Click instead. Not that it should matter, but I also hide the Next button until they complete the slide - whether they get it right or wrong, I set a switch that says they completed the slide so that they can come back to the slide and then move forward again without having to redo it.
However, when I complete the slide and then Prev back to it from the next slide, it doesn't accept a click - it does nothing no matter where on the slide I click. What is curious, too, I've noticed is that the cursor turns into a pointy finger over the entire slide - EXCEPT over the hotspot!
So I cannot figure out what the heck is going on here. Would appreciate any assistance.
I thought it would be the 'resume setting' but wanted to check
with the setting 'resumed saved state' SL assumes you want it back to what it was when the user left the slide which was 'answered' correctly or incorrectly.
If you change the revisit option to 'reset to initial state' you'll be able to click again - see this Peek if this is the behaviour you are after. I only made the change on the TOS slide.
ok, I will try that - i'll look at your sample first. but the reason I said to resume to save state is so that the triggers I set would remain the same. if I change a trigger value from 0 to 1, then don't resume the saved state, then go forward a slide and then back, will the value remain at 1? (I guess I can check that myself, but that's what I was concerned with.) i'll look at your changes now.
If you are using variables they are global to the project and will not reset unless you trigger them to reset. So they don't restart on 'reset to initial state'.
25 Replies
I get the same thing, it submits but marks incorrectly. Not sure if this is a bug or I am missing something, you can set it to submit on click instead of submit button, but I cannot get this to work, I did duplicate the button and tried other ways of submtting.
May be a bug
Hi Phil
Thanks again for helping me solve this.
Like you said, it seems like a bug...
How do I report that? - Do you know that?
Best regards
Ole
you should be able to do it here http://www.articulate.com/support/contact/submit.php
I now got an answer from Support:
The reason why the custom button is not working is because the whole slide is an active area for your hotspot interaction. Once you click on the custom button, you automatically select it as your hotspot answer.
They suggest that I remove the custom button and use the predefined "submit" button in the player instead....
Not the answer I hoped.
A future solution should be to use the hotspot image as the active area for the interaction and not the whole slide. But that's probably not that easy to develop...
Not sure if this would work, can you add a layer that prevents clicking on the base layer add your button to that layer, add a trigger to show layer when user clicks hotspot, (you could have a transparent shape under the hotspot with a trigger to show incorrect). May not work at all
Hi Phil
You are my hero!
It works perfect. Thank you again
Ole
Phil's idea sort of worked (I'm using Storyline 2) but beware the underlying issue here:
The reason why the custom button is not working is because the whole slide is an active area for your hotspot interaction. Once you click on the custom button, you automatically select it as your hotspot answer.
I made a hotspot interaction manually - it was a safer option!
Hi, John -- Thanks for your input here for those who come across this thread in the future! :)
No problem Christie...we're all here to help each other out.
No doubt, John -- many thanks! :)
Hi,
It,s almost four years ago but it helps me a lot
Thanks
Delighted to hear this oldie-but-goodie discussion is still coming in handy, Amol! Thanks for the update. :)
A very late thanks to everyone. the layer worked - I was just wrestling with this one today.
Best, Steve
Awesome Steve! Thanks for popping in to share.
Hi all - I hope this thread is still active. I have an issue with freeform hotspot that I cannot figure out. First I'll say what doesn't work; then I'll describe what I'm doing. If anyone can help, it would be greatly appreciated.
I have the learner click on an image, and I supply correct & incorrect feedback. I do not use a Submit button; I just use On Click instead. Not that it should matter, but I also hide the Next button until they complete the slide - whether they get it right or wrong, I set a switch that says they completed the slide so that they can come back to the slide and then move forward again without having to redo it.
However, when I complete the slide and then Prev back to it from the next slide, it doesn't accept a click - it does nothing no matter where on the slide I click. What is curious, too, I've noticed is that the cursor turns into a pointy finger over the entire slide - EXCEPT over the hotspot!
So I cannot figure out what the heck is going on here. Would appreciate any assistance.
Thanks
Stuart
Oh, I wanted to add: I select Resume saved state on every layer - the base layer as well as the correct & incorrect layers.
Thanks again.
sjg
HI Stuart
it would be helpful if you could upload the .story file so we can work with the setup and see what's happening.
Okay, let me try to do that. I'll create a version that has just those slides. Gimme a minute. And thanks very much.
This has 4 examples that are basically all the same. Let me know if anything jumps out at you.
Thank you!
Hi Stuart
I thought it would be the 'resume setting' but wanted to check
with the setting 'resumed saved state' SL assumes you want it back to what it was when the user left the slide which was 'answered' correctly or incorrectly.
If you change the revisit option to 'reset to initial state' you'll be able to click again - see this Peek if this is the behaviour you are after. I only made the change on the TOS slide.
The #ofAttempts for the hotspot interactions is set to 1 and therefore will not accept another click when you return to the slide.
ok, I will try that - i'll look at your sample first. but the reason I said to resume to save state is so that the triggers I set would remain the same. if I change a trigger value from 0 to 1, then don't resume the saved state, then go forward a slide and then back, will the value remain at 1? (I guess I can check that myself, but that's what I was concerned with.) i'll look at your changes now.
Thank you!
if I may - two follow ups
1. should I change it to Automatically decide, or to Reset to initial?
2. I assume I need to do that on all layers (base, correct, incorrect)?
If you are using variables they are global to the project and will not reset unless you trigger them to reset. So they don't restart on 'reset to initial state'.
Great. Thank you very much Wendy (and Michael), I really appreciate it.
This discussion is closed. You can start a new discussion or contact Articulate Support.