Problems with the buttons in Storyline 360

Hi Sarah, and welcome to the E-Learning Heroes Community! Glad you're here! 🎉

Thanks for including your .story file! I am able to replicate this behavior on my end. It looks like the conditional trigger you have included is not allowing the built-in states to behave properly.

When using built-in states, a clicked button in your course will no longer be considered Normal. Since you had the condition linked to just the Normal state, that is why the trigger was not behaving as intended when previewing. Here's an article that can help you better understand this.

I went ahead and created a sample for you. By removing the conditional formatting on the trigger, it is able to behave as expected when previewing the slide. To have a better look at the button functionality, I changed the colors of each state so you have a clearer look at the states in action. Attached you'll find my file. Feel free to test this out on your end.

Could you please share more details of what you’re trying to achieve? It would be helpful in order to recommend a more personalized solution for you.

Hope this helps! Have a wonderful start to your 2024! 

Hello Luciana, thanks for your answer. I think I have to be more  specific to make you understand what my problem is. I am pretty sure that the buttons in Storyline behave differently than they used to a few months ago. And now I am wondering if the previous behavior will come back because I think it was more useful. I will show you what I mean with some projects. The first project "Prozesskriterien Drag and Drop (6ans)" is built like the one in my previous post. It doesn't work anymore after opening it and testing it in Storyline but it did a few months ago.

https://360.articulate.com/review/content/c2af9930-8c9a-47d3-8a4a-3ba6cc215c7c/review

This is the link to the review360 project where it does work (I didn't change anything in the project).

Because of these changes I have to use a variable. It's not a much worse way to create the drag and drop exercises but I think it was more intuitive before, easier to use and also easier to make others understand them. A file where you can see the solution with the variable is the "Drag and Drop A2.1.6 (17ans)" file.

I hope you now know what I mean and that you could tell me whether it will stay this way or not and maybe why these changes were made.

Greetings
Sarah

The file "Drag and Drop A2.1.6 (17ans)" actually had an error so it wasn't able to be correct but now I fixed it and if you drop the answers in the right boxes the interaction will be set to correct.

Hi Luciana, I just found another solution. You could also make your own "Normal_2" (or something like that) State by creating one and it works just fine again. So that's why I'm wondering why the actual "Normal" state behaves differently now than self made ones.

Hi Eric, 

I get that but I still don't understand why states that are created do work with a trigger that uses the condition If state of Button is "created_state". 

Hey, 

Today I got an update for Storyline 360 and now the buttons work just fine again. I am really happy that the previous behavior is back!

I also tried the Test_Datei_bug in my first post and this one also works again...

Thanks Team!

Hi Sarah, 

Wonderful news! Glad to hear everything is running as expected on your end after the most recent Storyline 360 update. 

If any other questions come up in the future, feel free to reach out. 

Have a great weekend!