- July 22, 2018 at 1:14 pm #23556
If Only in Candidates is selected, both ABC and abc are used as a candidate, and typing A or a displays both ABC and abc.
If Both in Candidates and in Typing is selected, both ABC and abc are used as a candidate, but typing A displays only ABC, and typing a displays only abc.
** But currently “Only in Candidates” is behaving the same way as “Both in Candidates and in Typing”.
The default dictionary has:
** The refreshment of the candidate list is slower when “Both in Candidates and in Typing” is set. (Especially with lowercase typing.)
Open 2 windows with the same configuration.
Change the “Match Case” option in WordComplete properties in one window.
** The behavior in another window does not follow the change instantly.
(I didn’t test on other options.)
Open WordComplete Properties.
Select any configuration. Open its Properties.
In Options page, “Number of Characters” is 1 by default.
Change it to 2 and click OK.
Now select all the configurations. Open the Properties.
** In Options page, “Number of Characters” now is 0.
Thank you for adding “Complete (Keep Typed Case)” command.
Is it possible to enhance it further:
When the “Match Case” option is “Never and Keep Original Text when Completes”, “Complete (Keep Typed Case)” command reverses the function (i.e. completes with the candidate case).
I think a Reset button is necessary for every page in WordComplete (sub-)Properties for configuration(s) dialog box. So we can see the default settings temporarily.
Clicking “…” button (in Dictionaries page) should open the path according to the (absolute/relative) path in the “Dictionary File” box when valid. (And the file should be selected when the dialog box is open.)
Otherwise it should open the default “Dictionaries” folder.
When open, the default type should be: All Files (*.*)
Currently it opens EmEditor’s current directory (OpenDir).
And the type is always *.txtJuly 28, 2018 at 11:13 am #23563
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.
You must be logged in to reply to this topic.