![]() ![]() above in the picture, outlined in red) mean that these features are disabled?īelow, I typed out Rh help topic, but I am still unclear on the descriptions. If I select the Master Page check box (enables the Master Page and CSS radio buttons) and select Master Page (i.e., my pull down list would show Product A and Product B), will this affect any Styles that are using my RhSytleMapping.css?.If I remove the footer verbiage, how can I apply a different footer for Product A and Product B when I generate CHMs?.Since the inception of Rh 11, we now have the optional to use multiple header/footer master pages for “Print Documentation” hence I can assign a specific footer for Product B and in theory, I can remove this footer section. ![]() Picture below shows the HTML Help Options. What makes the two products (Product A and Product B) unique during the generation process showing this header, it is using a Conditional Build Tag over the verbiage in the footer section hence, trigger by the “Conditional Build Expression”. Note, this master page is used for both instances (Product A & Product B). My goal: To generate two different CHMs that has its own branding (proprietary verbiage in Footer section) appear on bottom of help topics located on the Online Help window (CHM), WITHOUT using the old configuration (mentioned below).Ĭurrent configuration (Old): A single Master page with a Footer that has Product B proprietary verbiage. So this is not a question as much as a problem with the resolution I came up with that might help others as well. I have not checked that all my links exist, however, I did NOT disconnect my resource that was local to my hard drive and everything seemed to work fine. ![]() I finally found a way to disconnect my Resource Manager links to the SharePoint sites-once those were disconnected, I could open and check out the files appropriately. I checked and the cpd file doesn't seem to be in the SharePoint library and Clear project cache (.cpd file) before opening any project was selected. I checked to see if the sample project would open and it behaved the same way-hanging and never allowing me to work with RoboHelp. It appeared to open the project, but hangs, not allowing me to work on the project. I started RoboHelp again about an hour later to see if it would open the project. When I set it up, it loaded the files into the library, then hung with a spinning circle and "not responding" in Task Manager for several hours before I finally just closed RoboHelp. I had setup my version control previously on TFS/SharePoint site but the IT department got rid of that site, so I disconnected from that version control and then created a new version control link to a new SharePoint site for this project. I am using RH 11 on Windows 8 with SharePoint Foundation. So far I've not found any such information in the RoboHelp Help or online.ĭoes anyone know where I can find a list of RoboHelp HTML project management files, such as the PSS file, that should never be checked into Source Control? I vaguely remember reading something somewhere once upon a time about not checking certain RoboHelp project management files into Source Control. Two years ago it was not being checked in.) (I think the PSS got checked in by our Release Engineer when he was trying to solve some other problem. No more conditional build tags or unwanted Single Source Layouts, etc. We deleted the PSS and stopped checking it into Source Control. ![]() Eventually, thanks in part to an old post from Peter Grainge, we realized that the PSS in Source Control contained a lot of that old information. For example, I had removed all conditional build tags from my project, but their version still included the build tags. When my two colleagues recently "got" the latest project files from Source Control, they also got items that had been removed or deleted. Running RoboHelp 11, integrated with Team Foundation Server and Visual Studio 2010. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |