Reproducible steps: When entering a transaction in the registry, after setting the date, I begin typing the name of the description. After pressing the first letter, a suggestion is shown in the description space which starts with the letter I entered, with the cursor after that letter, and with the rest of the suggestion after the cursor. Expected behavior: The remaining portions of the suggestion should be highlighted. If it is, when I type the second letter, the suggestion should be updated based on that (either the same suggestion, but with the cursor one more character over, or a new suggestion if the second character does not match the original suggestion). In this way, multiple initial characters of the description can be entered at once, and the best suggestion presented based on those. Actual behavior: The remaining portions of the suggestion is not highlighted. Therefore, when the second letter is typed, it is inserted after the first letter of the suggestion and before the rest of the suggestion. With this behavior, a suggestion based on multiple initial characters is not possible just by typing the characters. The remaining part of the field must be manually highlighted before the last character is entered. Example: In the description, I type "I". The description field shows "I|nterest Earned" (where the pipe represents where the cursor is). Nothing is highlighted. I type "n". The description field shows "In|nterest Earned" (again, pipe is cursor) I expect it to show "In|terest Earned" where "terest Earned" is highlighted, so that if I were to type a letter other than "t" I would get a new suggestion. Or if I were to enter a "t", it would advance the cursor and highlight one fewer character. Versions: The behavior was as I described in "expected behavior" in version 2.6.19. It is as described in "actual behavior" in 3.2. I have not used any versions between those two so I do not know when the regression appeared. I have only used GnuCash on a mac. This behavior was seen running on MacOS High Sierra, 10.13.5. Other comments: I think I saw this in the account field as well, but have not tested it enough to determine that it is a bug.
Thanks for reporting this. It has been discussed on the mailing list but it's better to have a bug report for tracking. I've found that there's a work-around as long as you don't need input methods (as you would for typing in many Asian languages): Rename or remove GnuCash.app/Contents/Resources/lib/gtk-3.0/3.0.0/immodules.cache.
*** Bug 796735 has been marked as a duplicate of this bug. ***
Thank you for the suggested workaround. I will try it and report back my results. I do not following the mailing lists, so I was not aware of the discussion there. I hunted down the thread and read it. For anyone else, here is a link to the root message of that thread in the archives: https://lists.gnucash.org/pipermail/gnucash-user/2018-July/077881.html
The workaround did work for me. Thanks.
*** Bug 796748 has been marked as a duplicate of this bug. ***
The same for me. John Ralls workaround solves the issue. Thanks!
A work-around isn't a fix, and this one in particular won't work for users who need the input method.
*** Bug 796752 has been marked as a duplicate of this bug. ***
Yes, this works for me too. Thanks John, and sorry for not noticing the earlier bug reports (I did search, but not as zealously as I ought to have).
*** Bug 796770 has been marked as a duplicate of this bug. ***
*** Bug 796795 has been marked as a duplicate of this bug. ***
*** Bug 796796 has been marked as a duplicate of this bug. ***
John, thanks for the work-around (Comment 2)! I was just about to go back to 3.1.
*** Bug 796803 has been marked as a duplicate of this bug. ***
Thanks, the work-around works for me too. Maybe putting some more keywords in the title of the bug would help eliminate duplicates. I searched for autocomplete and QuickFill, but not auto-complete.
Hi all, this issue is really disturbing, as I used it so much in the past, and the workaround won't be the solution to me. I was wondering if this was part of a new feature from 3.2 (cause it didn't work the same in 2.6), or not? If it is, is it possible to re-integrate the previous feature, which was working perfectly at that time, until the new one is fixed? Thanks in advance
It's not a change in the feature, it's a change in the input-method handling between Gtk2 and Gtk3. It's not even clear at this point that the problem is actually with GnuCash: Since it affects only MacOS it's entirely possible that it's a bug in imquartz.c, part of Gtk+.
Hi, the immodules.cache rename workaround worked for me too. (I was kind of surprised by this regression.)
As were we all. ;-) Anyway, I've fixed the problem for 3.3.
*** Bug 796846 has been marked as a duplicate of this bug. ***
The workaround fixed my problem too. Thank you
*** Bug 796864 has been marked as a duplicate of this bug. ***
