On Aug 11, 2013, at 5:50 AM, David Carlson <[email protected]> wrote:
> On 8/10/2013 1:34 PM, John Ralls wrote: >> I guess I should have done this much sooner, but I tried using Register2. >> Some issues: >> >> * The number field is reproduced when copying a memorized transaction if >> it's left blank before tabbing out of the description field. >> >> * Return doesn't commit the transaction and move to a new empty one, it >> toggles the edit state on the current field. Tabbing off the end of the >> transaction, rather than opening a new empty transaction, takes one to the >> first entry in the account. Arrow-down doesn't do anything. I was able to >> commit the transaction by arrowing up, which created a new empty transaction >> that I could arrow down to, but of course the cursor isn't in the date >> column where I need to start, it's in whatever column I was last in in the >> previous transaction. I have to back-tab to the date field to start entering >> the next transaction. >> >> * Because Enter/Return doesn't move the cursor, the "Enter moves to blank >> transaction" preference has no effect. >> >> * The new blank transaction shows today's date rather than the last date >> used. >> >> * Delete Split doesn't work on a new, unsaved transaction [1]. Attempting to >> empty the transfer account on a split crashed Gnucash [2]. >> >> * Deleting the value in a split's deposit or withdrawal column fails: the >> value is restored when one tabs out. One must enter 0 which is removed when >> one tabs out. It's not necessarily a bug, but it's different from Register-1 >> and we need to be aware of it. >> >> * One must click on a field or press Enter when starting to edit a new >> transaction, otherwise a search box opens when one begins typing. >> >> * Completion of the rest of a transaction after autocompletion fails >> intermittently. >> >> All of these problems occur on both OSX with Gtk-2.24.20 and Fedora-18 with >> Gtk-2.24.16. >> >> Regards, >> John Ralls >> >> [1] https://bugzilla.gnome.org/show_bug.cgi?id=705762 >> [2] https://bugzilla.gnome.org/show_bug.cgi?id=705763 >> _______________________________________________ >> gnucash-devel mailing list >> [email protected] >> https://lists.gnucash.org/mailman/listinfo/gnucash-devel >> > I also noticed, but may have failed to report that in a windows 7 64 bit > environment the enter button in the menubar does commit the transaction > edit while the keyboard enter/return keys do not commit the transaction > edit as you have stated herein. That is both in scheduled transaction > edits as I did report in > <https://bugzilla.gnome.org/show_bug.cgi?id=702880#c10>, and in normal > transaction edits. Just tested that -- I used the Transaction>Enter menu item, but they both fire the same action -- it does commit the transaction. It also moves to the first transaction in the account, just like tabbing out does. Regards, John Ralls _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
