Skip to main content
L
LaurieGoslee
Known Participant
April 15, 2015
Answered

Reuse custom menu across projects

  • April 15, 2015
  • 1 reply
  • 420 views


I am working in Captivate 8 and have a custom menu that I would like to reuse in multiple projects.  The menu is made from smartshapes and is placed only on the first slide, then set to display for rest of project.  It contains advanced actions.

The issue is that the other projects will start from imported PowerPoints, so the menu will need to be copied onto the "PowerPoint" slide within the Captivate course (since the PowerPoints don't import just as a background).  Of course, when I do this, I have to rename all the objects, update my advanced actions etc.  Is there a way I can copy the custom menu from one slide/project to another without renaming each object etc. each time?  I understand I can probably replicate the action of the button using shared actions, but don't know how I may be able to reuse the whole menu without renaming all the objects.

Here is a visual of my menu:

This topic has been closed for replies.
Correct answer Lilybiri

Alternative are shared actions. Those objects will be parameters, you could even indicate the generic name instead of your custom names. I think most users underestimate the power brought to Captivate by shared actions. And try to use groups as much as possible in the action; a parameter can be anything.

1 reply

Lilybiri
Lilybiri
Legend
April 15, 2015

You are talking about which 'objects'?

Why not start with that menu slide and insert Powerpoint slides after it?

L
LaurieGosleeAuthor
Known Participant
April 15, 2015

I am referring to the group of smart shapes that makes up the custom menu.

Yes, though about that, but didn't think I could hide the first slide and still show the menu for the rest of project.  I suppose if there's no other solution I could replace the PowerPoint's title slide with a Captivate title slide.

Lilybiri
LilybiriCorrect answer
Legend
April 15, 2015

Alternative are shared actions. Those objects will be parameters, you could even indicate the generic name instead of your custom names. I think most users underestimate the power brought to Captivate by shared actions. And try to use groups as much as possible in the action; a parameter can be anything.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices