WOW Yutaka, thanks, works great.
I will test some more, but basically that’s how i had imagine it.
My experiences:
First i got an error
---------------------------
eehelptool.exe - Komponente nicht gefunden
---------------------------
This application has failed to start because MSVCR100.dll was not found. Re-installing the application may fix this problem.
Die Anwendung konnte nicht gestartet werden, weil MSVCR100.dll nicht gefunden wurde. Neuinstallation der Anwendung könnte das Problem beheben.
---------------------------
OK
---------------------------
That’s because i didn’t have the “Visual C++ 2010 Redistributable Package” installed.
I had only 2005 and 2008 installed.
Now i got interim the MSVCR100.dll and put them in the
same folder as the eehelptool.exe and it works fine.
I have set up this tool as:
Titel: short description, e.g. VBScript help file
Command: path to eehelptool.exe, even relative to EmEditor folder, e.g. myDocuseehelptool.exe
Arguments: path to help file, even relative to EmEditor folder, e.g. myDocusSCRIPT56.CHM $(WordText)
Initial Dir:
Icon Path: path to icon resource, e.g. \%SystemRoot\%hh.exe for the default help file icon
Note the ” $(WordText)” after the CHM which will search the CHM for just that selected keyword.
In fact, the keyword even have NOT to be selected, just the cursor right before the first char or after the last char is enough for “$(WordText)” to work. Great.
Of course this “search for the keyword” feature will work only for CHM files which are compiled with an proper index. If not, or if you just want to open the CHM without jumping to the “selected” word, you don’t need to include this ” $(WordText)” part to your Arguments: definition.
– – –
I have found one improvement wish:
the keyword is found and selected in the index tab,
but i miss:
* pressing enter (so to say) to open the page in the preview pane for ease use
* having the focus in that preview pane to allow immediately scrolling
Maybe that can be included too?
– – –
Question:
will this tool be part of the core package or even be included in the EmEditor.exe?
Maybe from interest for you:
other editors allow to have one syntax related help file (like SCRIPT56.CHM for *.VBS) per syntax language configuration, and all are accessible via the same shortcut (like Alt+F1).
Which CHM is opened depends on the currently active syntax configuration.
If i am on an VBS doc, the vbs.CHM is launched.
If i am on an HTML doc, my html.CHM is opened.
So we didn’t need to have 5 tools / toolbar icons / shortcuts
just to open the syntax related help files. One would be enough.
Just some ideas. Thanks for EmEditor. Great Tool. Well done.
–
Ah, thank CrashNBurn too. I have tried that before posting my question but found it not works
well with relative paths and all over all that is not that easy for the average user (beginners)