I would like to do the following:
1. Put a button on a slide. When clicked, it displays a popup.
2. The popup has a Close button. When clicked, it closes the popup. The popup does not close unless the Close button is clicked.
Is this possible?
Which version do you use, please? And I suppose rollover caption is not an option, because it is a lot easier.
Can be done:
Have a look at this video where I explain the difference between a simple and a standard action:
I am using Captivate 4.
I want to be able to give the user a navigation feature that lets them jump to any slide. I am not great in Captivate, but I know how to make one button that goes to a slide, but in this case, I want to have about 10 buttons that go to slides. And...I want a "Nav" button that opens the 10 button set.
So...I want to somehow "group" those ten buttons into an object that I can show or hide.
Your question "create the popup (is what?)" gets at the the heart of my problem. I know how to create rollovers, but my customer does not want a rollover...he wants the visibility of the object to be controled by a click...not a rollover motion. So, if I can't use the rollover slidelet object...what object can I use to hold ten buttons?
I tried to insert the GoToSlide.swf widget only to get an error message saying that I needed to install FlashPlayer 8. Well...I have FlashPlayer 11 so I would think that if 8 would work...then why not 11?
I am frustrated.
My slides already have a widget that I downlaoded from the internet. This Widget pauses the slide. This is good since my presentation does not actually "play". Rather...the user clicks thru it at her own pace. So I amespecially frustrated that I already have an operating widget, but cannot insert a standard widget for the GoToSlide.
I appreciate any insights you have on this,
I found one answer to my complicated problem.
Adobe has addressed the conflict between Captivate 4 and Flash Player 11. The fix is basically a totally new Captivate EXE file. You download it and replace your existing EXE. Then the problem of not being able to insert widgets disappears.
So...now I have the GoToSlide widget working in my presentation.
My next question is How do i edit the widget so that it says something other than "Select Slide" as the default choice in the drop down?
I would recommend you change your navigation strategy to something that will be easier to maintain, lower file size, and not bloat your project with lots of interactive objects.
Basically what you're trying to do right now would require you to add (and hide) 10 or more buttons on every slide just to get this popup navigation window to appear. The sheer number of objects, variables and advanced actions required to do this makes it unwise.
You're thinking of Captivate content as if it was just like normal web pages where a reusable popup window (e.g. in an iframe) might provide a solution. But CP content doesn't work the same way.
My suggestion is that you just have ONE button on each slide that will jump users to a special navigationslide (you can make it look like a popup) that contains your 10 buttons. You can have a button on that slide that will take the user back to their last visited slide in case they want to return to the same point in the project. However, having all navigation done on ONE slide will be significantly easier to maintain and won't cause you anywhere near as much grief.
Nothing wrong with using the Go to Slide widget per se, except that you'd probably need to have one on every slide (so a lot of widgets), and it will be a real pain in the proverbial to maintain if you happen to change the number of slides in your project at any time.
The Go to Slide widget creates what looks like a drop down menu to jump to other slides in your publshed project. However, though the widget shows you the name of the slide when you are selecting which one to go to, it uses the slide number as the reference at runtime. This means that if you add in or remove slides that happen to change which slide number of target slide locations, then you immediately render all of the Go to Slide widgets out of date. To ensure they all continue to point to the correct slides, you'd need to open every instance of the widget and change the slide numbers. If you have a project with dozens or scores of slides, this is going to be very tedious.
That's why I suggested that the better solution might simply be to have ONE slide used as a navigation menu and jump to that instead so that the user can choose the next destination. It's still the same number of clicks for the user to navigate. But a lot easier for the developer to maintain.
When using the GotoSlide widget, I will always time it to display for the rest of the project. So there is only one widget to 'maintain', right? Is there a lot of difference with a navigation slide in that case?
OK. I see what you mean. Yes using Display for rest of Project would also work and mean you just had one object. But it also might mean that it would get in the road on certain types of slides (e.g. question slides or simulations).
Since this is a Static widget, you could also just add it to the relevant Master Slides and set it to be on top of all other objects?
Hi Lieve, Hi Rod,
Thank you so much for your thoughtful and helpful replies.
I am probably going to use the gotoslide widget and have it display for the rest of the project. I do not have a large number of slides...about 14 and I also do not expect much turbulence once this is done and published.
I considered the use of one navigation slide and I may still try to convince my customer to accept that approach, but I think they really like the gotoslide widget.
I also looked into "upgrading" to Captivate 6 and I was interested to learn that there is no upgrade path to 6.
6 is an entirely new ballgame because of HTML 5. So the product known as Captivate is actually discontinuous from 5.5 to 6.
As a result, I am looking to move away from flash based tools and towards stuff that uses HTML 5 etc. I'm liking Adobe Edge...
Lieve, thank you also for the tip regarding the FLA. I have a guy here who uses flash and I asked him to do the edits on that widget...worked great.
I think you may be premature thinking that Captivate will no longer fill your need.
Who told you that you'd need to move away from Captivate if you wanted to work with HTML5?
One of the biggest features of Cp6 is its HTML5 output option.
Thanks. I did not know that.
I mostly work on instructional pieces for an internal audience. So...technically I am not really a "web developer". We tend (here) to dabble in a variety of tools to produce instructional materials so that we don't have to conduct as many classes or web casts.
So...I use (or have used) Lectora, Adobe Presenter, Word docs deployed as PDFs, Captivate, Jing, Snag It, RoboHelp. Pretty basic stuff. I am actualy looking to review our tool set this fall and maybe buy and train on something that does everything we need and that is fairly simple.
Here's the problem:
Anything that does everything you need, won't be simple.
A tool that is simple, won't do everything you need.
Captivate will do everything you need, but it's not simple.
Articulate Storyline is simpler, but it won't do everything as well as Captivate.
So if your needs are only ever going to be simple, and you don't feel like learning, maybe Captivate is not the right tool for you.
If on the other hand you want to get a tool (or in the case of ELS a toolset) that has all the headroom you'll ever need, then I recommend Captivate.
Europe, Middle East and Africa