Yes, this is what I've always done, even though I've expanded the documentation of some apps to be quite long any more. What I am considering doing now, for apps which have a lot of documentation, is to create the docs as an html file, and use the VirtualBrowseMode object from the GW toolkit to display it. This would allow me to structure the docs into various levels of headings, lists, tables, etc. However, unfortunately, there's no way to link to this from the standard help dialog toolkit object, so I guess I will put a summary of what the app does as the text there, and instructions as to how to bring up the apps docs in a browser window (probably via a menu choice on the app menu). A little more trouble for the user to get on to at first, but for long docs, they'll probably appreciate the organization which allows them to use navigation commands. hth, Chip
_____ From: Vic Beckley [mailto:vic.beckl...@gmail.com] Sent: Monday, April 02, 2012 4:10 PM To: gw-scripting@gwmicro.com Subject: RE: One more dialog question - please Can't you use the StandardHelpDialog object of the GW Toolkit to display the help text? Just put it in your xml file under the strings section with a string Id of script_help. Best regards from Ohio, U.S.A., Vic E-mail: vic.beckl...@gmail.com From: David [mailto:eleph...@tele2.no] Sent: Monday, April 02, 2012 2:49 PM To: gw-scripting@gwmicro.com Subject: One more dialog question - please I now finally have got a dialog working, for my app. Wonderful. But I have one question. The documentation for the app, currently is available in a text file. I wanted to have a button in my dialog, that would open a ReadOnly edit box - or something like that - and then load the documentation ito that box. Well, that was the idea. Is there any better approach? I do not know, how to create a standard Windows Help file or the like. So, I simply wrote the documentation in Notepad. But, of course, the user should not be able to edit the docs, so I can't simply load it into Notepad for him either. Smile. The documentation is something like 300 lines long, so the user will need to scroll up and down the screen. Don't know, if the edit boxes that WE provides, can hold that much. So, if anyone have experience here, and/or any good suggestions to the best approach, I am all ears. My idea was, since the documentation would be made available in more than one language, to save each language in its own file, and via my XML file - with a simple string - to direct the app to the currently locale documentation file. That part is not a problem, it works already. But my problem is how to get the contents of the file, displayed on the screen in the best way. Thanks for any assistance.
