September 20, 2018
Copying into objects that have States OR converting a group into a state
Comments
(2)
September 20, 2018
Copying into objects that have States OR converting a group into a state
Newbie 3 posts
Followers: 0 people
(2)

Hi there 🙂

A colleague and I are converting a lot of Captivate 5.5 old swf based elearning into Captivate 2017 HTML5 versions. the HTML Tracker tool is excellent for this. In the past, previous developers were creating multiple roll overs using widgets that we are breaking into, copying out the content in situ and pasting on the stage outside of the widget.

What we would like to do is either group these images/text etc then copy and paste them into a new state of a state-based object. But this seems impossible. A work around we thought would be to create the group and then some how turn this into a multi-state object. But no again. Turn it into an object like you can in Animate (Like an mc which is then stored in the library and can be drag and dropped into another object) and then drop it into a state, but you can’t do that.

At every turn we are blocked. It seems ridiculous that we can’t copy and paste in this way or create MSOs from groups. And the only solution is to rebuild from scratch? We surmise then that we are missing something vital. What have we missed? Surely this is something we can do in Captivate 2017?

kind regards,
Claire

2 Comments
2018-09-21 09:13:04
2018-09-21 09:13:04

I posted an answer, but you’ll have to be patient. Since there are links (to published posts in this forum) it has to be moderated.

Yuo don’t mention the Library as tool. If you import all the images in the Library it is a breeze to get an image in a state. That doesn’t solve the problem for texts (unless you convert them to SVG’s) nor groups.

Like
2018-09-21 09:11:10
2018-09-21 09:11:10

I am very sorry, agree that Multistate Objects which are very powerful have several limitations like you tell about copy/paste. Please log a feature request.

If you are converting to a responsive project (which you don’t mention) Multistate objects are indeed the way to go. It is rather easy to drag images from the Library into a state. If you are aiming at a non-responsive project (which can be rescalable HTML) you can keep the groups instead of needing a multistate object. Recently I posted two articles comparing Hide/Show (using groups) with State changes in Multistate objects. Have a look:

https://elearning.adobe.com/2018/07/force-clicking-hotspots-comparison-2-workflows/

https://elearning.adobe.com/2018/08/forced-clicking-hotspots-fluid-boxes-project/

 

Like
Add Comment