Captivate project fails when multiple buttons that “show for rest of project” are added.
I am running into a new issue in Captivate 2017 64-bit on Win10, and I am beginning to think that it’s not something foolish that I am overlooking. The project is HTML5.
I am working on a final project for an ID class and am working on trying out new and more advanced approaches. I’ve programmed in an exit button which exists on the second slide and remains for the rest of the project, but which only appears once conditions have met. This works brilliantly. Now that I’ve proofed several other interactions and features, I wanted to go back and make buttons for the sections listed on a sidebar, but have those appear throughout the whole project as well and change states based on the section. This would be a tremendous time saver versus programming in a custom state for each on each slide.
When I add multiple buttons with custom states to the slides and check off to show them for the rest of the project, the project stops previewing properly (either failing to show the buttons or failing to show any interface at all other than the skin frame) and published content also fails. I’ve gotten to a point in troubleshooting where I’m blaming the software, not myself. It will work just fine with three buttons, but then if I add a fourth with the same properties, it breaks again. Delete any of the four, it works again.
Help? I’m going to clear my cache now and will report back, but I wanted to put this out there.
Please and thank you,
-Dana
Can you check the exact version number? It should be 10.0.1.285.
There was a problem with having more than 3 shape buttons on master slides, I’m wondering if you are not bumping onto a similar issue. I often use objects timed for the rest of the project, but only in non-responsive projects (you cannot use them in Fluid Boxes). Hence my next question: are you talking about non-responsive or responsive projects?
It is non-responsive.
I will check the version when I am back on my home computer. My coworker has a license here at work and we tried to re-create the issue without running into the same problem. I will see if my version is up to date and, if so, I am assuming that a re-install is in order.
Thank you, Lieve. My install was not updated. After updating, it appears to have fixed the problem. I would complain about all of the time I lost troubleshooting, but it ended up forcing me to devise a workaround with identical functionality, so progress none the less.
Spoke too soon. ‘Preview’ is working, but published project is still failing. Also, I’m noticing that drag and drop interactions I built work fine when previewed from the slide (ie- without ‘show for rest of project’ elements), but not at all when viewed as a complete project.
Problem resolved. Drag and drop failure was discovered to be a transparent object overlapping with elements. Publishing failure was discovered to be a hidden “show for rest of project” exit button triggered to show once variables are fulfilled. Deleted it and created an identical button and no apparent issues. Unless I missed something, I’m going to chalk this up to a glitch related to the object.
Which preview method?
Preview Project was working for basic functionality save for the Drag and Drop unless I previewed from those slides (ie- skip the slides which introduced a transparent overlay which would have mucked it up). Previewing in browser or publishing were dying on the slide which that button was introduced. I went back and tested and even cutting and pasting the offending object right back where it was fixed the problem, so I’m guessing that Captivate had references to or from the object that were faulty.
Do you really still want to publish to SWF? All Preview methods with one exception do use a temporary SWF file which is a pity. The only real HTML preview method is F11, Preview HTML in Browser. If it is not working, that is an indication that something is going awry, but not totally sure. Sometimes I had projects which lost some functionality with F11 but worked perfectly once uploaded to a webserver after publishing. Did you ever try that?
You must be logged in to post a comment.
