Was this ever working for you? I think it’s just a side-effect of WebHelp…
I've seen your site and it's tremendously helpful.
Unfortunately, it doesn't address my issue.
Why it can't focus on the window being called seems strange to me.
1 person found this helpful
Did you see the bit about changing the "#" to "?" ?
That is really for when using a URL rather than an ID and I'm not a developer so I don't know if it will work there.
If that's not of help, I suggest you take a look at Willam van Weelden's site as he has some more detailed information. http://www.wvanweelden.eu
See www.grainge.org for RoboHelp and Authoring tips
Thanks for the responses, but this doesn't really help.
I'm using a simple URL to make the call.
(That's all I can do within the web app API console I'm working with.)
I have to give up for now.
I've just appended >>newwnd=false to the end of my calls, so the help appears in another browser tab, rather than its own window.
This isn't great, since each call opens a new tab, but that's better than the help window disappearing behind the sea of open windows most of us have going on, only to cause the user to hunt for it (if they even know it's there).
Thanks all for your pointers.
If I ever find the time to really work on this issue, I'll post a fix (if there is one).
RoboHelp user since v1.1