Gnucash 4.0, Windows 10 I can reproduce this issue in multiple different *.gnucash files and even after closing and reopening the app. -- Ever since upgrading to GnuCash 4, I've noticed one difference in behaviour which is somewhat irritating for my workflow: 1. Open an account from the account list. 2. Click on any existing transaction with the intent to alter it (e.g. duplicate a transaction to a new date and then focus your typing bar into the 'Deposit' field so that you can change the amount the transaction is for). 3. Press Ctrl+A to select the entire value (so you can type to replace it). Expected: Value is selected Actual: Value is selected and windows plays whichever sound is associated with 'Default Beep' in the sound scheme ('Windows Background.wav'). This sound is associated with many events, but I can change Default Beep to another sound and then a different sound will play when I perform these steps. After the field has been focussed, any subsequent Ctrl+A presses are silent, even if you use the cursor to click within the field (to unselect all and insert a typing bar somewhere in the field) and press Ctrl+A again. However, if you change field (e.g. from Deposit to Date) then the next Ctrl+A will make the chiming noise again.
If I click once inside any of the register fields, the typing focus is always placed before the first character in the field (no matter where I clicked). E.g. if I click on the decimal point in a Deposit of "100.07", the the bar will be entered as "|100.07". When the cursor is in this position, the chiming noise occurs on a Ctrl+A press. If I left-click a second time first, the typing bar moves to where I clicked (e.g. "100|.17") and at that point Windows will NOT chime if I press Ctrl+A.
Thanks for the detailed troubleshooting. This is fixed for 4.1 and will be in tomorrow's nightly.
I installed maint/gnucash-4.0-2020-07-20-git-4.0-101-g8ef370ce8+.setup.exe and attempted to reproduce the problem. - Focussing a field now enters the typing bar in the correct position for where I clicked. - Pressing ctrl+A in such a field does not chime, unless the field is empty (in which case I accept that ctrl+A is not a valid thing to press). Verified fixed.
It will still chime if you put the cursor at the beginning of the string. That behavior is hard-coded into GtkEntry.
