You know that I often appreciate more the hidden gems, which help any developer to save time and frustration.
Those are not the big hype features that were emphasized everywhere. There has been a lot of evolution in Captivate since versions, slowly but steadily. Same confusion can be found in many training schedules and books. When trying to help Captivate users, I often bump onto confusion between themes and templates. ToHelp triggered by the shape button on the master slide 'Content' You do not have to define a default value for that user variable. This variable will be used to store the value of cpInfoCurrentSlide when the user leaves the content slide to go to the Help slides. One user variable has to be created: v_last. That means that slide 1 has to be indicated as 0, slide 2 as 1. Beware: for this variable the index starts with 0. cpCmndGotoSlide: will be used to navigate the user back to the content slide.The index starts with 1, which means that for slide 1 this variable is 1. cpInfoCurrentSlide: gives the slide number of the current slide.Two system variables are used in this example: I didn't opt to time that button for the rest of the project, because there are only two Help slides and having to hide/show them would have been more work than using two instances. It has another instance of that special button '' SB_Back2'. Slide 6 (Help slide 2): has no need for a Next button, but needs a pausing Back button (to navigate back to the first Help slide) with the action ' Go to Previous Slide'.Why? That button will already been hidden if the user comes from the last content slide, but not when he is getting here from one of the previous content slides. The On Enter action for this slide is used to hide the button 'SB_Next' (from slide 2), same way as on the last content slide. This shape button has a bubble added in the Rollover state, which functions as Tooltip.
This button triggers a standard action ' BackToSlide'. This slide has a special shape button ' SB_Back1' to allow going back to the content slide. Slide 5 (Help slide 1): has another instance of the Help button (SB_Next_Help) with the action ' Go to Next Slide'.Master slide 'Help': this slide has no interactive object, is used by the Help slides.Slide 4 (last content slide): the Next button has to disappear, which is done with an On Enter action ' Hide SB_Next'.For this small example, it can look easier to have a Next button on each slide where it is needed, but if you have a lot of content slides, this approach will save on time and file size. This Next button has been labeled ' SB_Next'. You cannot show/hide an object on the master slide, because it has no ID, no name. A shape button on the master slide is excluded because this Next button has to be hidden on the last content slide. This shape button is timed for the rest of the project, so that it will show up in all following content slides. Slide 2 (Content1): has a shape button for Next which pauses the slide at 2.5secs.This master slide is used for the content slides. Master slide 'Content' has the Help button (with the question mark): it is a shape button (no states at this moment in CP9) which triggers a standard advanced action ' ToHelp'.Slide 1 (Title) which uses the master slide 'Title', has a click box covering up the slide.
#Adobe edge inspect cc app adobe captivate 9 download#
Download HelpNavigation.swf Interactive objects/events
0 kommentar(er)
