I have a problem that I can't solve. I have a drag-and-drop interaction and when I try to complete it I see the error "You must complete the question before submitting". I removed the button and the placeholder for the right answers from all groups but it is still not working.
I've also read all other discussions on this issue and nothing works for my situation. I Attached the file below.
Creating a Hover state for an object gives it superpowers, one of which is to automatically change to the Hover state when the cursor hovers over it. When you create another trigger that duplicates that action, it frequently conflicts with the built-actions. The results of those conflicts are unpredictable, sometimes spectacular, but almost always undesireable. In this case, they cause the error message you are seeing. Delete all those "hover" triggers, and see if it works.
An additional fact is that all the states on the drop-down name menu for new states behave the same way - they can handle their native function, and resent any interference. :)
I'll suggest not to create a custom state when there is a built-in state, it might cause glitches. With build-in states, you don't need to set triggers and that can save you time. Take a look at the modified file attached to see details about what I mean.
Actually, the built-in states are very good at what they do, but they are limited only to that. The best reason to create custom states is to have the flexibility of doing something else.
Thanks for your kind words. PIAWYC (Pass It Along When You Can)
Walt is correct, the built-in states are very good at what they do. Use the built-in states if you want the same function. Create a custom state for flexibility that a built-in state can't.
6 Replies
Creating a Hover state for an object gives it superpowers, one of which is to automatically change to the Hover state when the cursor hovers over it. When you create another trigger that duplicates that action, it frequently conflicts with the built-actions. The results of those conflicts are unpredictable, sometimes spectacular, but almost always undesireable. In this case, they cause the error message you are seeing. Delete all those "hover" triggers, and see if it works.
An additional fact is that all the states on the drop-down name menu for new states behave the same way - they can handle their native function, and resent any interference. :)
Hi Kate,
I'll suggest not to create a custom state when there is a built-in state, it might cause glitches. With build-in states, you don't need to set triggers and that can save you time.
Take a look at the modified file attached to see details about what I mean.
Walt, thank you. I really liked the part about spectacular conflicts! Amazed by your writing skill. Thanks for your help again.
Thanks, Joanne. I actually heard that built-in states are pretty glitchy and most people just create custom states to avoid glitches
Actually, the built-in states are very good at what they do, but they are limited only to that. The best reason to create custom states is to have the flexibility of doing something else.
Thanks for your kind words. PIAWYC (Pass It Along When You Can)
Walt is correct, the built-in states are very good at what they do. Use the built-in states if you want the same function. Create a custom state for flexibility that a built-in state can't.