Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
.CHM and user-defined field labels
Message
From
08/02/2010 14:52:38
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
 
 
To
08/02/2010 13:46:36
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
01448161
Message ID:
01448182
Views:
40
>Just wondering -- does anybody have any idea if there is a way to set up something so that .CHM files can adapt to "user-defined" field labels? Say for example your program has phone01..phone10 and the screen label for these can be configured (using a config utility or configuration screen in application). Although it's relatively simple to have your input screen then adapt to configuration changes, as would be changes to menuing system, but when it comes to help files, I haven't figured out a way. Back in the DOS days when FPD used DBF files for online help, you could simply modify the memo data (you would have two memo fields -- one used within the help, and another with the original unedited version w/ tokens identifying user labels -- then it's a matter of using the "original" and replacing those tokens with user text to generate the display text). I suppose one way would be to not use compiled help and use directory full of HTM files and set up hook for help events to select the appropriate one -- but that could get rather messy (even if you isolate the HTM files into a separate subdirectory).

If your html isn't too complicated, you can still keep your help in dbf files with a few textmerge fields inside, and merge on demand. VFP is extremely fast with generating html, so invoking a regular browser (which the user probably already has loaded) with your generated page may actually be faster than invoking the chm reader, or whatever they use for help in Windowses nowadays.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Previous
Reply
Map
View

Click here to load this message in the networking platform