NedMaker wrote:
In EmEditor 9 Function Bar it will be corrected?

For example, on last button there is no appointed function.





Likely it is necessary to add customization that the user could appoint functions necessary for it itself.

owilsky wrote:
Hi,

I have two requests for EmEditor 9.00:

1.
For macros we have a trigger named "Before saving". Can we also have one "After saving"?
Reason is that we need to call a macro that determines which configuration to load with document.ConfigName based on the filename, not on the file extension.
And before saving there is no file name

2.
In "HKEY_CURRENT_USER\Software\EmSoft\EmEditor v3\Macros\Macro0" there is the full path to the macro, e.g. C:\Documents and Settings\Oliver\My Documents\My Macros\test.jsee.
This makes deployment of multiple macros to other computers very hard. If you enter a relative file name into registry (e.g. only "test.jsee"), EmEditor looks for test.jsee in "C:\Program Files\EmEditor".
How about changing that so EmEditor looks in the configured macro folder that is stored in HKEY_CURRENT_USER\Software\EmSoft\EmEditor v3\Common\MacroFolder ?

Thanks for listening,
Oliver

2. You can export settings as INI files, and then you can import at a different machine. When exported as INI files, a macro path become the relative path. Does this solve your issue?

owilsky wrote:
Quote:

2. You can export settings as INI files, and then you can import at a different machine. When exported as INI files, a macro path become the relative path. Does this solve your issue?

Not really, because in the exported INI file there is still the absolute path. If I import that file on another computer with another user name, I have wrong paths (I see the wrong paths in Macros/Customize at the bottom label).

I see two possible solutions:

1.
Use some kind of paths relative to home folder (my documents) like I suggested above

2.
Implement some kind of variable like %my documents% which can be used in exported reg files and ini files. These files can then be imported on the target computer easily.

Am I the only one working for a company and developing Macros for EmEditor and having the problem to deploy these macros to my users?

Oliver