![]() and if I need to edit the buttons after I have to edit them outside the application, rename them all, and bring them all back in. In Captivate, I have to create the buttons as image files in a seperate appplication, name them appropriately (for example, button1_down.png, button1_over.png, button1_down.png.) and then add those buttons in as images. In Storyline, to create a button with a hover state, I simply add a state. It is simply not as intuitive as Storyline, by any means.Ī few of the main things that bothered me when I worked in Captivate 7 for a recent project: I'm a very advanced Adobe Illustrator and Photoshop user, and I still found myself struggling with the Adobe Captivate 7 interface. Any idea on how to get motivated by a tool you don't like? The only thing: I really wanted to give a chance to Captivate, as some IDs are happy with it. She offered to consider buying the SL license so the battle is not lost. I warned my manager: I won't reach the professional level I used to have so easily. At first, Captivate tutorials really don't explain how to do something, only they mention you can do it.Īs for their community. So I really appreciate that offered several links to learn more. I find the environment really arid, I call it the Captivate dessert, it is really dry and unpleasant. At work I'm trying hard to learn Adobe Captivate 7: I don't see the intuitive part anywhere. ![]() The 30 free trial days were more than enough to finish my first projects, and I've only grown in the professional use of Storyline thanks to this community and to the great tutorials posted. I bought a SL license when I started being a freelance. Yeah, you just said it: the learning curve.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |