We do have this issue reported in the current update, and our team is taking a look at possible fixes! Do you have a .story file you could share with me so that I could include it in the report with our team? The more examples the better. 🙂Â
Also, I see that two workarounds were noted of either using the cue points as the way to trigger or a trigger of when timeline of <audio1> ends.Â
Let me know if that helps and if you can share that example I'll attach it to the report. Once we do have any additional information to share I'll be certain to post here!Â
4 Replies
Anyone else seeing this behavior in the current update?
Hi Jason,
We do have this issue reported in the current update, and our team is taking a look at possible fixes! Do you have a .story file you could share with me so that I could include it in the report with our team? The more examples the better. 🙂Â
Also, I see that two workarounds were noted of either using the cue points as the way to trigger or a trigger of when timeline of <audio1> ends.Â
Let me know if that helps and if you can share that example I'll attach it to the report. Once we do have any additional information to share I'll be certain to post here!Â
Thanks for the update! Great to hear!
re: workarounds
I am aware of those workarounds. But I don't want to change the whole design paradigm for something that should be fixed soon.Â
re: exampleÂ
I'll send support example later today.
Thanks again!
Â
Thanks Jason - and I certainly understand not wanting to change the whole design! Â
This discussion is closed. You can start a new discussion or contact Articulate Support.