[Yutaka Emura]

v18.0.4 fixes the Suggestion 3 issue.
I can’t reproduce the Issue 2. However, it is not unusual that the candidate list is displayed somewhat slower if the dictionary size is large.
Can you please write numbers in details (how many seconds to display the list, and how large the dictionary is)?

[Yutaka Emura]

Hello LTT,

These issues will be fixed on the next version. Thanks!

[Yutaka Emura]

You can go to the View page of the Customize dialog box, reset the “Use System Color”, and click Text and Background buttons to customize colors.

For German translations, can you please clarify which text you are talking about? Please write more info, and you can send me a screenshot at tech @ emurasoft.com

Thanks,

[Yutaka Emura]

There were issues with menus on v18.0.0. We will fix the issues and release a minor update shortly. I apologize for any inconveniences.

[Yutaka Emura]

Hello,

The new version (v18.0) moves commands in “This Document” up the hierarchy by default.

You can also access the Bookmark related command by right-clicking on the Line Numbers of the left edge of the EmEditor window.
Or, you can press CTRK + K to show User Menu (1) to select a selected number of bookmark related commands.
Or, you can record a bookmark related command as a macro, save it as a macro file, and add that macro to the toolbar.

Thanks,

[Yutaka Emura]

Hello LTT,
We’ve fixed all these issues on the next version.
Thanks,

[Yutaka Emura]

Hello LTT,
All issues except 2 and 3 will be addressed on the next version. I am not sure if I understand/reproduce the Issue 2, but it might be also addressed on the next version. Please see if it is fixed when the next version is released.
All suggestions will be also addressed on the next version.
Thanks,

[Yutaka Emura]

Hello David,

If you use “eeExFind…” flags in Find/Replace macros, please use them as a separate parameter like this:

document.selection.Replace("de_DE@(.+?);","",eeFindNext | eeReplaceAll | eeFindReplaceRegExp, eeExFindRegexBoost);

If the issue still persists, please let us know.

Thanks,

[Yutaka Emura]

Hello,
The next version (v17.9.0 beta) will address this issue.
Thanks!

[Yutaka Emura]

** Any way to delete the last editable line(s) leaves an empty line.
** Triple-clicking in an editable line selects the line including the newline character, except in the last editable line.

These are correct behaviors.

All the other issues will be addressed on the next version. Thanks!

[Yutaka Emura]

These issues will be addressed on the next version. Thanks!

[Yutaka Emura]

We reproduced the issue when the Show Markers on Vertical Scroll Bars is cleared in the Scroll page of configuration properties. We will address the issue on the next version. I am sorry for any inconveniences, and thank you for reporting the issue.

[Yutaka Emura]

Issue 3-3 also occurs on Untitled documents.

I am not sure what you mean by this? Are you talking about a normal untitled document (NOT grabbed text)? If so, this is an intentional behavior.

[Yutaka Emura]

I am not sure if you tried, but you can use the Advanced Filter on the Filter toolbar.
As for your second suggestion, I am not sure if the “Wildcard” is a good solution. Regular expressions should be easy to understand and flexible. Please let me know if you need more help.
Thanks,

[Yutaka Emura]

As for double-clicking on an Option item, this will be fixed on the next version.

[Yutaka Emura]

All these issues will be fixed on the next version. Thanks!

[Yutaka Emura]

Issue D: I reproduced the issue. Thank you.
Issue E: I will think about an option in the future.

[Yutaka Emura]

Issue D: We can’t reproduce the issue with EmEditor v17.8.0 whether DirectWrite is on or off. Can you make sure you are using the latest version of EmEditor, and can explain once more in details?

Issue E: WordComplete plug-in does NOT monitor dictionary file changes. If this is important, we might add extra code to monitor those changes.

Issue G: We reproduced the issue, and will fix it on the next version.

Issue ZZ: We will add these accelerators on the next version.

[Yutaka Emura]

As for the macro, yes, you are right. The last line of the macro was not necessary.
I might think about the ability to grab EmEditor by EmEditor. Thanks,

[Yutaka Emura]

Issue E and G: I am NOT sure what these issues mean. Can you please describe them?
Issue F: I might think about adding a new option to specify the encoding of the dictionary file.
Issue H and I: Since WordComplete is a plug-in and NOT a core feature of EmEditor, it isn’t as flexible. To address these issues, we would make it a core feature of EmEditor, otherwise EmEditor would become much slower.
Issue J: It is an expected behavior by internal code design. We’ll fix the Help in the future.
Suggestion 3: The Home/End key will be available on v17.8.0. Thanks!

[Yutaka Emura]

OK. It will be something like this on v17.8.0:
[72|>80]

[Yutaka Emura]

Hello,
I can’t reproduce the issue D. Can you?

[Yutaka Emura]

The Automatically Name Untitled Document option issue will be fixed on v17.8.0. Thanks!

[Yutaka Emura]

These issues will be addressed on v17.8.0. Thanks!

[Yutaka Emura]

Hello,

“currDoc.Activate();” was necessary before the “doc.Saved = true;” line because a particular internal code reason.

We can’t allow EmEditor grabbing EmEditor if both documents are in the same group window by design. Why do you need this ability?

Issue 3-2 and Issue 3-3 will be addressed on the next version.

Thanks for all the comments!

[Author]

Posts