Lectora 17 Navigation Issue

Hi Richard,

We are glad we are not the only ones experiencing this problem! Thanks for your suggestion, we will look into this further and will have a go at removing any transitions.

Hopefully we will find a resolution to this problem soon.

Thanks,

Sophia

Hello Sophia,

I have recently experienced this exact same problem. After discussing with the Lectora support team we determined that transitions were causing the problems. Specifically, if a navigation button is clicked during any other object transitioning all the navigation on the page locks up. The only solution we've found is to remove transitions.

I can understand why a button may not function during a transition, but why should that lock up all other navigation on the page even after the transition is finished.

Hope that helps!

Richard

Hi,

We set up a test to compare a page of fade transitions and a page with no transitions.

The first page was set up to have 15/20 copies of the same image fading in and out automatically. After 15 seconds it automatically redirects you to the next page which was exactly the same in every way except there were no transitions on the images and it redirects you to the previous page; creating a loop.

Our results show that 9 times out of 10 it would stop redirecting on the transition page after 3 or 4 redirects. This also indicates it cuts automatic navigation - not just on click actions.

It never cut out on the other page without transitions further indicating it's something to do with the transitions and not other factors like the amount of images/actions etc. It also sent through logs to our LMS, even after cutting out meaning it does seem to be a Lectora issue and not an issue with SCORM or connection to the system.

All-in-all I think the only way around this is as you said - to remove all transitions.

Thanks a lot for helping us out! :)

Sophia

Hi Sophia,

Thanks for further testing on that. Removing transitions will be a bit of a showstopper for me. A course with no transitions makes for a clunky and un-engaging experience. Hopefully there will be some resolution to this problem.

Richard

undefined

Hi Richard,

We've spent some time looking into an efficient way to remove all transitions, both in and out; we discovered quickly that going through and locating each transition on an object is slow and fairly tedious.

We opened up the .awt file in Dreamweaver and located every "undefined

Sophia

Sophia,

Thanks for passing that info along. That's great to know, but still very cumbersome for my resources and workflow. I have screens with many objects fading, wiping, flying in, etc. I can't see building and testing these motions outside of the authoring environment.

Glad to hear you came up with a solution that fits your needs. You must have some strong coding skills :)

Richard

undefined

@jasondal Do check the Forum of Greensock. Quite a lot inthere. Another good way to get up to speed with GSAP is checking out Codepens.. you can edit and tweak them to your liking. And if you made something you wanna add to Lectora..you can export the pen as a zip...and step for step add the things inthere to your Lectora.

Thinking about this, my first instinct is to wonder if there's an issue with JavaScript. Whenever I run into a glitch in a page, I check out the Inspector Console in Firefox Developer Edition (regular FF, Chrome or IE can be helpful). There may not be much that you could depending on the error, if there is one. But at least it could give a direction on a workaround or info for support to work from.

@mnotermans5114 - I've looked at the GSAP site and struggling with how exactly to run and learn the methods. Any tips on ways to do that?

Thanks @mnotermans5114

@jasonadal - Have a look at the following to see basics of JS and Greensock: https://greensock.com/jump-start-js

For Lectora this can be added in using 'Run Javascript' action on a page or inserting HTML extension using additional files or added using 'Header Scripting' type.

Fading: TweenMax.to("#MyElement", 2, {autoAlpha:0,ease:Elastic.easeOut});

Wiping: TweenMax.fromTo("#MyElement", 2, {x:-1009},{x:0,delay:0.75, ease:easeArray[10]});

Flying: TweenMax.to("#MyElement", 2, {scaleX:5.5, x:-66,y:-78, rotationX: 215, rotationY: -115, rotationZ: 122, ease:Elastic.easeOut});

With GSAP Tweenmax (esp. the latest version) you can make any animation you can imagine.