Captivate Classic file locations

[iDoNotBelieveIt]

I have just updated from CP2019 to the latest version (Captivate Classic 11.8.2.254) and have discovered that the file locations are no longer in "C:\Program Files\Adobe\Adobe Captivate 2019 x64\" but rather "C:\Program Files\Adobe\". The new Captivate is in "C:\Program Files\Adobe\Adobe Captivate".

Slightly confusing, but if you have modified files like me and therefore the update breaks projects, I hope this will save some time and headaches 🙂

[Lilybiri]

Just want to comment that you are probably talking about the Captivate duo installed on a Mac.

This is NOT the same on Windows. Just to warn all users.

I rarely keep the default folders, check the location of the folders for both versions under Preferences, General. 

[iDoNotBelieveIt]

No, PC 🙂

I can see where confusion might arise, so thanks for pointing this out. For clarity I am not referring to the default locations that can be changed in Preferences, but where Captivate saves its core files. I have a customised index.html file, which gets overwritten every time Captivate is updated. Most users won't do this, so it will not be relevant to them.

[Lilybiri]

OK. That explains, but those folders will be different for a Mac user.

I am a lot more confused about the eLearning assets structure at this moment when using both 11.8.2 and 12.

[iDoNotBelieveIt]

I have only had a quick look at 12 and whilst it looks pretty, there is a lot of functionality missing compared with 11. But hopefully that will change quickly. My main challenge with Classic is getting objects to display as intended for mobile devices. It is very time consuming but I am learning some workarounds by trial and error.

[Lilybiri]

Pretty looking, but still frustrating after many years of testing.

You have no control whatever over where objects will appear on mobile devices. Within limits this was possible with Fluid boxes, and even better with Breakpoint views but it took working hours. I am busy trying to convert a Fluid Boxes project to version 12, and have a lot of bumps already. This is the goal:

https://www.lilybiri.com/published/CrunchNumbers/index.html

I am aware that the shared action - which I used 30x - needs to be replaced by an interaction which needs to be copy/pasted 30 times and individually edited. At this moment I am struggling with the loss of object styles, and having only text styles which cannot get a meaningful name is hard. Multistate objects cannot be duplicated (or copy/paste) within one container. You'll see that I use identical multistate objects a lot in this example.

Positioning is crazy, but worse is lack of reusability. Copy/Paste cannot solve everything.

[iDoNotBelieveIt]

Oh dear. That doesn't sound great. Sounds like there is a lot of work still to do. Thanks for the warning.