Bug 249215 - Ledger View has blank area
Summary: Ledger View has blank area
Status: RESOLVED NOT A BUG
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR minor
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-27 13:18 UTC by allan
Modified: 2010-08-29 17:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Difference of "Today" marker between 1.0 and 4.5 (6.37 KB, image/png)
2010-08-28 12:36 UTC, Thomas Baumgart
Details

Note You need to log in before you can comment on or make changes to this bug.
Description allan 2010-08-27 13:18:35 UTC
Version:           unspecified (using KDE 4.4.4) 
OS:                Linux

I've been noticing this for several days.  In Ledger view for my bank current account, There is a blank area between two transactions or, more accurately, added on at the bottom of a transaction, perhaps four pixels in height.  I first noticed it after a reconciliation, but suspect this is irrelevant, as I couldn't reproduce it that way.

It doesn't clear with screen resizing, or closing and reopening the file, or selecting a different account and then returning.  Duplicating then deleting the apparently affected item doesn't help as the new item now has the problem.

After editing it, etc. I eventually realised it resembled the group header separator, which I do not use, and it appears as a pseudo-separator following the current date.  (I had setup to show scheduled items in advance, but changing those settings still leaves existing entered future items displayed.)

I've just now reproduced the problem on an earlier file.  With zero days set for entering or displaying future scheduled items, I entered a scheduled item for today, which appeared OK.  I then changed the number of days to preview, to 7, and the previously OK latest entered item now has a blank separator between it and the first scheduled item.

Reproducible: Always

Steps to Reproduce:
I've just now reproduced the problem on an earlier file.  With zero days set for entering or displaying future scheduled items, I entered a scheduled item for today, which appeared OK.  I then changed the number of days to preview, to 7, and the previously OK latest entered item now has a blank separator between it and the first scheduled item.

Actual Results:  
see above

Expected Results:  
No such blank area should appear.

Version 3.98.2-svn1164040
Comment 1 Thomas Baumgart 2010-08-28 12:36:24 UTC
Created attachment 51045 [details]
Difference of "Today" marker between 1.0 and 4.5

The area is there by design but looks different between 1.0 and 4.5
Comment 2 allan 2010-08-28 13:20:29 UTC
(In reply to comment #1)
> Created an attachment (id=51045) [details]
> Difference of "Today" marker between 1.0 and 4.5
> 
> The area is there by design but looks different between 1.0 and 4.5

Oh, OK.  Is the 'by design' recent, as I've only recently become aware of it.  Perhaps the lack of the horizontal line below make it look a bit unfinished in 4.5?

I shall stop trying to get rid of it, anyway!
Comment 3 Thomas Baumgart 2010-08-28 14:39:54 UTC
The 'by design' is around since the pre 0.9 days. So we talk about a couple of years (http://kmymoney2.cvs.sourceforge.net/viewvc/kmymoney2/kmymoney2/kmymoney2/widgets/register.cpp?r1=1.37&r2=1.38& introduced it on line http://kmymoney2.cvs.sourceforge.net/viewvc/kmymoney2/kmymoney2/kmymoney2/widgets/register.cpp?annotate=1.38#l1925 which I added in March 2007)
Comment 4 allan 2010-08-28 15:00:56 UTC
(In reply to comment #3)
> The 'by design' is around since the pre 0.9 days. So we talk about a couple of
> years
> (http://kmymoney2.cvs.sourceforge.net/viewvc/kmymoney2/kmymoney2/kmymoney2/widgets/register.cpp?r1=1.37&r2=1.38&
> introduced it on line
> http://kmymoney2.cvs.sourceforge.net/viewvc/kmymoney2/kmymoney2/kmymoney2/widgets/register.cpp?annotate=1.38#l1925
> which I added in March 2007)

Yes, I can believe it's been around  for a while under 1.xx, etc., and, as it appears there, it's pretty obvious that it's by design.  Presumably, it's been in 3.xx since I started using it, so I have to put my not observing it until now, down to my new lenses.

Thanks.