[kmymoney] [Bug 395098] Moving around in budget amount (assignments) fields

2018-07-27 Thread Joshua Christopher
https://bugs.kde.org/show_bug.cgi?id=395098

Joshua Christopher  changed:

   What|Removed |Added

 CC||chrisjoshtop...@gmail.com

--- Comment #1 from Joshua Christopher  ---
I'm not able to reproduce this in git master. Has it been fixed?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 395985] New: QIF Export manually typing file path adds .qif after every character

2018-06-28 Thread Joshua Christopher
https://bugs.kde.org/show_bug.cgi?id=395985

Bug ID: 395985
   Summary: QIF Export manually typing file path adds .qif after
every character
   Product: kmymoney
   Version: 5.0.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: exporter
  Assignee: kmymoney-de...@kde.org
  Reporter: chrisjoshtop...@gmail.com
  Target Milestone: ---

When trying to manually type a path in at the QIF export dialog, the string
".qif" gets added automatically after each character press. See the linked gif
showing what is happening on my computer when I type "a" followed by "b" then
"c".

https://gfycat.com/SkeletalThunderousCockroach

The final string is "a.qifb.qifc.qif" and if you choose to export with that in
the path field then the file is written to $HOME/a.qifb.qifc.qif (on linux, I
presume similar for other operating systems?)

If you write the path you want in a separate program such as a text editor, you
can copy and paste the path into the field and it will export to the path/file
given as expected.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 395912] Number field not wide enough when directly entering transactions into list

2018-06-27 Thread Joshua Christopher
https://bugs.kde.org/show_bug.cgi?id=395912

--- Comment #2 from Joshua Christopher  ---
Created attachment 113615
  --> https://bugs.kde.org/attachment.cgi?id=113615=edit
Input field clips to smaller than column display

I notice that the numbers display column does expand when the transaction is
entered, but the input field for the number is about one digit smaller than the
display.

To show this, I entered a big number for a transaction (in this case 1234567)
and the number column resizes after entering the transaction. In the next
transaction I type in the number to 1234568, but the input field only displays
the last 6 digits instead of all 7 (the leading digit is clipped in the view
but still there). I'll attach another screen shot here to demonstrate.

This is independent of how wide the KMM window is.

I feel that the input field should be able to show the same number of digits as
the column displays when not editing the transaction, and it looks like it may
be a regression from whenever the screen shot on this page was taken:
https://docs.kde.org/stable5/en/extragear-office/kmymoney/details.ledger.direct.html.
I figured it should be reported as a bug due to that (although probably a
rather minor bug).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 395912] New: Number field not wide enough when directly entering transactions into list

2018-06-26 Thread Joshua Christopher
https://bugs.kde.org/show_bug.cgi?id=395912

Bug ID: 395912
   Summary: Number field not wide enough when directly entering
transactions into list
   Product: kmymoney
   Version: 5.0.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: chrisjoshtop...@gmail.com
  Target Milestone: ---

Created attachment 113587
  --> https://bugs.kde.org/attachment.cgi?id=113587=edit
Number field too narrow for 3 digits

The number field is too small when entering transactions directly into the
list. Currently only two characters are visible in the number field but at
least three should be visible if not 4. See the attached screenshot where I
have entered the number 111 but only "11" is visible.

Steps to reproduce:
1. Turn off transaction form (Settings->Configure KMyMoney->Ledger->Display
tab).
2. Insert a new transaction in an account
3. See that only two characters are visible in the Number field.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 392477] Cannot create new investment

2018-06-18 Thread Joshua Christopher
https://bugs.kde.org/show_bug.cgi?id=392477

--- Comment #4 from Joshua Christopher  ---
I'm sorry, I linked to the wrong bug in the previous post. The bug regarding
the workaround is: https://bugs.kde.org/show_bug.cgi?id=395591

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 392477] Cannot create new investment

2018-06-18 Thread Joshua Christopher
https://bugs.kde.org/show_bug.cgi?id=392477

Joshua Christopher  changed:

   What|Removed |Added

 CC||chrisjoshtop...@gmail.com

--- Comment #3 from Joshua Christopher  ---
I am having this exact same issue. I am also having an issue with the
workaround, see https://bugs.kde.org/show_bug.cgi?id=328280.

Error message:
"Unable to create all objects for the investment"

Details:
"Stock account cannot be parent account caugt in
/workspace/build/kmymoney/mymoney/mymoneyfile.cpp:1059"

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 395591] New: Cannot enter transaction after creating new security

2018-06-18 Thread Joshua Christopher
https://bugs.kde.org/show_bug.cgi?id=395591

Bug ID: 395591
   Summary: Cannot enter transaction after creating new security
   Product: kmymoney
   Version: 5.0.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: chrisjoshtop...@gmail.com
  Target Milestone: ---

Seems very similar to: https://bugs.kde.org/show_bug.cgi?id=328280
And possibly related to: https://bugs.kde.org/show_bug.cgi?id=392477 (At least
I discovered this bug while following the workaround mentioned there).

Basically the issue is as in the title.

Reproducible: Always

Steps to Reproduce:
1. Open the ledger for an Investment Account
2. Enter a new security.
3. Complete the wizard.
4. Fill out the rest of the New Transaction form with data
5. Attempt to enter the transaction.

Actual Results:  
There is no way to enter the transaction. The Enter button is disabled and
pushing the "Enter" key on my keyboard does nothing.

The new security name is filled out in the form. If you select a different and
already existing security then try to select your new security, the new
security does not exist. While you have selected a different and already
existing security it is possible to enter the transaction.

If you go to the "Investments" page for the account you just tried to create a
new security in, the new security does show up in the list. If you then return
to the Ledger for the account, you can now select the new security and enter
transactions like normal.


Expected Results:  
You should be able to enter the transaction immediately after completing the
New Security Wizard and filling out the other necessary information in the New
Transaction Form. Switching to the Investments page and back should not be
necessary.

-- 
You are receiving this mail because:
You are watching all bug changes.