[Kmymoney-devel] [kmymoney4] [Bug 249844] wrong memo field after duplicating and editing transaction

2013-05-13 Thread Mark Blakeney
https://bugs.kde.org/show_bug.cgi?id=249844

Mark Blakeney  changed:

   What|Removed |Added

 CC||mark.blakeney@bullet-system
   ||s.net

--- Comment #11 from Mark Blakeney  ---
I raised bug 319807 today but just found this bug which is closely related.
Adding a linkage between them.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel


[Kmymoney-devel] [kmymoney4] [Bug 319807] New transaction from memorised carries old memo

2013-05-13 Thread Mark Blakeney
https://bugs.kde.org/show_bug.cgi?id=319807

--- Comment #1 from Mark Blakeney  ---
OK, have been hunting in detail through the KDE KMM bug tracker and have found
bug 249844 from 2010 which is very closely related. Plenty of discussion there
where some developers claim this issue is "by design". Here, that argument is
less appropriate because a memorised transaction bears less relationship to the
new transaction. Either way, I disagree strongly that this is desirable
functionality. The original main split memo was created from the main
transaction memo, so it should also be for a new transaction.

My words are not clear from 1st description here, I mean't to say that I give a
KMM report to my accountant but it is extremely confusing because she sees all
old memo descriptions on the main amount splits, unless I remember to go
through an entire year of transactions and manually update them by hand before
I produce the report. What a pain.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel


[Kmymoney-devel] [kmymoney4] [Bug 319807] New: New transaction from memorised carries old memo

2013-05-13 Thread Mark Blakeney
https://bugs.kde.org/show_bug.cgi?id=319807

Bug ID: 319807
   Summary: New transaction from memorised carries old memo
Classification: Unclassified
   Product: kmymoney4
   Version: 4.6.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-devel@kde.org
  Reporter: mark.blake...@bullet-systems.net

I am using automatic VAT/GST splits on my transactions. If I start entering a
payee and then select a transaction from the memorised list then enter a new
memo on that new transaction then the transaction will always only update the
memo on the main transaction. It will keep the first ever entered memo on the
split for the main amount.

This is a really unfortunate bug. Means I give a report to my account and the
memo descriptions are all wrong (because they are very old and don't correspond
to the actual transaction). This bug has existed for a while but I have not got
around to reporting it because I assumed it would get fixed eventually. Seems
it has not been noticed by many.

Reproducible: Always

Steps to Reproduce:
1. As above
2.
3.
Actual Results:  
Expect new memo on the main split.

Expected Results:  
Old memo still on split.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel


[Kmymoney-devel] [kmymoney4] [Bug 319801] program looses track of check number if check number sequence is interrupted.

2013-05-13 Thread allan
https://bugs.kde.org/show_bug.cgi?id=319801

--- Comment #1 from allan  ---
On Mon, 13 May 2013 20:18:17 +
 wrote:

> https://bugs.kde.org/show_bug.cgi?id=319801
> 
> Bug ID: 319801
>Summary: program looses track of check number if check
> number sequence is interrupted.
> Classification: Unclassified
>Product: kmymoney4
>Version: 4.6.3
>   Platform: Other
> OS: Linux
> Status: UNCONFIRMED
>   Severity: normal
>   Priority: NOR
>  Component: general
>   Assignee: kmymoney-devel@kde.org
>   Reporter: jr09...@gmail.com
> 
> If I make a non-numeric note in the ledger number field, KMyMoney
> looses track of the next check number. It always reverts to number 1
> in the next transaction.
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1.enter several checking transactions, using number (for example)
> 1000, 1001, 1002, 1003, 1004 - then:
> 2.enter a debit transaction and enter EFT in the number box, then:
> 3.enter another transaction - KMyMoney will offer the check number 1
> instead of 1005
> 
> 
> 
> Many transactions do not have a number, such as EFT (electronic fund
> transfer) and ATM (automated teller machine). To help keep track of
> these transactions, I enter EFT or ATM in the number box in the
> ledger window. If I enter several consecutive checks , KMyMoney
> offers the correct check number in each new transaction. If I enter
> EFT or ATM, the next transaction that follows will offer the number 1
> in the number box, not the correct check number. FYI: PCLinuxOS 2013
> 64  is my operating system. I hope I have explained this clearly. I
> am new to Linux and KMyMoney.
> 

