Branching View in Captivate
Hi Community,
I’m looking learn if anyone uses the Branching View in Captivate? If so, what’s your experience? How do you use it when developing your projects?
I was excited to learn that a graphical flow of my project existed, specifically because I had an issue. I was hoping that I could use it to pinpoint a flaw in flow of my project – use of Advance Actions.
My point…
The view seems inconsistent, and I’m having trouble deciphering it.
Can you share your experience?
Forgot to tell that there is another rather unknown panel which I use all the time: ‘Advanced Interaction’ (F9), not to be confused with Advanced Actions. Terminology in Captivate can be confusing. I really need to write out a detailed exploring blog about that panel.
I didn’t even realize this was almost 10 years old. No panic, nothing much has changed except that you can resize the panel now (had insisted by multiple requests) which was not possible in older versions:
http://blog.lilybiri.com/unknown-is-unloved-flemish-proverb-branching
Quite a while ago I created a blog about the Branching view (will post the link in a separate comment to avoid moderation delay). However, although I use Captivate daily, I do not use it anymore for a couple of reasons:
- For some reasons opening this panel can lead to crashes, since some versions. Do not know why, but this has been reported by multiple users.
- Only the Branching scenarios created in a very old way will be visible, not those which are done using all type of actions with button or other events.
For complicated branching I will sit down and lay out the branching before creating the Captivate application, with a mindmapping tool or even with…. pen and paper (almost the only situation where I do that).
You must be logged in to post a comment.