Storyline limitations in comparison to Captivate

Hi, I am a Storyline user, it´s a great tool, fun and powerful, but recently I had to create some courses using Captivate (Cp). Though in balance I prefer Storyline, mainly because it is more "visual", I´d like to mention some Cp features that I would like to see in SL.

• Captivate has actions that trigger animation effects (for example: "when clicking this button, apply a wipe effect to that picture"). To my knowledge, SL doesn´t have this feature; a somewhat similar roundabout is to trigger a state change, where said state has an integrated effect, but it´s not as straightforward as Cp. 
• Cp makes an effective difference between objects hidden in the edit timeline and objects hidden in the published or preview output; for example, in Cp, if you hide a circle in the timeline because it gets in the way of another object you need to manipulate, that circle will appear in the published output no matter if you forgot to click the show box in the timeline; it will be hidden in the output only if you mark another specific box. Instead, in SL the objects you hide in the edit timeline are also invisible in the output if you forget to activate the eye icon; this is often confusing and frustrating; the Cp option is preferable , or at least add a warning text before publishing or previewing: "One or more objects are hidden in the timeline and won´t be visible. Do you want to continue?"
• In Cp you can delay actions very easily (e.g., "when clicking this button, show this text, wait three seconds, and show this picture"); while in SL you can create a motion path that serves as a delayer, this means more clicks and triggers.
• In Cp you can substitute a picture by dragging thumbnails over it, but not in SL.
• In Cp, the library keeps an item even when there are no instances of it in the project. In SL, instead, if you delete an item (a character, for example) it will be deleted from the library too, so if ultimately you decide that you want to use that character, you have to import it again to the project: more clicks.
• In Cp you can update all the instances of a picture in one step (not sure that SL does the same).
• Captivate has a ribbon to place and align objects (same as SL) but in Cp it includes some very useful buttons to make two or more selected objects the same lenght, width or both; this saves many clicks.
• Another issue with SL is that after you create or paste a trigger, the list of triggers in the panel moves abruptly, and this forces you to do a visual search of your trigger. This is a little bothersome. The Cp interface for programming actions lacks thumbnails of the objects (that´s a great advantage of SL), but is more stable. The trigger logic is great, but please consider fixing this  interface annoyance. UPDATE: The new trigger panel solves this issue very well.