I have some objects on a slide. Each object has a visited state. When I click on any of the objects the first one does not change state to visited, regardless of which one I start with. But the second and the rest changes to visited when I continue to click on them. Why does not the first object change state?
See enclosed story file. Click on the colored objects.
What you're experiencing is "unexpected behavior." Any object with a Visited state should automatically change to Visited when clicked (well, unless there's also a Selected state).
There should be no need for a trigger to change the state to Visited when the object is clicked.
And yet... As you said, the first petal clicked doesn't change to Visited automatically.
I tested your file by turning off the triggers that show the layers. With those triggers, all the Petals worked as they were supposed to: even the first one clicked switched to its Visited state. But when I turned those triggers back on, the same problem occurred -- even when I added a trigger to change the state to Visited.
I suggest you submit this case directly to the Articulate staff, so they can determine what's going wrong. You can do that here:
Although we should not need to use any trigger for changing an object to visited state, so I agree with Judy below. I will submit a support ticket on this.
I see you worked with Renato, who logged this behavior as a possible software bug where the change of state trigger in shape doesn't work if the state has a textbox with animation and the slide layer shown pauses the base layer's timeline.
We are investigating the issue, and we will let you know once we have new information to share, as this discussion is connected to the report.
I'm sorry you've also hit this snag! We're still looking for a fix, but since you are now subscribed to this discussion, we'll notify you once it is available. Here's a peek into our process:
I was able to fix the issue - for my current project at least: the bug appeared when creating a new slide based on a template slide we have. The template slide functions perfectly, but after adjusting it, the issue appeared. The fix was to use the original slide and adjust that, which solved the issue for my current project.
I still submitted a case (number 04039349), as I don't understand why updating the template slide results in an issue, while updating the original slide does not result in the bug, even though the same steps were used to adjust them.
I added a sample project with the template and original slide, what I changed, and what the outcome is. Perhaps it even gives a clue to fix this bug (fingers crossed :-)).
You're welcome, Mirjam! Thank you for opening a support case with your Storyline file. You're right; this might help provide clues to solving the bug. I added your observations to the bug report so our product engineers will be aware; I appreciate you sharing them.
In the meantime, I encourage you to continue working with Chester in your support case. You're in good hands!
So sorry to hear you've also run into this setback!
Our development team is still closely tracking this issue and looking for a fix. We'll be sure to update this thread as soon as one is available.
If you're comfortable sharing your .story file, we'd be happy to test the behavior and confirm if you are being affected by the same issue. Feel free to upload a copy here in the discussion or privately through a support case.
10 Replies
This post was removed by the author
Hi, Maria,
What you're experiencing is "unexpected behavior." Any object with a Visited state should automatically change to Visited when clicked (well, unless there's also a Selected state).
And yet... As you said, the first petal clicked doesn't change to Visited automatically.
I tested your file by turning off the triggers that show the layers. With those triggers, all the Petals worked as they were supposed to: even the first one clicked switched to its Visited state. But when I turned those triggers back on, the same problem occurred -- even when I added a trigger to change the state to Visited.
I suggest you submit this case directly to the Articulate staff, so they can determine what's going wrong. You can do that here:
https://articulate.com/support/contact/case
Good luck!
Hi Abigail and thank you!
I appreciate your effort.
Although we should not need to use any trigger for changing an object to visited state, so I agree with Judy below. I will submit a support ticket on this.
Thank you Judy, I will do that.
Hi, Maria.
Thank you for opening a support case!
I see you worked with Renato, who logged this behavior as a possible software bug where the change of state trigger in shape doesn't work if the state has a textbox with animation and the slide layer shown pauses the base layer's timeline.
We are investigating the issue, and we will let you know once we have new information to share, as this discussion is connected to the report.
Hi Maria,
I'm experiencing the same issue. Is there any new information to share?
Thanks,
Mirjam
Hi Mirjam!
I'm sorry you've also hit this snag! We're still looking for a fix, but since you are now subscribed to this discussion, we'll notify you once it is available. Here's a peek into our process:
In the meantime, we're happy to troubleshoot your file for any tailored options. Please use this private upload link to share the Storyline file.
Hi Eric,
Thank you for your quick response!
I was able to fix the issue - for my current project at least: the bug appeared when creating a new slide based on a template slide we have. The template slide functions perfectly, but after adjusting it, the issue appeared. The fix was to use the original slide and adjust that, which solved the issue for my current project.
I still submitted a case (number 04039349), as I don't understand why updating the template slide results in an issue, while updating the original slide does not result in the bug, even though the same steps were used to adjust them.
I added a sample project with the template and original slide, what I changed, and what the outcome is. Perhaps it even gives a clue to fix this bug (fingers crossed :-)).
Thanks!
Mirjam
You're welcome, Mirjam! Thank you for opening a support case with your Storyline file. You're right; this might help provide clues to solving the bug. I added your observations to the bug report so our product engineers will be aware; I appreciate you sharing them.
In the meantime, I encourage you to continue working with Chester in your support case. You're in good hands!
Has this bug been resolved. I'm having the same issue.
Hi Sandy!
So sorry to hear you've also run into this setback!
Our development team is still closely tracking this issue and looking for a fix. We'll be sure to update this thread as soon as one is available.
If you're comfortable sharing your .story file, we'd be happy to test the behavior and confirm if you are being affected by the same issue. Feel free to upload a copy here in the discussion or privately through a support case.