Database Search
TechHome
 |
- 1028 Error using Go rather than Run Button
- Add Separator to the WinBatch Studio Toolbar
- Adding File Types to Studio
- Background Check
- Bitness of WinBatch Studio
- Block comment and uncomment code
- Change File Save-Open Default
- Change Studio Default File Open Path
- CLR Files for Other Extensions
- Code to Convert Hex to Decimal in Studio
- Custom Syntax Colorization
- DirGet returning Winbatch System Subdir
- Disable Studio Keyboard Shortcut
- Extended ASCII Cursor Placement Issue
- F12 in WinBatch Studio
- Foreign Language Search
- Hitting n Key Causes Strange Behavior
- Interactive Debug Mode and GoSub
- Keyboard Shortcuts
- Keyword Lookup not Working
- Manipulate open file or highlighted lines in WinBatch Studio
- Null characters found
- Pass Params in Winbatch Studio
- Pass Parms to WBT while in WB Studio
- Problem wRight wLeft and wGetChar
- Recreate WinBatch Studio Environment
- Regular Expression searches in WinBatch Studio
- Save As Dialog in WB Studio
- Shift-F1 stopped working
- Turn off WinBatch Tips
- Unable to Run WIL Extension
- Using Debug to See Contents of Array in Studio
- WinBatch Studio Choppy and Slow
- WinBatch Studio Window Missing
- Wrap lines to a specific length
- WSHELP.DLL - WSHELP.INI question
- WSINIT.DLL Process Stays When Studio Opens
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Shift-F1 stopped working
Keywords: Shift-F1 stopped working
Question:
I was using Winbatch Studio on a different computer than it was installed on (through a mapped drive) and hit Shift-F1 to display help on the function my cursor was currently on. It prompted me to select the help file, but I picked the wrong one by accident. Now, even on the computer the software is installed on, Shift-F1 brings up the wrong help file. Any way to set it back to the way it was?Answer:
Go into:...\WinBatch\System\HelpLook at both the WSHELP.INI file and perhaps the WEH file associated with the help file. Examine both for the bad data. Fix.
Make sure all the HFxx entries are actually HFxx and not FHxx which was a bug floating around some time ago.
Basically the first time you hit a *.hlp file, a lot of thrashing aorund occurs to locate the file. Once the file is found, the located= entry is added to the weh file.
If you are interested in how all this really works, see the wspopup.mnu file that captures the right-click keyword lookup menu item and forwards it to the same place the Shift-F1 does, which is the wshelp.dll file.
Now, in spite of the DLL extension on this file, it is just a plain WinBatch script file. Find the :KEYWORDHELP entry point in the file. That's what both the SHift-F1 and the wspopup.mnu functions call. That kind of sorts out the help required, finds the files, runs help etc etc etc.
Article ID: W15351
File Created: 2002:12:16:11:33:38
Last Updated: 2002:12:16:11:33:38