Forum Replies Created
- Posts
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,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,
** 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!
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.
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.
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,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.
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,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!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!
Hello,
Suggestion 1:
The next version (v17.7.97) allows you to do searches par your request.Suggestion 2:
We will think about that in future versions.Issue A:
The next version (v17.7.97) addresses this issue.Issue B:
Already fixed on v1q7.7.96.Issue C:
I am not sure where you want to double-click. Can you please describe in details?Issue D:
If you select Keymap on the Help menu, “All Configurations” check status will be restored.Issue E:
We might think about changing the UI in the future.Issue F:
We optimized the behavior.Issue G:
The behavior depends on whether the focused item is at the top of the multiple selections, or the bottom of the multiple selection. If the focused item is at the top of the multiple selections, pressing UP will set the focus to the search box but I think this is the correct behavior.Issue H:
I might think about that in the future.Issue I:
The next version (v17.7.97) addresses this issue.Issue J:
The next version (v17.7.97) addresses this issue.Issue K:
It depends on whether the “Keep this Window Open” button is pressed on the Quick Launch window. The next version (v17.7.97) addresses this issue.Thanks for all the bug reports!!
Hello,
As for Suggestion, you can use the following macro:
currDoc = document; docs = new Enumerator( editor.Documents ); for( ; !docs.atEnd(); docs.moveNext() ){ doc = docs.item(); if( !doc.Saved ) { doc.Activate(); doc.Saved = true; } doc.close(); } currDoc.Activate();As for Issue 1, we don’t support EmEditor grabbing EmEditor, please! We will disable this on the next version.
As for Issue 2, we will undo the “Close without Save” command change. I don’t really want to change the specs back and forth. Please think twice before suggesting a change or consider writing a macro next time.
As for Issue 3, I agree. We will change the initial status to no “*” for grabbed text.
As for Issue 4, Currently, the split persists. Do you want the split NOT persist?
We finally figured out the reason of this issue, and it should be fixed on the next version.
Thanks for your patience.I reproduced the issue, and it will be fixed on the next beta (v17.7.95) but not all cases are supported, for instance, Undo after deleted lines.
