Thanks for the update status about issues in 3.0 and also about the registry2. However, can someone tell me what that registry does and what problems people are seeing? I've built 2.6.21 and it seems to run without errors. After reading the note and seeing the changes from Len I'm wondering if the errors maybe in background or worst database corruptions? Cheers

The --enable-register2 has been removed in the 2.6.21 upgrade (mistake on my part), and the gnucash3 program and doc scripts will hit with the next update (had to wait for an update to gtest). As others (including the developers) have said, unless you're feeling adventurous, you may want to stick with the 2.6 release.

My understanding is that the an account registry is a window on the transactions for that particular account. The problem I saw was that if there were hundreds of transactions in an account you would only see a subset of them between a certain date range irrespective of how much scrolling up and down was down within the registry. Bit like if a date range filter had been applied.

To see transactions outside of that date range one has to click on either the first or last transaction in the registry. If one wanted to see the earliest dated transaction in an account and there were hundreds of transactions that is a lot of clicking and scrolling to get back to the start. Takes a long time.

I didn't detect any corruption, everything reconciled back to the bank statements.

IMHO if the developers are intending that the registry is going to operate in the way that I described above it will lead to confusion and will increase the users workload in a significant way.

Thanks Lenard for the fix and update.

Update: gnucash-3.1 has been released.

The bug related to the environment file has been fixed, sort of; gnucash will now look for the file where it got installed in /etc/opt/... So the fix above for copying the environment file is no longer needed.

Also it turns out that the googletest/gmock source tree does not need to be installed as I showed above - it just needs to be available when Gnucash is built. So the gnucash CMAKE command changes to something like this, assuming you unpacked and built googletest under the same parent directory, and the source is still there:

There are a number of bug fixes in gnucash-3.1 and you might seriously consider upgrading from 2.6.x to this version.

Update: The latest version is GnuCash-3.2. It works well on Slackware 14.2, except for the same problem I've had with all 3.x: messed up text in the Summary Bar on the accounts tab.

I got around that problem by installing Gtk+3-3.20.10 (separate from Slackware-14.2's Gtk+3-3.18.9) and having GnuCash use the newer Gtk+3 library instead. Something is wrong in Gtk+3-3.18.9 that triggers this issue. The problem should fix itself with the next Slackware release, as Slackware-current now has Gtk+3-3.22.30. (Unlike 3.20.x, 3.22.x would require a newer GLib, which is why I'm using 3.20.10.)

A word of caution: Interactive performance of my GnuCash-3.x is a lot worse than GnuCash-2.x on the same hardware. I'm talking about time to open a new window, or even to register a click or double-click. It's usable on my old PC, but not nearly as snappy as 2.x was.

1 members found this post helpful.