GnuCash
Contact   Instructions
Bug 797889 - editing amounts in dr / cr behaving oddly
Summary: editing amounts in dr / cr behaving oddly
Status: RESOLVED FIXED
Alias: None
Product: GnuCash
Classification: Unclassified
Component: Register (show other bugs)
Version: 4.1
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: ui
QA Contact: ui
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-31 06:20 EDT by Wm
Modified: 2020-08-07 14:25 EDT (History)
4 users (show)

See Also:


Attachments

Description Wm 2020-07-31 06:20:44 EDT
this wasn't present in 4.0 but is in 4.1 (I like the 4.1 progress in general)
I've no feeling for whether this is OS specific so Win for the moment
it is not stopping me from doing accounts so Normal for the moment

recipe:
enter a tx of, say, 1234.56 (doesn't matter if it is dr or cr)
display is 1,234.56
highlight the 3 type 9
expected result 1,294.56
actual result 1,29.56

I can provide other examples if necessary, if it is happening to you the e.g. above should be clear.

I'm guessing this is the result of something underlying changing rather than something the gnc team did on purpose.

I have had a look but haven't seen this reported in 4.1.  I'm happy for this to be merged.
Comment 1 John Ralls 2020-07-31 18:30:05 EDT
Just another instance of failing to get the cursor handling right after pushing the register's input method handling back to Gtk where it belongs.

Fixed in git, will be in tomorrow's nightly. Thanks for the report.
Comment 2 Wm 2020-08-07 11:27:14 EDT
Will that fix things generally ?  There is another glitch in editing text in the description.  If the nightly builds are safe to play with at the moment I can see if it is still there.
Comment 3 Wm 2020-08-07 11:29:03 EDT
sorry, forgot to say, thank you
Comment 4 John Ralls 2020-08-07 14:25:14 EDT
The nightly builds should be pretty safe, nothing has gone in except bug fixes. If the other glitch also involves deleting or replacing then it's probably the same problem.

Note You need to log in before you can comment on or make changes to this bug.