Help & Manual Forums

Thanks for the heads-up on eWriter Tim. It does sound like it has some advantages, but it also traps you into Windows. So we hope that you'll keep maintaining WebHelp, because at the moment we'd prefer to be a bit less dependent on Microsoft (see the Edge gyrations etc..).

Whew. Problem solved, we now have functional (and context-sensitive) help. It turned out, as so many things, to be mostly a tangle of user errors. We tested with the 'Local without web server' build option on, and we tested with the '#' in the URL for context IDs, but we seem to not have tested with...

Hi Alexander, thank you for helping detangle this.. This particular help we distribute with our software. This is Windows software, generally it gets put on a common server and accessed with a local-path URL. Let me emphasize that we do get to the home page of the help perfectly well, and in fact ev...

So you know that you're using an anti-spam tool that blocks the software you sell, and you think that's normal?? I guess it works for you, since it conveniently allows you to push off urgent support for a week (so far), right? I hope potential customers see this, and heed the warning.. But you know,...

Sorry Tim, your mail is not fixed.. Delivery has failed to these recipients or groups: support@ec-software.com (support@ec-software.com) A problem occurred during the delivery of this message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpde...

Well, I'd do command-line compiling if I thought that'd solve my problems.
But as I said, you have popups that describe the function of the options, but nothing on how to set them, not in the tool, not in the documentation..

I can generate a map with the context tool all right, but then what do I do with it? What format is best/most standard, where would I put the resulting file, how would the resulting help know to use it?? No hint of path configuration in the skin variables, not a peep in the documentation..

Yeah, thank you, I've read the documentation forwards, backwards and sideways. It does imply that you can generally use links to context ID numbers, but nowhere does it state explicitly that you can do that by default in PP 3.46, it only talks about using that build option, which in turn can only be...

So we have a workaround, an ugly one... If we use a Premium Pack 3.46/V2 WebHelp skin, actually a version 2.60 one, we do get a help that's both functional in chrome and generates context IDs so that our context-sensitive help works. It just looks uglier, and doesn't allow us to configure nearly as ...

I've found the 'Build Options' in the Edit menu of Premium Pack 3.46 in hmToolbox.exe, and they do correspond to the options I see when I publish the project. The documentation describes what they do adequately, but nowhere can I find how to turn them on or off for the skin... Any hint?

For the purposes of context-sensitive help, we need a map of context IDs. This is presented as an option on some skins' include options ("Context ID Links").But not in the new Premium Pack 3.46 skins :-(. It seems this used to be handled by an OPT_CONTEXT build option, is this correct? But...

So yes, sadly, it seems that the so-called Premium pack does have skins that are compatible with chrome, but that they omit the option to generate the context IDs that allow us to do context-sensitive help. Are there other skins that would do both? Is there a way to customize a skin to offer that op...

For reasons of chrome compatibility we upgraded Help&Manual to use a Premium Pack 3.46 skin, one of the Responsive WebHelp ones. We tweaked it a bit, but only for color and font. Only now our context-sensitive help is broken - we are using the same links we used to, we seem to be aiming for the ...