Version: unspecified (using KDE 4.3.5) OS: Linux KMyMoney -> Ledger -> (double-click) entry -> "split transaction" button -> enter category for first portion -> enter memo -> enter amount -> enter category for second part of the split... at this point, regardless of which data I try to enter (memo or amount) whenever I start typing it immediately assumes I am trying to select a category again and jumps the cursur to the second part of the split's category section. Reproducible: Didn't try Steps to Reproduce: KMyMoney -> Ledger -> (double-click) entry -> "split transaction" button -> enter category for first portion -> enter memo -> enter amount -> enter category for second part of the split... Actual Results: unable to enter more than one entry in the split transaction dialogue Expected Results: should be able to enter multiple splits for any given transaction OS: Linux (i686) release 2.6.31.12-0.2-desktop Compiler: gcc
Which version are you using? Did you install from your distro's repository or compile from scratch? I've either got the same problem, or something related. I'm using the latest svn version. For any old transaction that already has a split, the split button is disabled, but clicking on "split transaction" in the category field brings up the split editor. It appears I CAN add additional splits there. However, for a new transaction, or an old one without a split, the split button is disabled, and I can find no way to actually create a split transaction.
That might be a related issue, but it isn't the same one I'm reporting. This is the first time I've tried kmymoney4 and I haven't imported anything. It always gives me the option for splitting a transaction, but it never lets me finish modifying the second transaction correctly. I'm using the kmymoney compiled into OpenSUSE's Factory distribution (the one that will eventually replace the currently stable 11.2 version after more bugs are worked out so it can be called 11.3). The RPM package lists.. kmymoney4-3.98.1-1.4.i586 I believe I got the package from.. http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openSUSE_11.2/ On Mon, Jun 28, 2010 at 6:50 PM, Jack <ostroffjh@users.sourceforge.net>wrote: > https://bugs.kde.org/show_bug.cgi?id=242918 > > > Jack <ostroffjh@users.sourceforge.net> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |ostroffjh@users.sourceforge > | |.net > > > > > --- Comment #1 from Jack <ostroffjh users sourceforge net> 2010-06-29 > 01:50:15 --- > Which version are you using? Did you install from your distro's repository > or > compile from scratch? > > I've either got the same problem, or something related. I'm using the > latest > svn version. For any old transaction that already has a split, the split > button is disabled, but clicking on "split transaction" in the category > field > brings up the split editor. It appears I CAN add additional splits there. > However, for a new transaction, or an old one without a split, the split > button > is disabled, and I can find no way to actually create a split transaction. > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. >
Is this problem still happening? Do you use the transaction form below or you edit directly on the register list?
The problem with the disabled button has been fixed in SVN HEAD. Besides that, I am unable to duplicate the problem here using SVN HEAD.
Is this still happening? A lot has happened in that area in the meantime.
My problem was just the disabled split button, which Thomas fixed, so I have no issues with this. Is anybody else using OpenSUSE?
I'll check if I'm still having the problem when I get home. I've been using the kmymony4 package from OpenSUSE's repositories. Would the changes that have been made have been fixed there, or will I need to compile it myself to check?
I am pretty sure you have to build from source unless the open suse repository has been updated after the fix (which I doubt)
Please reopen if you keep having the problem with the latest version.