Hidden Style associations.
I am trying to develop a template and I want to set up my click box interaction with default styles on the success/failure/hints. I HAVE the styles set up in Object Style Manager – I can’t figure out how to automatically associate the style with the failure_shape type and hint_shape type. Somehow as I edited styles, the success style got applied to all 3 shape-types.
Is there a way to do this without starting over on an entirely clean template?
I’ve tried in both 2017 and 2019 (many of my colleagues are still using 2017, so it has to be accessible in 2017).
If you want to learn more about styles and the Object Style Manager, part of the Theme, you can find all links to the many articles I wrote about them in this post:
Here is the link:
http://blog.lilybiri.com/feedback-shapes-in-captivate-2017
BTW forgot to tell; do NEVER use a cptl file as template, it has too many bugs since a couple of versions.
So, don’t use the template file type for templates? How do you recommend preventing unwanted changes across a team? Password protect the “parent” .cptx?
For consistent design a custom theme is what you need. It includes object styles, master slides (which can include interactive objects and actions), skin etc. You can use placeholders and lock their position and size. You can also completely lock items if you really need a parent cptx. Keep all Preferences set up.
What do you mean more by ‘unwanted changes’? What a cptl file offers more are placeholder slides, is that what you mean?
We actually have about 6 preset slides that load with the template. A boilerplate “title,” “objectives,” and “navigation” style information so IDs aren’t copy-and-pasting the exact same slides (because they are supposed to be identical) in every lesson.
Why not create master slides for them? I don’t think the objectives are the same in each course?
This post is wrongly classified as ‘blog’, but you posted a question, correct?
You start from which theme? I explained this bug, which appeared in the first release of CP2017, was fixed after my bug report in the second release, and reappeared as bug in CP2019 where it has never been fixed. I will post a link to a blog post where I explained how to fix it. In a separate comment to avoid eventual moderation waiting time.
You must be logged in to post a comment.
