Viewing 10 posts - 16 through 25 (of 25 total)
  • Author
    Posts
  • #23336

    LTT
    Participant

    I see. Thank you for the change.

    —————
    Issue C:
    “Never and Keep Original Text when Completes” is used.
    Then when I really want to choose the candidate string, what should I do?
    For example,
    Type “unes”.
    The list gives “UNESCO”.
    How do I choose it?

    —————
    Issue D:
    2 empty lines. (The 2nd is EOF.)
    Type “aa” in the 1st line. The red wiggly line shows.
    Move cursor to the 2nd line.
    ** The red wiggly line vanished.

    —————
    Issue 4-2-2:
    Note the 2 lines marked with **:

    WordComplete properties:
    “Options” page:
    Number of Characters: 5.

    Type “strin”.
    The candidate list shows.

    Press Backspace key.
    Now it’s “stri”.
    The list closed.

    Show the list manually.
    Press Backspace key.
    Now it’s “str”.
    The list persists. Nice.

    Press Backspace key.
    Now it’s “st”.
    ** The list closed again.

    Show the list manually again.
    Type “r”.
    Now it’s “str”.
    ** The list closed again.

    In sum, I think the manually shown list should persist till the user closes it.

    #23339

    Yutaka Emura
    Keymaster

    As for Issue C, in this case, you will have to Backspace to delete your text “unes” and type “UNES”. That is the purpose of this “Never and Keep Original Text when Completes” option.

    As for Issue 3, we reproduced the issue, and it will be fixed on the next beta.

    As for Issue 4-2-2, yes, we fixed this issue.

    Thanks,

    #23351

    LTT
    Participant

    Issue C:
    Is it possible to implement that an operation (e.g. Ctrl+Enter) can override the rule to make an exception for once?

    #23384

    LTT
    Participant

    Issue D is not fixed yet.

    Issue E:
    WordComplete needs an option for words in UserDic.bin.

    Issue F:
    The default en_US.dic is CP-1252. Some characters could be displayed incorrectly in the candidate list on different OS’s, e.g.:
    Ångström
    cliché
    clientèle
    I converted en_US.dic to UTF-16LE+s (since UserDic.bin is). Seems work well for WordComplete, but not for CheckSpelling.

    Issue G:
    CheckSpelling can recognize the word between 2 non-Latin characters (with no spaces). But WordComplete can not.

    Issue H:
    Type “doc”. The candidate list shows.
    “docc”. The list hides.
    Press Backspace.
    I think the list should show again.

    Issue I:
    When “QAZ” is deleted in the document, it will be cleared from the candidates.
    But when “Include All Documents in Group” option is used, and after I closed the other documents in the group, the words from them are still in the candidates, till I detach the tab.

    —————
    Issue J:
    “Never and Keep Original Text when Completes” is used.
    When both “qaz” and “QAZ” exist in the document, the candidate list displays only the first one (according to the order in the document).
    Is this as expected?

    The description for “Never” in CHM is not quite clear for me:
    > For instance, suppose ABC and abc are found in the current document (or a dictionary file).
    > If Never is selected, either ABC or abc can be used as a candidate, and typing either A or a displays either ABC or abc.

    I think “the first one loaded” should be stressed, rather than use “either”.

    —————
    Suggestion 3:
    Hope the candidate list can be cycled to the bottom/top by pressing Up/Down key.
    Or make Home/End key also available in the candidate list, since PageUp/PageDown key can be used.

    #23399

    Yutaka Emura
    Keymaster

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

    #23401

    Yutaka Emura
    Keymaster

    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!

    #23435

    LTT
    Participant

    > Issue D:
    When DirectWrite is off.

    > Issue E:
    CheckSpelling saves the user-added words in UserDic.bin.
    But WordComplete doesn’t read this file.

    > Issue G:
    orangオレンジorangオレンジorang
    orang橘orang橘orang
    orang오렌지orang오렌지orang
    You can see the red wiggly line on each “orang”.
    Set the text cursor within each “orang” and compare the candidate list.
    WordComplete works as expected only in the “オレンジ” line. Apparently you’ve optimized it for kanas.

    Issue ZZ:
    Hope these items in Spelling Suggestion menu will also have the accelerator keys (underlined letters):
    Add to Dictionary
    Ignore All

    #23442

    Yutaka Emura
    Keymaster

    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.

    #23445

    LTT
    Participant

    > Issue D:
    + The wrapping mode should be other than “No Wrap”.

    > Issue E:
    I think this is necessary. But let it be an option.
    UserDic.bin is just like the user-defined strings in Highlight (1).

    #23447

    Yutaka Emura
    Keymaster

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

Viewing 10 posts - 16 through 25 (of 25 total)

You must be logged in to reply to this topic.