Comments Regarding New 2.5.1 Register

[David Carlson]

On 5/29/2013 3:10 AM, Geert Janssens wrote:
> On Tuesday 28 May 2013 14:59:04 John Ralls wrote:
>> On May 28, 2013, at 2:53 PM, David T. <sunfish62 at yahoo.com> wrote:
>>> I was trying out 2.5.1 on my Mac (Mountain Lion) and was prepared to
>>> report that it was crashing when I tried closing and then re-opening my
>>> main checking account register. Every time I did, I got a beach
>>> ball/hourglass, and had to force quit the application.
>>>
>>> I thought the problem had to do with the fact that my Accounts were set to
>>> use tab color designators (which are not displaying, BTW). But loading a
>>> couple of other colored-tab accounts worked. That was when I remembered
>>> the thread regarding SLOW loading. Sure enough, when I tried again to
>>> open my account, and this time waited over two minutes (!!), my account
>>> opened in the new register. So consider this another voice raised for
>>> needing this to work faster. I truly thought I had crashed the software!
>>>
>>> Having loaded the new register, I see what folks have been saying about
>>> the screen flag for future transactions. Personally I think it does not
>>> work. Users looking at the register see it naturally as a flow of time
>>> from the top of the screen to the bottom, and having the blue horizontal
>>> line is highly effective at indicating a transition from past to future.
>>> Having a vertical bar might work, but is nowhere near as obvious.
>>> Furthermore, embedding this bar two thirds of the way off to the right
>>> makes no sense to me at all. At the very least, it should default to the
>>> left-most position. I was able to move it to the left--by moving all the
>>> other fields to the right, which was quite cumbersome. I think the old
>>> way would be clearer. Or perhaps the entire transaction could have a
>>> different background color if its in the future?
>>>
>>> I'll note that the correct heading is "Withdrawal", not "Withdrawl."
>>>
>>> Finally, the click-sortable columns is really neat, but I would like to
>>> see it possible to have a "Click to restore the default sort order"
>>> button. I did not see any way to return to this sort order once I had
>>> clicked on a heading. This is especially frustrating since the tendency
>>> to re-sort a column is great when one is simply trying to resize the
>>> columns.
>> Thanks for the report. I hope you mean 2.5.2, released today, rather than
>> 2.5.1 from 3 weeks ago.
>>
>> Regards,
>> John Ralls
>>
>>
> It looks like David really tested 2.5.1: the typing error in "Withdrawal" was part of that version 
> and fixed in 2.5.2.
>
> David: 2.5.2 has already some speed improvements, though there is plenty of room for more. 
> Can you evaluate that version and update your feedback based on it ?
>
> Thanks,
>
> Geert
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>
I am the other David- David Carlson.
Last night I installed 2.5.2 windows build on Windows 7 64 bit.  If you
look at the IRC channel, I started documenting 3 errors when opening a file.
Please do not shoot the messenger.
David C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xDC7C8BF3.asc
Type: application/pgp-keys
Size: 1729 bytes
Desc: not available
URL: <http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20130529/5327fb04/attachment.bin>