Another user reported this same problem yesterday (see Feature
request). I see you use just integers for your numbers, yes?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel


Re: [Kmymoney-devel] [kmymoney4] [Bug 319801] New: program looses track of check number if check number sequence is interrupted.

2013-05-13 Thread aga
On Mon, 13 May 2013 20:18:17 +
 wrote:

> https://bugs.kde.org/show_bug.cgi?id=319801
> 
> Bug ID: 319801
>Summary: program looses track of check number if check
> number sequence is interrupted.
> Classification: Unclassified
>Product: kmymoney4
>Version: 4.6.3
>   Platform: Other
> OS: Linux
> Status: UNCONFIRMED
>   Severity: normal
>   Priority: NOR
>  Component: general
>   Assignee: kmymoney-devel@kde.org
>   Reporter: jr09...@gmail.com
> 
> If I make a non-numeric note in the ledger number field, KMyMoney
> looses track of the next check number. It always reverts to number 1
> in the next transaction.
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1.enter several checking transactions, using number (for example)
> 1000, 1001, 1002, 1003, 1004 - then:
> 2.enter a debit transaction and enter EFT in the number box, then:
> 3.enter another transaction - KMyMoney will offer the check number 1
> instead of 1005
> 
> 
> 
> Many transactions do not have a number, such as EFT (electronic fund
> transfer) and ATM (automated teller machine). To help keep track of
> these transactions, I enter EFT or ATM in the number box in the
> ledger window. If I enter several consecutive checks , KMyMoney
> offers the correct check number in each new transaction. If I enter
> EFT or ATM, the next transaction that follows will offer the number 1
> in the number box, not the correct check number. FYI: PCLinuxOS 2013
> 64  is my operating system. I hope I have explained this clearly. I
> am new to Linux and KMyMoney.
> 

Another user reported this same problem yesterday (see Feature
request). I see you use just integers for your numbers, yes?


___
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel


Re: [Kmymoney-devel] Onlinebanking

2013-05-13 Thread Martin Preuss
Hi,

I'm using the same settings as Thomas but for the NetBank (which uses
the server of the Sparda Bank). And those settings work for me.


Regards
Martin


Am 13.05.2013 08:54, schrieb Thomas Baumgart:
> Hallo Herbert,
> 
> wir sprechen hier in der Regel Englisch.  Sollte das ein Problem
> sein, lass' es uns wissen.
> 
> 
> Please see my settings for Sparda Hessen in the attached
> screenshot. Hope that helps.
> 
> Cheers
> 
> Thomas
> 
> On Monday 13 May 2013 08:28:58 Herbert Weinberger wrote:
> 
>> Sehr geehrte Damen und Herren,
>> 
>> vor einigen Tagen habe ich Kmymoney eingerichtet.
>> 
>> Allerdings funktioniert das Einrichten der Konten (unter
>> AqBanking) nicht mit der Sparda Bank München (BLZ 70090500),
>> während die HypoVereinsbank (BLZ 70020270) einwandfrei
>> funktioniert.
>> 
>> Woran kann dies liegen?
>> 
>> Auf einem Windows PC funktioniert auch die Sparda Bank.
>> 
>> Vielleicht können Sie mir helfen.
>> 
>> Vielen Dank!
>> 
>> Mit freundlichem Gruß Herbert Weinberger Ettenhoferstr. 4 81375
>> München herbert-weinber...@kabelmail.de
>> 
>> ___ KMyMoney-devel
>> mailing list KMyMoney-devel@kde.org 
>> https://mail.kde.org/mailman/listinfo/kmymoney-devel
>> 
>> 
>> ___ KMyMoney-devel
>> mailing list KMyMoney-devel@kde.org 
>> https://mail.kde.org/mailman/listinfo/kmymoney-devel


