Captivate 9: Smart object states are not allowed on master slides??
If anyone can tell me I'm wrong (the 'question' I'm posting I suppose) then please do - and tell me what I'm not seeing in this program. Thx!
I have a large module series just completed for a high profile pharma product sales force - all built in my former Captivate 8.whatever software. It was required I build a custom and fully branded interface (as it usually is) and not use the gawd-awful looking, school teacher friendly, built in stuff. All of the shell/interface controls are on master slides (as they should be) - and they are smart objects that use images in their button states. Worked great! A master slide for no next, one for quizzing, one for no previous... you get it. In addition - I have complex animations that require certain artwork come into the content area from an offstage position - so the master slide elements HAVE to be selected as always on top (another reason for placing the controls on the master slides. Some of my animations are Edge Animate - so those are fine - but the Captivate timeline based stuff cannot be 'masked' obviously.
Guess what?? Captivate 9 not only busted all of the controlls (and all custom advanced actions btw) - which needed to be rebuilt using their new "states" method - but for some bizarre reason Adobe brilliantly REMOVED states capabilities completely, from any objects that are placed on master slides... WHY!? Now - the projects I opened in it (which where conveniently converted to C9 now) do not have any visual user feedback for my custom shell controls (no rollover states). Am I the only human that builds custom controls and requires them to be in the most logical location... the master slides?? I'm at a loss with this absurd oversight - especially when it was already possible in Captivate 8. Really bad call people.
Hopefully - someone can tell me I'm an idiot and I'm not seeing a simple button somewhere....
