Targets and Alias files-how they work with conditional text

[parsonsv]

I have one Webhelp Flare file, and in it I use conditional text and create two Webhelp targets because the content goes with two different versions of my company software.

One version of my company software is Map only, and the other version is Map and Grid. So, almost all the content in Map is also in the Map and Grid file.

I have CSH help attached to every dialog box. However, I when I compile the help for the Map-only software, I get a bunch of CSH errors in my compile because some of the topics in the Header file are not included in the output.

I tried creating two different alias files and two different header files, but regardless of which alias file I assign to the target, Flare still compiles both header files and gives me the error.

Is there a way to add conditions to header files? How can I assign a header file specifically to one alias and not have it appear with the other? Does anyone have two outputs from their Webhelp and use CSH and can give me an idea about how you set this up?

Thanks

[wclass]

Yes - I generate several output targets from the one project that all need to use the same header/alias files.
No - there is no way to put conditions on header files, but I don't think you need to.

First up, what exactly is the error message you are getting - can I assume it is domething like "Generating alias file: Topic excluded from output: ..."? These are really warnings rather than "errors" so you can ignore them if you like.

Have you tried one header with two alias files? As both versions of the software use the same screens you really only need the one header file. But you can create a different alias file for each target you generate with only the topics you need, and this should eliminate the errors you are getting.

However, having said that, I just have the one header and one alias file and I put up with the errors/warnings. If I need to add a new topic, or delete one, I only have to update one CSH mapping file rather than trying to remember which alias something needs to go in, or get removed from.

[parsonsv]

Alright - sounds like I have to put up with the compile warnings. I know they are harmless, but I was considering them noise that might hide some actual warnings that I need to address

Sounds like that's the process though hey. I appreciate your response.

[rob hollinger]

Rumor has it,
Possibly Coming soon -
The ability to condition files and folders in the Project Organizer.

[wclass]

... I know they are harmless, but I was considering them noise that might hide some actual warnings that I need to address...

I was concerned about this as well, but all the alias errors are issued together, so I am confident that I won't miss other errors in amongst them - need to scroll back and forward though.