Prime Fluidic Player

Report · Aug 28, 2018

I have two comments regarding the fluidic player. I am curious to know how many have experienced these.

Exiting the player can be a challenge. I recently received a phone call from one of the participants in a course who asked me how to close out of the content and go back to the course screen. I responded by stating that there should be an 'X' in the upper right corner to close the player. They said there is no 'X' there. Fortunately, this was an internal participant - so I went to their desk and had them show me and sure enough, there was no 'X' in the corner. We tried a different browser, same issue. To make the long story short, it turns out that when you have the table of contents open, the 'X' slides off the screen. So you must first close the table of contents then close the window. This is not a showstopper now that I am aware - I can tell folks what to do.

I submit that the 'X' should properly float in the corner all the time.
I have an issue where my content plays functions as expected when previewing but not after uploading to Prime. I have had two issues of the same nature. Both situations involved a button with complex actions using Javascript. The common link between the issues was using one of the two commands.

window.parent.cpAPIInterface.gotoSlide(16); or window.cpCmndGotoSlide=16;
Again, they worked fine in preview through Captivate and when published as HTML5 to a local server but the buttons failed when uploaded to prime. My solution was to separate the navigation from all of the other action behind the button which meant several hours of re-work.

Anyone else have thoughts on these items?

Report · Aug 28, 2018

Hello Greg,

Thanks for raising your observations and detailed explanation.

We will look into the first issue and work on improving this experience for the learners.

I could not reproduce your second issue about javascript not working within Prime. Is it possible for you to share any of your sample content (preferably .cptx project) so that we can try it out and investigate further.

Regards

Mukul

Captivate Prime Team.

Report · Aug 28, 2018

Thank you.

Is there an email address I can use to send the file?

I am not seeing a way to attach it here.

Report · Aug 28, 2018

Hello,

I have sent you a private message with my contact details.

Regards

Mukul

Report · Sep 02, 2018

Hello Greg,

As discussed on email, content not playing in Captivate Prime (refer to Issue-2) is not a Prime issue and the content infact did not play well in other system as well. Also you confirmed that the suggested javascript fix worked for you.

Incase this resolves your issue complete, please go ahead and mark this thread "Answered" so that this issue gets closed.

Other feedback around "X" button in Fluidic Player is noted and we will discuss it internally to see how we can improve that experience.

Thanks,

Mukul

Product Manager | Captivate Prime.

Report · Sep 03, 2018

I don’t think I can mark a discussion thread as answered.

It was not originally posted as a question so I don’t see the option.

However, I can offer a brief summary of this for others who may encounter the same.

In review, I have been using a line of Javascript in order to jump to a specified slide. The line I had been using looks like this...

window.parent.cpAPIInterface.gotoSlide(0);

The slides are zero indexed which means the line above would actually take you to slide 1.

I had never had any issues using it until recently. This had been tested as a published file to a server by multiple individuals. Even in Captivate preview, it worked fine.

So not surprisingly, I was confused to hear from a student that something which had been tested many times over by many different people suddenly stopped working. I verified that it did not work in Prime

The correction is to remove 'parent' from the code which allows things to continue working as originally expected. So this is not a Prime issue.

However, I wonder if something changed elsewhere - perhaps a browser update - that introduced this issue. I won't beat my head over it though since I have a solution.

The corrected code looks like this...

window.cpAPIInterface.gotoSlide(0);

I implemented the changes across my files and made updates and verified functionality. As such, this issue has been resolved.

My appreciation to Mukul and the Adobe Team for their responsiveness.