-- 
"Things are only impossible until they're not"

AqBanking - http://www.aqbanking.de/
___
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel


[Kmymoney-devel] [kmymoney4] [Bug 282240] Split Transaction

2013-05-13 Thread Arnold Metselaar
https://bugs.kde.org/show_bug.cgi?id=282240

--- Comment #4 from Arnold Metselaar  ---
Created attachment 79875
  --> https://bugs.kde.org/attachment.cgi?id=79875&action=edit
New crash information added by DrKonqi

kmymoney (4.6.2) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.2

- What I was doing when the application crashed:

I had just entered the second component of a transaction in the split
transaction window and was trying to get back to the main window.

-- Backtrace (Reduced):
#7  0x7f6518c7b845 in QStyleSheetStyle::event (this=0x72ec640,
e=0x7fff87e72820) at styles/qstylesheetstyle.cpp:5798
#8  0x7f651895e70c in QApplicationPrivate::notify_helper
(this=this@entry=0x2b42b30, receiver=receiver@entry=0x72ec640,
e=e@entry=0x7fff87e72820) at kernel/qapplication.cpp:4556
#9  0x7f6518962b8a in QApplication::notify (this=0x2b34900,
receiver=0x72ec640, e=0x7fff87e72820) at kernel/qapplication.cpp:4417
#10 0x7f651be5c886 in KApplication::notify (this=0x2b34900,
receiver=0x72ec640, event=0x7fff87e72820) at
../../kdeui/kernel/kapplication.cpp:311
#11 0x7f6519831b5e in QCoreApplication::notifyInternal (this=0x2b34900,
receiver=0x72ec640, event=0x7fff87e72820) at kernel/qcoreapplication.cpp:915

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel


[Kmymoney-devel] [kmymoney4] [Bug 319801] New: program looses track of check number if check number sequence is interrupted.

2013-05-13 Thread jr09877
https://bugs.kde.org/show_bug.cgi?id=319801

Bug ID: 319801
   Summary: program looses track of check number if check number
sequence is interrupted.
Classification: Unclassified
   Product: kmymoney4
   Version: 4.6.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-devel@kde.org
  Reporter: jr09...@gmail.com

If I make a non-numeric note in the ledger number field, KMyMoney looses track
of the next check number. It always reverts to number 1 in the next
transaction.

Reproducible: Always

Steps to Reproduce:
1.enter several checking transactions, using number (for example) 1000, 1001,
1002, 1003, 1004 - then:
2.enter a debit transaction and enter EFT in the number box, then:
3.enter another transaction - KMyMoney will offer the check number 1 instead of
1005



Many transactions do not have a number, such as EFT (electronic fund transfer)
and ATM (automated teller machine). To help keep track of these transactions, I
enter EFT or ATM in the number box in the ledger window. If I enter several
consecutive checks , KMyMoney offers the correct check number in each new
transaction. If I enter EFT or ATM, the next transaction that follows will
offer the number 1 in the number box, not the correct check number.
FYI: PCLinuxOS 2013 64  is my operating system. I hope I have explained this
clearly. I am new to Linux and KMyMoney.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel


Re: [Kmymoney-devel] Review Request 110212: Add Merge Payee Option

2013-05-13 Thread Felipe Tonello


