script leaves FrameMaker file locked

[rlauriston]

The following script updates the specified RoboHelp project with any changes to the FrameMaker source. It works fine, except it leaves the last .fm file in the book locked (i.e. there's an .lck file in the FrameMaker source dircectory). How can I fix that? Or is this a bug?

var projectPath = "<path>\\<project>.xpj";

main();

function main()

{

        if(projectPath == "")

        {

               //Error!. Quit RoboHelp

               alert("Project path is not defined. \nPlease update the 'projectPath' variable in the script.");

               RoboHelp.quit();

        }

        RoboHelp.openProject(projectPath); // open the project

        RoboHelp.project.updateAll(true); // force-update FrameMaker source

        RoboHelp.closeProject(); // close the project

        RoboHelp.quit(); //quit RoboHelp

}

[Willam van Weelden]

Hi,

I’ve not encountered this problem and I’ve used the same code too. Is there anything special about the book or the last fm file? Special characters that my wreak havoc? Does this happen with all linked books or only with some linked books? Do you have the same problem when you manually update your linked docs in RoboHelp? I’m just guessing here, it does sound like a bug.

You can report a bug via: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform <https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&product=38> &product=38

Greet,

Willam

[rlauriston]

This is the only book I use with RoboHelp. Doing the same steps manually does not leave the file locked. I guess I could test it with a sample book to see if it's a bug.

The script is run by a batch file, so it was easy to work around the issue by simply deleting the .lck file.

[rlauriston]

I can't duplicate the problem with a test project, so Adobe probably wouldn't be able to either.