Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Preview doesn't work when project contains buttons that link to other projects (repsonsive project, Win 8.1, 64bit, V. 9.0.0.230)

Community Beginner ,
Nov 03, 2015 Nov 03, 2015

Hi there,

I'm trying to create a course-start-page in a responsive project, where users can navigate between lessons (i.e. other captivate projects) etc., but I encountered a couple of issues:   

First of all, all preview options (except preview in Adobe Edge Inspect) don't seem to work anymore as soon as I add buttons that link to other captivate projects - when selecting one of the preview-options, the usual progress-dialog appears informing me that the slides are being created etc. and eventually a browser tab is opened to show the preview - but except showing the usual loading animation / spinning wheel nothing further happens, not even the project navigation is shown....

To ensure that it's not a project-specific issue, I checked this with multiple responsive projects & different buttons - all preview options work as expected as long as no button is added, that references another project - from that moment on preview goes south ... - if I remove those buttons (or change their on-click-action into something else), all preview-options work again - so it's definitely not a project-specific issue... 

The only preview option still working after adding those buttons is "preview in Adobe Edge Inspect", which brings me to the next issue: In this case the preview opens as expected in the browser, but the buttons don't reference the projects correctly (which they do when I publish the project as HTML5 for devices) - instead of pointing to the appropriate sub-folder in the "main"-project's "callees"-folder (where referenced projects should be copied when I understood this correctly), they point to the location where the referenced "sub"-projects are original stored... It seems Captivate expects there to find the referenced project's published files - but since I store my captivate projects in another location than their published output, the reference points into the void  ...      

Any thoughts on what might be causing this issues (or if there's a better way to link responsive projects)? 

142
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
no replies

Have something to add?

Join the conversation
Resources
Help resources