by Dave Lee on Wed Mar 07, 2018 12:56 am
Well, the code in your app that makes the CSH call to the help has to use an identifier - it has to send something to the help.
But you don't necessarily need to hard-code that identifier in the app.
For example, the app could automatically generate the identifier used in the CSH call.
That's what we do in our applications. It's a Windows app, and in Windows each form/screen has a unique name and "path" (namespace).
So when the app makes a CSH call, it generates the identifier from the form's unique name/path; e.g. MyApp_FeatureArea_FormName
It's then my job to add all those identifiers to my Flare alias file, and map them to appropriate topics.
The identifier doesn't have to be generated exactly like this, the key point here is that each identifier used for CSH must be unique, and it must be fixed and can't change.
If there's a lot of identifiers, the developer could make this job easier by writing an app that generates a list of all the possible identifiers for you, in a header file format. That will save time, and make sure you haven't missed any.
The developer might take some persuading, but it'll save them time in the long run. For any decent sized project, this will be quicker for them than manually adding identifiers in the code, or asking them to fix bugs in those identifiers.