Which version do you use, please? And I suppose rollover caption is not an option, because it is a lot easier.

Can be done:

• create the popup (is what?), add the close button in the wanted place and hide everything in the Properties panel
• for the close button you create a first standard advanced action that does close all what is in the popup (if there is only one object, could be done by a simple action, but then the playhead will move on)  AND the close button as well
• create the button on the slide and make it trigger another advanced standard action that shows the popup objects and the close button

Have a look at this video where I explain the difference between a simple and a standard action:

http://www.youtube.com/watch?v=M3nKi-DB6Fw&feature=plcp

Lilybiri

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.

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?