This content has been marked as final. Show 3 replies
Hey there Tom
From my experience, the only time I need full motion is during a drag & drop or scrolling type of action when the view "moves" like a film.
My suggestion is that you plan what you want to do (click here, then there, then select that button etc.)
Step 2 is to start a new project and select "Demonstration" as the recording type, spec the size of the recording window if needed and start recording (You might want to use auto capture which would automatically record all interactions and key strokes, but please remember to "manually" capture certain screens using Print Screen e.g. after a drop down menu has opened.) (Hint 2 - Rather record too many screens than miss one critical one out)
Step 3 would be to stop recording and edit the individual slides with captions, animations etc. At this stage, you can specify exactly how long each screen would display, when your captions etc appear and for how long they show.
In summary, a decently built demo has a seperate slide for each change in what the user would see on the screen, with FMR being used to "tie together" 2 views where a movement action causes the transition.
Hope this helps
Thanks for the reply, I think I'm beginning to understand how Captivate is meant to work.
It's a bit tricky though, since our software is pretty much all about drag-n-drop, adjusting scroll-sliders and other "moving" interactivity that we want to show. So I really need to produce a smooth animation of this.
Hi again Tom
No problem, the mind set that I tend to use is that every user interaction is a slide on its own, thus every individual drag & drop would be a slide, similarly all scrolling and highlighting etc. This helps a lot when it comes to editing and the "whoops!" factor becomes minimised if you only need to replace one faulty interaction or screen shot versus a slide full.