Bug 273205 - ledger screen weird behaviour
Summary: ledger screen weird behaviour
Status: RESOLVED FIXED
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: SVN
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-13 16:07 UTC by allan
Modified: 2012-04-05 21:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description allan 2011-05-13 16:07:57 UTC
Version:           SVN trunk (using KDE 4.6.0) 
OS:                Linux



Reproducible: Didn't try

Steps to Reproduce:
1) Open a cheque account via ledger view.
2) The last entry shows highlighted as though selected.
3) Right click on that entry.
4) 'Edit' is not enabled but 'New' is.
5) Now right click below last entry.
6) As for 4) above.
7) Select 'New'.
8) Last entry is opened for editing, but 'Cancel' is not enabled.
9) Select another transaction.
10) Click 'yes' to cancel editing.
11) The transaction still appears open for editing but 'Cancel' now available.
12) Notice that preceding transaction is overlayed by current one.
13) Click 'Cancel'.
14) Entries still corrupted.
15) Select another account and then go back.
16) Sanity returns.

Actual Results:  
As above.

Expected Results:  
Should work as for selecting 'New' at bottom of view.

Have seen this before but haven't found entry (except mentioned in passing during recent crash).
Comment 1 allan 2011-05-13 18:18:40 UTC
I mentioned this in Bug 270752 (referred to above), although in fact that wasn't a crash.
Comment 2 allan 2011-05-13 18:26:47 UTC
I mentioned this in Bug 270752 (referred to above), although in fact that wasn't a crash.

See also Bug 269559.
Comment 3 allan 2011-05-13 19:21:17 UTC
Also, bug 272974.
Comment 4 Thomas Baumgart 2011-05-14 07:26:05 UTC
I was able to duplicate the problem here, at least partially. The 'edit' action not being available is probably caused by a closed account that the selected transaction refers to.

The transaction editor screwing up on the 'new' action is the second part. I was only able to duplicate the problem by using either the context menu as the OP does. Pressing the 'New' button or using the 'Transaction/New' menu entry or pressing 'Ctrl+Ins' as the shortcut I don't see it happen. That is strange.
Comment 5 Cristian Oneț 2011-05-21 22:11:41 UTC
I think that this is the duplicate of the fixed bug. The symptoms are the same, after the register is loaded the selection is void thus only 'New' is enabled.

*** This bug has been marked as a duplicate of bug 262095 ***
Comment 6 allan 2011-08-29 23:30:15 UTC
(In reply to comment #5)
> I think that this is the duplicate of the fixed bug. The symptoms are the same,
> after the register is loaded the selection is void thus only 'New' is enabled.
> 
> *** This bug has been marked as a duplicate of bug 262095 ***

I've just seen this, or something very similar, again, this time in an investment.

Wanting to add a new transaction similar to the last entry in the ledger, so duplicated it.  The new transaction was correctly created, and I edited it, changing the date to be a month later.  Having accepted that edit, this transaction, now the last one, was showing as selected but Edit was not available, either in the context or at the ledger foot.  Neither a single nor a double click changed that.

A second double click brought it to normal.  I was able to reproduce this a few times, but not after the double double click. I also saw it a few days ago.
Comment 7 allan 2011-08-29 23:42:00 UTC
Just to clarify, here's the revised last paragraph.

I was able to reproduce this a few times.  A second double click brought it to normal. I was NOT able to reproduce it after the double double click. I also saw it a few days ago.
Comment 8 allan 2012-04-05 21:32:42 UTC
I can't now reproduce this so will re-close.