Context sensitive help for powerbuilder

[robogroup]

hello,

I am very new to robohelp. In our company they are using Robohelp x4.1 for powerbuilder applications with web help. I would like to know how to create context sensitive help for the application.
For example. If i open a window and click on the help it should take me to the help information for that particular window.
Right now no matter what window is opened, if i click on help it goes to the main page of web help.

Any suggestion is greatly appriciated.

Thank You

[Peter Grainge]

Welcome to the forum

See the topic on my site about calling webhelp. Explains how to call the tripane window with the CSH topic.

[MergeThis]

The RoboHelp HTML online Help has a section titled, amazingly, "Context-sensitive Help."

In it, you will find that this type of help is a cooperative effort between the Help author and the application's developers.

In addition, you can avail yourself of Peter Grainge's helpful hints.

Come back if you're in need of any more detailed answers.


Good luck,
Leon

[MergeThis]

Ah, geezzz...tripped over Peter again!

Sigh...

[Peter Grainge]

OK, so the waistline is spreading a bit. It'll happen to you too.

[robogroup]

Thank you very much.. Let me try these and come back to you if i have more questions..

[JJG10101]

Hey, it looks like I've got a similar question. 😉 We've got a PowerBuilder home-grown app, and I've been tasked with creating help files for it. A few specific questions:

* I'm using RH 7. Does that make a difference?
* Does the PowerBuilder app pass "parameters" to the help system to identify where the user was when help was invoked?
* Are there any things to be aware of when creating CSH for a PowerBuilder application?

Thanks!
JJ

[MergeThis]

Have you researched the areas mentioned in last year's replies to robogroup (specifically, the ones from Peter and me, on 6/7)? I don't mean to sound harsh, but there are rarely any bumper-sticker answers to questions of this type; we users usually point other users to where they can identify solutions.

Keep in mind the first rule (okay, MY first rule!) of CSH: work closely with your developers to determine who will provide window/field names and who will refresh that information and how often. Start with testing for a single window (and field and control, if so decided) and expand to multiples for testing of navigation and the use of the Back button, etc. Also, remember that business decisions (by the upper-management types) can also determine what you and the developers are allowed to do.


Good luck,
Leon

[JJG10101]

Yes, I did a bit of research, but still had some questions. Fortunately, most of the questions have been answered. I would agree with your #1 rule: working closely with developers is critical. Again, I think I'm pretty lucky, as our development staff is quite eager to implement help.

Thanks again.