Image obj not as responsive as Shape obj?
Apr 19, 2018
Hi,
The latest storyline update (Build 3.15.15453.0) has me scratching my head over the inconsistency in interactivity.
In my project, I have a set of Shape object and Image object- both objects have the same exact triggers, and yet respond differently in the newest Storyline update.
The interaction used involves:
1. First, dragging and dropping both objects onto a box (drop target) and stays there.
2. Then, dragging and dropping them outside the box.
3. Lastly, repeating the first step: dragging and dropping them onto the box and stays there.
Error:
Both objects react normally up till step 3, whereby the Shape object will act as the triggers attach- dragged and dropped onto the box and stays there. However, the Image object is unable to stay on the box despite having the same triggers as the Shape object. This error will also happen when the Shape object has an image fill.
Pretty sure it's a new bug that came with the latest update, as this interaction worked perfectly for both object types in the previous builds. To be sure that image itself isn't causing the error, I've added images into the Shape object's states.
Here's published a sample here and also attached the .story file below. Hopefully, this error with object types can be resolved soon as my entire project has its foundation built on this interaction.
Thanks in advance!
8 Replies
Hi again Jia! 😊
I'm definitely seeing the behavior you've described in the sample link you provided, but I'm not seeing the problem in my own testing.
Can you test this link and let me know if you run into the same error there? Thanks!
Hello again Alyssa!
I don't see the behavior on your testing either and I'm pretty sure my Storyline is up to date.
Is there anything that would cause two of the same software to have different products? I've encountered a couple of times where publishing on Storyline Review had a more accurate result than compared to LMS publishing.
Hi Jia,
You mentioned Update 15, and that's the latest update for Storyline 360. You may also want to check what browser(s) and versions you're testing on?
You initially shared a Review link, does that match what you were seeing in your LMS? It looks like Alyssa tested your course and published for the web?
I have the same problem. It´s because of that version. Ashley / Alissa, what kind of version are you using?
Hi Ashley,
I've tested them on Internet Explorer and Safari, and Google Chrome; all of which gave the same results of the Image object being less reactive.
The Review I shared matches with my LMS publishing, so I was wondering how Alyssa managed to get it to work. For my project, I'm required to publish in LMS so I don't think web publishing is an option for me.
Is there any way to fix this?
Hi Ines,
Glad that I'm not alone on this issue. It's been adding so much extra workload to replace all image objects with shape objects. :'(
Hi Jia,
Since you mentioned you published for LMS, I wanted to try the same thing. I published your file for LMS with SCORM 1.2 and hosted it on SCORM Cloud. When I tested the output, I saw the same error you saw.
Here's a link to the output if you'd also like to test it.
I'm going to share this with our Support Engineers to get some further insight on why this is happening. They'll test your file and reach out to you via email soon!
Hi Alyssa,
The output you've sent also gives the same error when I tested it!
Thank you! I look forward to receiving their email and rectifying this issue. :D
This discussion is closed. You can start a new discussion or contact Articulate Support.