I am creating a Freeform Drag and Drop screen and I am having trouble with a custom submit button.
If I use the standard player submit button, the Drop Correct and Drop Incorrect states change as expected when the submit button is clicked. If it was dragged in the correct spot, it turns green. If it's not, then it turns red.
If I use a custom button to trigger the submit interaction, the Drop Correct and Drop Incorrect states on the dragged items do NOT change to their appropriate states. They just stay at their normal states.
Why don't they work the same regardless which button you press? I am literally just changing the button to press in the trigger and it doesn't work.
Hi Liz! This issue is actually something that has been submitted to our QA Team. Unfortunately, I cannot offer a timeline of when this issue will be corrected. In the meantime, I would recommend using the Player's Submit button.
I used the standard states Drop Incorrect and Drop Correct. I made those states exactly like the Normal State. I created 2 custom states, RIght and Wrong. The right is green and the wrong is red.
I added a submit button and converted the slide to a free form drag and drop.
The I added some triggers to my Submit button.
The first submits the interaction
The next changes the state of drag object 1 to Right when the uer clicks the submit button IF the state is Drop Correct (see below)
Then I just another trigger to change the state to wrong when the user clicks the submit button IF the state is Drop Incorrect
I did this for each drop item, it seems to wirk as you want it to.
Thank you Leslie for confirming I wasn't a crazy person. Good to hear it's already on the fix list at least.
And Garth, you're a god-send. Thank you! I was going crazy with about 20+ different permutations and none were working. Yours did the trick. Thanks again!
The sequence of the triggers is sometimes important. They occur in sequence from the top of th elist of triggers to the bottom. If a trigger fires, for example a change state trigger, before he submit interaction trigger, you may not get the exected result.
It is hard to troubleshoot without seeing what you have, if you can upload your file, I am happy to take a look and see if I can help you fix what is not working.
I'd agree with Garth, it'll be easier to understand your set up if you're able to share your .story file here with us. You'll want to use the paperclip icon to attach it here. Also depending on how large your file is, it may exceed the upload limits of the forums (around 20mb I believe) you may want to place the .story file in a public Dropbox folder and share that link with us here.
I think I have managed to fix it after replicating a drag and drop several times, I seem to have managed to get it to eventually work. So strange as I have repeated the same thing over and over again, but then suddenly it began to work how it was suppose to.
That happens from time to time, and you'll just want to ensure you're working with local project files to prevent any odd behavior. If Storyline continues to behave erratically, you may also want to conduct a repair of Storyline.
As a heads up, I discovered that you have to leave the check box unmarked for "Delay item drop states until interaction is submitted" for this solution to work. :-)
Hi - I was having the same problem but the solutions above didn't work. I did figure out (almost by accident) a workaround so I'm documenting in case someone else comes across this thread and is in despair. :)
In my D&D I had a 'group' dropping onto a hotspot. The group was a shape and text box and I wanted to keep it that way rather than a picture, to make translation easier and because the picture just didn't look as crisp. I had the 'drop correct' and 'drop incorrect' states on one element in the group. However, it was apparently that the custom submit button did not like grouped items. (The inbuilt button worked fine.)
Thinking maybe that the group was the problem, I replaced one group reluctantly with a picture and tested it - lo and behold all the other groups worked when I did this! So after much testing and retesting I figured out that having just one picture and hotspot meant everything else worked. I created a dummy picture and hotspot and hid them and added them to the interaction. The picture needed to be on the slide in an appropriate place, otherwise the other answers when randomized seem to fly everywhere out of place. So I just hid the fake picture answer under one of the real answers (my hotspot is offscreen and that doesn't seem to matter). Voila!
I expect this would probably mess up scoring but I'm using an manual scoring method so that didn't effect me. Just a heads up on that.
13 Replies
Hi Liz! This issue is actually something that has been submitted to our QA Team. Unfortunately, I cannot offer a timeline of when this issue will be corrected. In the meantime, I would recommend using the Player's Submit button.
I have a way to do what you want.
I used the standard states Drop Incorrect and Drop Correct. I made those states exactly like the Normal State. I created 2 custom states, RIght and Wrong. The right is green and the wrong is red.
I added a submit button and converted the slide to a free form drag and drop.
The I added some triggers to my Submit button.
The first submits the interaction
The next changes the state of drag object 1 to Right when the uer clicks the submit button IF the state is Drop Correct (see below)
Then I just another trigger to change the state to wrong when the user clicks the submit button IF the state is Drop Incorrect
I did this for each drop item, it seems to wirk as you want it to.
File attahced.
Thank you Leslie for confirming I wasn't a crazy person.
Good to hear it's already on the fix list at least.
And Garth, you're a god-send. Thank you! I was going crazy with about 20+ different permutations and none were working. Yours did the trick. Thanks again!
Hi Liz! No problem at all. Thanks to Garth for providing a creativesolution for you as well.
Hey Garth,
Thanks for you solution, this may just save my day. However, I have recently carried out your method and its still not working for me?
I have downloaded your example and have my story set up the same way, still to no avail.
Any help would be appreciated.
The sequence of the triggers is sometimes important. They occur in sequence from the top of th elist of triggers to the bottom. If a trigger fires, for example a change state trigger, before he submit interaction trigger, you may not get the exected result.
It is hard to troubleshoot without seeing what you have, if you can upload your file, I am happy to take a look and see if I can help you fix what is not working.
Hi Wesley,
I'd agree with Garth, it'll be easier to understand your set up if you're able to share your .story file here with us. You'll want to use the paperclip icon to attach it here. Also depending on how large your file is, it may exceed the upload limits of the forums (around 20mb I believe) you may want to place the .story file in a public Dropbox folder and share that link with us here.
I think I have managed to fix it after replicating a drag and drop several times, I seem to have managed to get it to eventually work. So strange as I have repeated the same thing over and over again, but then suddenly it began to work how it was suppose to.
Thanks anyway Garth, I maybe back very soon.
Hi Wesley,
That happens from time to time, and you'll just want to ensure you're working with local project files to prevent any odd behavior. If Storyline continues to behave erratically, you may also want to conduct a repair of Storyline.
As a heads up, I discovered that you have to leave the check box unmarked for "Delay item drop states until interaction is submitted" for this solution to work. :-)
Ah, thanks Rebekah for popping in here and sharing.
Hi - I was having the same problem but the solutions above didn't work. I did figure out (almost by accident) a workaround so I'm documenting in case someone else comes across this thread and is in despair. :)
In my D&D I had a 'group' dropping onto a hotspot. The group was a shape and text box and I wanted to keep it that way rather than a picture, to make translation easier and because the picture just didn't look as crisp. I had the 'drop correct' and 'drop incorrect' states on one element in the group. However, it was apparently that the custom submit button did not like grouped items. (The inbuilt button worked fine.)
Thinking maybe that the group was the problem, I replaced one group reluctantly with a picture and tested it - lo and behold all the other groups worked when I did this! So after much testing and retesting I figured out that having just one picture and hotspot meant everything else worked. I created a dummy picture and hotspot and hid them and added them to the interaction. The picture needed to be on the slide in an appropriate place, otherwise the other answers when randomized seem to fly everywhere out of place. So I just hid the fake picture answer under one of the real answers (my hotspot is offscreen and that doesn't seem to matter). Voila!
I expect this would probably mess up scoring but I'm using an manual scoring method so that didn't effect me. Just a heads up on that.
Hope that helps someone one day!
Great find, Miriam! Thanks for sharing this tip with the rest of the community. 🌟
This discussion is closed. You can start a new discussion or contact Articulate Support.