After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 344455 - Resume autocompletion upon backspace
Resume autocompletion upon backspace
Status: RESOLVED OBSOLETE
Product: GnuCash
Classification: Other
Component: Register
unspecified
Other All
: Normal enhancement
: ---
Assigned To: David Hampton
Chris Shoemaker
Depends on:
Blocks:
 
 
Reported: 2006-06-10 02:48 UTC by jlquinn
Modified: 2018-06-29 21:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description jlquinn 2006-06-10 02:48:54 UTC
While typing in autocomplete in either description or destination account, if you accidentally break out of autocomplete by typing e.g. backspace, it's a nuisance to resume.  You need to back up a char and type the next char again.  Sometimes you forget the right thing to type because your fingers are on autopilot.

It would be nice for autocomplete to resume without extra steps.

Other information:
Comment 1 Chris Shoemaker 2006-06-13 19:03:15 UTC
Autocompletion does automatically resume if you type a character that continues an existing string.  I interpret this RFE as requesting that autocompletion also resume when backspace results in a string that is a prefix of an existing string.
Comment 2 jlquinn 2006-07-24 04:05:33 UTC
Yes, that's right.  I should have been more specific.

I bumped the version to 2.0.0, since that's current and this is still relevant there.
Comment 3 David Gianforte 2013-05-06 03:09:58 UTC
Due to the register rewrite in 2.5 this is no longer an issue. In 2.5 auto-complete is implemented with a drop-down instead of in-place. The drop-down will pop back up if backspace is used after typing a description which has no auto-complete options.

(Tested on trunk, rev 22949M)
Comment 4 John Ralls 2018-06-29 21:07:41 UTC
GnuCash bug tracking has moved to a new Bugzilla host. The new URL for this bug is https://bugs.gnucash.org/show_bug.cgi?id=344455. Please continue processing the bug there and please update any external references or bookmarks.