This content has been marked as final. Show 4 replies
So they've tested this isn't an issue with other HATs?
Take a look at Calling WebHelp on my site. There is some information on this issue there.
No, nobody at my company has tested this specific problem with other HATs. It's unfortunate that we are not going to see this through, especially after all the work I put into it.
Yes, I did have the programmers look at your site (nice site, btw!), but they said it's not what they're looking for. They want to be able to call the help, show the help, have the user go back and forth between previously viewed pages and have the help always in the foreground (sigh!).
I believe that is down to them rather than the help tool. You'll find out after you have tried a few more HATs.
Look forward to seeing you back here. :-)
It's a C++ issue. Your app "remembers" the instance that is still open, thus your "problem." Need to call a new instance from the app. This could also call a new tab to display the topic.