> On May 3, 2013, 11:53 a.m., Thomas Baumgart wrote:
> > I wonder, why we need a merge payee feature if the delete payee feature has 
> > basically the same functionality. Maybe, you can provide some insights why 
> > you developed this patch in the first place. Or am I missing something 
> > completely here?
> 
> Felipe Tonello wrote:
> That's true, but for the user stand point of view delete to merge doesn't 
> make sense.
> I added this feature because it is useful for me, perhaps for other users 
> as well. Sometimes I have to merge Payees because I wrote them wrong or 
> because they are the same and I didn't know.
> 
> Maybe we can just change delete to delete/merge. But still, for in terms 
> of UX I prefer having different buttons for each functionality.
> 
> Thomas Baumgart wrote:
> Agreed, but can we share the code of both somehow? After all, we have a 
> list of payees that need to be deleted and the transactions referenced by 
> them to be changed to a single payee. The UI might be different, but the 
> works are the same, right? I think it would definitely a plus to have a 
> single place to maintain the logic instead of two. What do you think? (Just 
> saw that you mentioned that yourself in the FIXME section). Would a 
> MyMoneyFile::mergeAndDeletePayees(MyMoneyPayee, QList) be of 
> help?

Yes, I agree.
I will try to work this out and send another commit request. :)


- Felipe


---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/110212/#review31936
---


On April 27, 2013, 3:20 a.m., Felipe Tonello wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/110212/
> ---
> 
> (Updated April 27, 2013, 3:20 a.m.)
> 
> 
> Review request for KMymoney.
> 
> 
> Description
> ---
> 
> Patch 1: Implements the actual merge operation.
> 
> Patches 2 and 3: Implements KAction and context menu option[2] and a button in
> payees view[3].
> 
> Patch 4: This patch might be controversial because I believe the functionality
> provided by this patch was not implemented because of some reason that it's
> not documented.
> 
> TODO: improve user experience (UX) by:
>   - Use a dialog similar to the KPayeeReassignDlg. Probably just making it 
> more generic.
>   - Improve slotPayeeNew() to not to ask if user wants to create new payee or 
> not.
> 
> FIXME: Too much duplicated code from slotPayeeDelete() and others. The way 
> that the
>MyMoney* Objects are designed requires too much repeated work, so I 
> believe using
>generic helper functions might be a good idea.
> 
> 
> Diffs
> -
> 
>   kmymoney/kmymoney.h 22515f4e842a48645ea82ee50d3bd735927b87d5 
>   kmymoney/kmymoney.cpp 063f8b5a0357e39de2482a93abbd4cb33f869e19 
>   kmymoney/kmymoneyui.rc f35364158b77af1ee066d779b59ded7578f5c8f2 
>   kmymoney/views/kpayeesview.h 1fb9633f96355e0cd0da231afc8384bc48f01ca6 
>   kmymoney/views/kpayeesview.cpp 97a3f93ab034707db30fb3085c79b06e7ca8f1ca 
>   kmymoney/views/kpayeesviewdecl.ui 8d9c0083780c5cfb31dc3a237aa1deac1c708cca 
> 
> Diff: http://git.reviewboard.kde.org/r/110212/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Felipe Tonello
> 
>

___
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel


Re: [Kmymoney-devel] feature request

2013-05-13 Thread aga
On Sat, 11 May 2013 14:25:24 -0500
Warren Goodrich  wrote:

> Hello,
> 
> My new feature request is this:
> 
> 
> A lot of my checkbook transactions are via debit card or atm card. I 
> would like to enter EFT (electronic fund transfer) or ATM (automated 
> teller machine) into the number box when doing this. This way, I can 
> scan my register and see right away which transactions were made with
> my debit or atm card. My problem is, if I enter anything except a
> check number in the number box, KMyMoney "forgets" my next check
> number. The program always reverts back to number "1" no mater what
> my next check number should be. Is it possible to change the program
> to allow me to enter EFT or ATM into the number box, but still have
> my next check number "pulled up" automatically in the next
> transaction? Maybe this could be in the form of a drop down menu in
> the number box from which I could choose 1 - ATM or 2 - EFT or 3 -
> Next check number. I know this may not be a "big" issue, but I would
> find it a very nice change. Thanks for listening.
> 

Hello Warren

This appears to be a bug, so please would you report it via
https://bugs.kde.org so that it may be tracked properly.

Thanks

Allan
___
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel