Adobe Captivate 5 import caption style issue

Question

Hi dear all,
I use captivate 5, and so is my college. We try to make a base template to use and distribute to all that will work with us.
There are issues with setting standards in Captivate 5
Problem no 1
One issue is that all changes made to caption styles are gone after you close and open your project again.
a) Edit
b) Object Style manager
c) Change styles on e.g. default
d) Press button "Apply"
e) when done press button "OK"
d) Save and close
f) Open
d) Enter Object Style manager = all styles are back to factory settings.
Respons to predicted questions:
Yes we tried both opening Captivate 5 as an administrator and as a normal user.
Yes my account on the computer is the admin account
My college got the "Project-all-styles.cps" file I exported by choosing "all styles of all objects" and pressing export
This is done under Object Style Manager.
Problem no 2
My college successfully imports the file "Project-all-styles.cps", by choosing the import function under the Object Style Manager
This results in one [Default Caption Style] that still is with factory settings and a new [Default Caption Style]_1 with my preferences are made.
Problem no 3
The [Default Caption Style] can not be deleted, i want to remove the one called [Default Caption Style] and change name on [Default Caption Style]_1
I want to remove _1
Solution 1
Find a way in Captivate 5 to unlock the "change default lock" that seems to be there
Solution 2
Enter the file that contains the default styles and change manually by typing by hand. I could not find th file for that. It does not seem to be an *.ini file containing that information.
I hope for good answers on these question.
Best Regards // Daniel Perez

Answer 1

Just make it easy
1. Use an understandable language like when defining styles
When opening a *.cps document it looks like this
And that is not good.
function(){return A.apply(null,[this].concat($A(arguments)))}
$   < C a p t i v a t e S t y l e s / > •     ‰   ÷   Š     ‹     &#127;   “   Œ                   D   ~   ÷   “   &#141;       “   Ž       “   &#143;       “   &#144;       “   e   U   f   &#127;   j   m       n       k   g   l   h       i   6   [ D e f a u l t   R e v i e w   A r e a   S t y l e ] k   m       n       k   g       h       i   ~   k   g       h       i   ÿÿÿÿk   g       h       i   ÿÿÿÿk   m       n       k   g   Š   h       i   ^   k   m       n       k   m       n       k   m       n       k   g       h       i     k   g       h       i     k   g   ÿ   h       i     k   g   ï   h       i     k   m       n       k   m       n       k   m       n       k   g   /   h       i       k   g   ¶   h       i       k   g   ·   h       i       k   m  
   n       k   m       n       k   l   ’       “   •     ‰   ‘'  Š     ‹     }   “   Œ                   D   |   ‘'  “   &#141;       7   “   Ž       7   “   &#143;       “   •     ‰   ë   Š     ‹     7   “   Œ      
2. Let the user choose within three options, and be able to change choice later.
a. Embed the styles in the project
b. Absolute-link to a folder, network folder or URL (with the URL it is easier to collaborate between individuals and also change styles centrally if needed)
c. Relative-link to a file. (E.g. one homemade folder called styles that always are at the same level as the folder with the projects)
This makes it easier to move entire project to other computers.
3. Have a button that says "default" then the issue of overwriting default is not an issue anymore.
4. Do the same three steps with question pools, motions, and all other features that could be lifted out in their own files. (E.g. skin editor)
I think that it would make this tool a really really really tough competitor to beat.
Just to sell it in a bit more, if e.g. the question pools would be an easy understandable XML then it would be no match to export questions from old systems/PDF's or read in questions in paper form with an OCR and transform them to useful XML's
Best Regards and very hopeful for the future to come
// Daniel Perez