Skip to main content
Participant
April 27, 2017
Answered

Linking to external pdf and project files when publishing as a Mac executable

  • April 27, 2017
  • 1 reply
  • 288 views

Hi,

My team have created an eLearning module that is published as a Windows Executable and Mac-Executable which is designed to be watched via USB on PC and Apple desktop/laptop computers. The project consists of a Main Menu and five small modules linked to the main menu via (Open Another Project) action.

The first problem we are currently facing is that when the published project is loaded on a Mac using the Projector App the links from the Main Menu to the other modules do not work. We are using a Windows PC to publish the module, if that matters.

Will publishing a project on a Mac allow the links to work?

Is the Open Another Project action compatible with Macs, if not please advise an alternative way to link to a Mac App from the main menu.

Another problem is when using a button to view a PDF (Open Another Project) from a slide this function is not working on Mac also.

Please advise what action is recommended to view a local PDF by clicking a button.

Regards, Dave

This topic has been closed for replies.
Correct answer RodWard

For starters:  You should forget about using the Open Another Project action.  It's a legacy from Captivate versions a decade or more ago and should be ignored completely. (I do not even understand why it hasn't been removed from the application.)

The Open Another Project action is actually designed to find an HTM file living in the same folder where the CPTX project file or the other target project is located.  Publishing any Captivate output to the same folder as its CPTX is NOT something that is ever recommended nowadays and is definitely not going to yield a correct file path for your published projects loaded on someone else's system.

If you wanted to call published output via an Action, you would usually choose the Open URL or File action and target the HTM or HTML file that launches that content.

Now for the next problem:  Trying to use one EXE file to open another EXE file will usually trigger Flash Global Security and block the links from working.

1 reply

RodWard
Community Expert
RodWardCommunity ExpertCorrect answer
Community Expert
April 27, 2017

For starters:  You should forget about using the Open Another Project action.  It's a legacy from Captivate versions a decade or more ago and should be ignored completely. (I do not even understand why it hasn't been removed from the application.)

The Open Another Project action is actually designed to find an HTM file living in the same folder where the CPTX project file or the other target project is located.  Publishing any Captivate output to the same folder as its CPTX is NOT something that is ever recommended nowadays and is definitely not going to yield a correct file path for your published projects loaded on someone else's system.

If you wanted to call published output via an Action, you would usually choose the Open URL or File action and target the HTM or HTML file that launches that content.

Now for the next problem:  Trying to use one EXE file to open another EXE file will usually trigger Flash Global Security and block the links from working.