Adding Responsive Layouts to RoboSource

[Gene_Feldman]

Currently My team members and myself are creating a responsive layout to use for our projects, however, when we create the layout and add to Robosource on one machine, the other machines can see the screen layout but can not select to apply it. Does anyone know of a solution to allow multiple machines to use a responsive layout via version control in Robosource?

[Willam_van_Weelden]

So if I understand correctly, they have the layouts in the Output Set-up pod, but can't apply them to the output? Normally, I would suggest removing the CPD and it should show up.

[Gene_Feldman]

Will the CPD file recreate itself when the user goes back into the project?

[Willam_van_Weelden]

Yes. The CPD will be recreated when you open the project.

When working with source control, I would advise you to enable the option to always clear cache before opening a project to avoid problems like these. (Tools > Options > General)

[Gene_Feldman]

Ad this is done locally?

[Willam_van_Weelden]

Yes. The CPD is not checked in as it is a local cache. The options are specific for your RoboHelp installation. So every user will have to manuallyset it.

[Gene_Feldman]

If the CPD file is on source control should it be deleted?

[Gene_Feldman]

William, the clear cache seems to have fix partial issues, we have updated the settings and styels for a repsonsive layout on one machince.  However, when we log into another machine and access the same project, we are getting the confim replace for the style sheet (Main.css) associated to the responsive layout but the layout file is not being replaced.  does that make sense?

[Willam_van_Weelden]

You can overwrite the CSS. It may be handy to get the latest version of all files though the RoboSource software before opening the project. That should avoid any warnings.

[Gene_Feldman]

The warning and css file is not really the issue, but the espnsive layout file is not coming over to the other machine.

[Amebr]

Perhaps try deleting the local .cpd file on the other machine, do a "Get All", then open the project.

Many years ago we had problems in a multi-user environment where additions/deletions wouldn't carry across to other PCs, because the cpd was caching the configuration. We would delete the cpd before starting work each day, and communicate regularly about structural changes, to ensure we didn't have problems.

But I haven't worked in this sort of environment for many Robohelp versions, so unsure if this is still an issue today.

[Amebr]

You should remove the .cpd, .ldb and .pss files from source control if they are currently included.