On May 13, 2013, at 9:32 PM, David Carlson <carlson...@sbcglobal.net> wrote: >> > I am pretty sure that all the barchart reports are broken in the Windows > release 2.5.1. I am not doing very much testing because 2.5.1 also > crashes when editing scheduled transactions, which I do nearly every day > in my real data, so I must go back quickly to 2.4.13. I do not have any > problems with memory usage when 2.4.13 is running, so I suspect that > 2.5.1 may also have a memory leak. Granted, I am not properly equipped > to test that hypothesis. > > I chose the thread title specifically to break away from the Time for > 2.5.1 thread. I suppose I should have either called it a 2.5.2 request > or Another 2.5.1 bug. I do think it should be tested in Windows by a > developer before releasing 2.5.2. It is not that hard to open one or > two reports in a test file. > > Actually, I am running Ubuntu 12.04 part time on my laptop. > Unfortunately, I am also using some programs that have no Linux > counterpart, so I am not considering a total conversion. >
Sounds like "Another 2.5.1 bug" or even "More 2.5.1 bugs" would have been the best choice, unfortunately. I'll try to find time to give trunk a spin in Win7 later this week. Aside from the GtkTreeView register not that much has changed in Gnucash itself, so perhaps we've been a little too aggressive in updating the dependencies for the Win32 package. Regards, John Ralls _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
