On 2/14/23 07:28, Thomas Baumgart via KMyMoney-devel wrote:
On Montag, 13. Februar 2023 19:49:22 CET Jack via KMyMoney-devel wrote:
I also just noticed that the "Last reconciliation:" shown at the bottom
of the ledger is not "8/9/2018" so it shows the most recently perf
https://bugs.kde.org/show_bug.cgi?id=465695
Jack changed:
What|Removed |Added
Severity|major |wishlist
--- Comment #3 from Jack ---
If it's clearly
https://bugs.kde.org/show_bug.cgi?id=465695
--- Comment #1 from Jack ---
You can use different categories for long and short term cap gains (and I even
have another set for tax deferred accounts.) I think the transactions don't
need different inherent types - you get a dividend of some sort
On 2023.02.13 02:03, Thomas Baumgart via KMyMoney-devel wrote:
On Sonntag, 12. Februar 2023 20:51:51 CET Jack via KMyMoney-devel
wrote:
> On 2023.02.12 07:19, Thomas Baumgart via KMyMoney-devel wrote:
> > On Samstag, 11. Februar 2023 21:51:38 CET Jack via KMyMoney-devel
wrot
On 2023.02.13 02:03, Thomas Baumgart via KMyMoney-devel wrote:
On Sonntag, 12. Februar 2023 20:51:51 CET Jack via KMyMoney-devel
wrote:
> On 2023.02.12 07:19, Thomas Baumgart via KMyMoney-devel wrote:
> > On Samstag, 11. Februar 2023 21:51:38 CET Jack via KMyMoney-devel
wrote:
https://bugs.kde.org/show_bug.cgi?id=465638
Jack changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=465638
--- Comment #1 from Jack ---
Have you tried to use "Not marked?" I think that will do what you want.
"Not cleared" could mean either not marked at all or Reconciled, which is
unlikely what anyone would want to see.
--
You are
On 2023.02.12 07:19, Thomas Baumgart via KMyMoney-devel wrote:
On Samstag, 11. Februar 2023 21:51:38 CET Jack via KMyMoney-devel
wrote:
> When testing the new "reconciled date" as a ledger sort item, I had
a
> transaction from 2018 at the end of the list. Finding th
https://bugs.kde.org/show_bug.cgi?id=453640
--- Comment #21 from Jack ---
You can start at https://invent.kde.org/office/kmymoney/-/wikis/home. It is
not very difficult, but if you are not used to compiling from source, it can be
daunting just to get basic development environment set up, as you
https://bugs.kde.org/show_bug.cgi?id=453640
--- Comment #19 from Jack ---
it is not how it is run, it is how it is compiled, and I do not know of
anywhere such information is collected. I suspect you can download a
distribution's package, unpack it, and run ldd on the kmymoney executable
hange the state from
R to not-reconciled to C to R, but even if that does reset the
reconciledate to today, it would be wrong, and sort badly using the new
sort criteria.
Why do I always seem to find these anomalies?
Jack
https://bugs.kde.org/show_bug.cgi?id=342999
Jack changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=303562
--- Comment #6 from Jack ---
If it were going to be in 5.1.4, for example, we could make a reasonable guess
between weeks and months. Unfortunately, master branch contains enough
changes, and is still a work in progress, that there is no specific
https://bugs.kde.org/show_bug.cgi?id=303562
Jack changed:
What|Removed |Added
Version Fixed In||5.2
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=465214
Jack changed:
What|Removed |Added
Summary|Add "Closed" flag to an |Show open/closed status on
https://bugs.kde.org/show_bug.cgi?id=453640
--- Comment #16 from Jack ---
I don't use Wayland, so I don't know if it has any equivalent of Xorg's
xbuffer. I would try to look into that, at least as a temporary workaround. I
would also ask the Ubuntu devs if they would consider building
https://bugs.kde.org/show_bug.cgi?id=453640
Jack changed:
What|Removed |Added
CC||ostroffjh@users.sourceforge
https://bugs.kde.org/show_bug.cgi?id=453640
--- Comment #10 from Jack ---
There is likely a deb file available for any distribution that uses that format
for packages, but KDE does not provide any.
https://repology.org/project/kmymoney/versions lists available versions by
distro, but does
https://bugs.kde.org/show_bug.cgi?id=303562
Jack changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
CC
I
don't think 6.0 would be appropriate, as I would only use that number
for a version totally and exclusively for Qt 6. Is 5.2 reasonable, or
is there a reason to just not use a version number in such cases.
Jack
https://bugs.kde.org/show_bug.cgi?id=303562
Jack changed:
What|Removed |Added
Component|general |ux-ui
Version|4.6.2
https://bugs.kde.org/show_bug.cgi?id=302917
Jack changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=453640
--- Comment #7 from Jack ---
Per Thomas' comment #1 it seems like you need to find a version compiled with
QWebEngine instead of QWebKit, as long as you are running stable (5.1.x)
instead of master. I am aware that is far more easily said than done
https://bugs.kde.org/show_bug.cgi?id=464870
--- Comment #13 from Jack ---
OK, my c++ reading ability is far worse than I thought. Even debugging through
the Qt code, I somehow missed the switch from the call to item() to the call to
text(). Adding a check before calling text() would certainly
https://bugs.kde.org/show_bug.cgi?id=464870
Jack changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=464560
--- Comment #4 from Jack ---
Will this get backported to 5.1?
In master, when I click apply after changing the value of that new dropdown, I
sometimes get a crash (I haven't gotten a backtrace yet, but will keep trying.)
However, in some of my
https://bugs.kde.org/show_bug.cgi?id=465214
Jack changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=464870
--- Comment #10 from Jack ---
Even though the csv import wizard clearly shows Start Line as 1 and End Line as
6, within sortLines m_startLine is -2 (from csvimporterrc) and m_endLine is 5
(which I assume is correct after changing 1 based counting
https://bugs.kde.org/show_bug.cgi?id=464870
--- Comment #9 from Jack ---
I agree a central check is good - perhaps whenever those values get changed. I
don't think this crash is simply because item() returns a null pointer, but
because something crashes in the depths of Qt during the call
https://bugs.kde.org/show_bug.cgi?id=464870
--- Comment #7 from Jack ---
I wonder whether it is StartLine (or m_profile->m_startline) being negative
that leads to the crash.
The importer has plenty of loops with "for (int row = m_profile->m_startLine;
row <= m_profile->m_endLi
https://bugs.kde.org/show_bug.cgi?id=460079
Jack changed:
What|Removed |Added
CC||ostroffjh@users.sourceforge
https://bugs.kde.org/show_bug.cgi?id=460079
--- Comment #11 from Jack ---
There is definitely something strange going on. If you just hit "Apply" on the
Range tab of the original report, the data all seems to disappear. Saving the
file with the new report and comparing the existi
https://bugs.kde.org/show_bug.cgi?id=464870
Jack changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=464870
--- Comment #4 from Jack ---
I have reproduced the crash with a new user using the csvimporterrc from
comment2. Running in a debugger, in CSVImporterCore::sortSecurities, the row
number starts out negative, even when I set the start and end rows
https://bugs.kde.org/show_bug.cgi?id=464949
Jack changed:
What|Removed |Added
CC||ostroffjh@users.sourceforge
https://bugs.kde.org/show_bug.cgi?id=274021
--- Comment #13 from Jack ---
I think the main problem here is not ideas on how to implement it, but lack of
available developer time. This is basically a "nice to have" as desirable as
it is for some users. The change of importance to H
https://bugs.kde.org/show_bug.cgi?id=464636
--- Comment #2 from Jack ---
The same problem does not happen with Categories because in reports (at least
those I have checked) categories are listed with their full hierarchy, not just
the name of the lowest level category. I wonder if this might
https://bugs.kde.org/show_bug.cgi?id=464636
--- Comment #1 from Jack ---
Please specify exactly where you see this behavior. I am only partly able to
replicate it.
If I run a Transaction by Accounts Report, with the Rows/Columns tab set to
organize by accounts, I do see 2022 listed only once
and useful to have more than one
set of matching rules, which could be chosen per account.
Jack
https://bugs.kde.org/show_bug.cgi?id=464560
--- Comment #1 from Jack ---
I can confirm with Version 5.1.3-caa1baff4, which is a fairly recent Appimage
version on Linux. Just thinking out loud, I wonder if the reconcile headers
should be treated the same as the other group headers
https://bugs.kde.org/show_bug.cgi?id=464435
Jack changed:
What|Removed |Added
Severity|normal |wishlist
--- Comment #2 from Jack ---
I'm pretty sure
https://bugs.kde.org/show_bug.cgi?id=464055
Jack changed:
What|Removed |Added
Summary|crash when entering a |crash when entering a
|portfogllio
https://bugs.kde.org/show_bug.cgi?id=424511
--- Comment #7 from Jack ---
What should the subject of this bug actually be? The current one doesn't
really make sense. (It's worth fixing to assist future searching.)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=464337
Jack changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
On 2023.01.10 13:29, Jack via KMyMoney-devel wrote:
On 2023.01.09 02:38, Thomas Baumgart via KMyMoney-devel wrote:
On Sonntag, 8. Januar 2023 22:19:57 CET Jack via KMyMoney-devel
wrote:
> I'm trying to create a sample kmy file with long, complicated
> investment and brokerage ac
On 2023.01.09 02:38, Thomas Baumgart via KMyMoney-devel wrote:
On Sonntag, 8. Januar 2023 22:19:57 CET Jack via KMyMoney-devel wrote:
> I'm trying to create a sample kmy file with long, complicated
> investment and brokerage accounts for testing the sorting issues
> recently causing
https://bugs.kde.org/show_bug.cgi?id=464055
--- Comment #8 from Jack ---
Thank you for the screen shot, it does help. We can work through terminology
and language differences.
It looks like you are buying one share of the Bitcoin security with a value of
1BTC per share - but you are paying
On 2023.01.09 02:38, Thomas Baumgart via KMyMoney-devel wrote:
On Sonntag, 8. Januar 2023 22:19:57 CET Jack via KMyMoney-devel wrote:
> I'm trying to create a sample kmy file with long, complicated
> investment and brokerage accounts for testing the sorting issues
> recently causing
https://bugs.kde.org/show_bug.cgi?id=464055
--- Comment #6 from Jack ---
Guy - if possible, please configure your email software to send text only. The
HTML portion gets added to the bug as an attachment.
There is still something I don't understand. If you have an Investment account
in BTC
https://bugs.kde.org/show_bug.cgi?id=464055
--- Comment #4 from Jack ---
I'm having trouble recreating this. Your base currency is CHF. I assume you
are creating the buy transaction in an investment account, and that account is
in BTC. Did you create an associated brokerage account? Also
https://bugs.kde.org/show_bug.cgi?id=464055
--- Comment #3 from Jack ---
First, when replying by email, please delete everything of the previous
comment, since your entire message becomes the next comment in the bug.
Don't worry about debugs and backtrace for now. We'll provide more information
https://bugs.kde.org/show_bug.cgi?id=464055
Jack changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
?
Thanks for any pointers.
Jack
Just to confirm, Version 5.1.80-b96565589
On 2023.01.08 01:47, Thomas Baumgart via KMyMoney-devel wrote:
On Samstag, 7. Januar 2023 21:27:16 CET Jack via KMyMoney-devel wrote:
> On 2023.01.07 08:53, Thomas Baumgart via KMyMoney-devel wrote:
> [...]
> >
Not sure about the inve
https://bugs.kde.org/show_bug.cgi?id=332924
--- Comment #8 from Jack ---
Very odd - it looks like those changes were only made in master and not the 5.1
branch. Was it actually working in 5.1.2? The branches differ enough that
backporting will not be trivial (for me.) Hopefully the fix isn't
be glad to provide a screen shot if it would help.
I wonder if the "Normal View" tab in the sorting config needs to be
split for Investment and other account types.
Jack
On 2023.01.03 02:17, Thomas Baumgart via KMyMoney-devel wrote:
On Montag, 2. Januar 2023 23:48:32 CET Jack via KMyMoney-devel wrote:
> On 2022.12.28 09:25, Thomas Baumgart via KMyMoney-devel wrote:
> > On Dienstag, 27. Dezember 2022 03:24:28 CET Jeremy Whiting via
> > KMyMo
it?
Jack
https://bugs.kde.org/show_bug.cgi?id=463854
--- Comment #1 from Jack ---
I believe in master branch, the original field from which Payee was detected is
included in it's entirety in the memo. I don't know if there is any chance
that this will be back-ported to 5.1 or not. What date does
https://bugs.kde.org/show_bug.cgi?id=461392
Jack changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
--- Comment #2 from Jack ---
Adjusting
of the date
field is selected.
I also noticed you have to hit tab twice to get from the date view to
get
to the payment box. Checking the .ui file it looks like an account
combobox/edit box is first in the tab order, but that's hidden in
ledger
view.
On Mon, Jan 2, 2023 at 3:48 PM Jack via
n third
from the bottom. As long as date is the first sort key, then I think
the running balance should be in the order displayed. That was even if
the balances don't match a statement exactly for each transaction, they
should still match at the end of each day.
Jack
https://bugs.kde.org/show_bug.cgi?id=463708
--- Comment #11 from Jack ---
First, I do not believe there is any way to match the Category on import. The
Category is set if the imported transaction is matched to an existing
transaction. If there is not already a wishlist for that, perhaps we can
https://bugs.kde.org/show_bug.cgi?id=463708
Jack changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=463708
Jack changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=463708
--- Comment #4 from Jack ---
What I will ask is what type of PC are you using? I just did import the csv to
a newly created XML file with one checking account. It accepted column 1 as
the date, column 2 as the payee, and column 3 as the payment
https://bugs.kde.org/show_bug.cgi?id=463708
Jack changed:
What|Removed |Added
CC||ostroffjh@users.sourceforge
https://bugs.kde.org/show_bug.cgi?id=463708
Jack changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=185570
Jack changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=445604
Jack changed:
What|Removed |Added
Summary|Ledger rows are too narrow |Ledger rows are too short
|in Windows
https://bugs.kde.org/show_bug.cgi?id=400465
--- Comment #7 from Jack ---
Brendon: Thanks. That was what I was thinking about.
Phillip: If you still get duplicates after following Brendan's advice, please
open a new ticket. Thanks.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=185570
Jack changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=178906
Jack changed:
What|Removed |Added
Resolution|FIXED |WAITINGFORINFO
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=178906
Jack changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=225550
Jack changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=283783
--- Comment #5 from Jack ---
While 5.1 seems to still only show future scheduled transactions if the sort
order is primary date ascending, current master shows them for any sort order
(that I have tested.) They are shown very dim, so
https://bugs.kde.org/show_bug.cgi?id=463015
--- Comment #2 from Jack ---
You are correct that there is no current way to tell KMM not to allow any new
transaction for a given Payee, so this is valid wishlist request. At minimum,
marking a Payee as inactive would remove that Payee from any
https://bugs.kde.org/show_bug.cgi?id=463246
--- Comment #3 from Jack ---
It really would make it easier if you provide a sample csv file, even if it's
only a header and one data row. It may be obvious to you what is wrong, but
debugging to find exactly where in the code the problem occurs
https://bugs.kde.org/show_bug.cgi?id=377869
Jack changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=385900
Jack changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=400465
--- Comment #5 from Jack ---
Given the original report was for QIF files, I'm not going to change the
status, and will let this one get closed if the OP doesn't respond.
OFX duplicate detection generally relies on a unique transaction ID provided
https://bugs.kde.org/show_bug.cgi?id=384279
Jack changed:
What|Removed |Added
Resolution|WAITINGFORINFO |UNMAINTAINED
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=385278
Jack changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Severity|normal
https://bugs.kde.org/show_bug.cgi?id=395339
Jack changed:
What|Removed |Added
Product|kmymoney|neon
Version|5.0.1
https://bugs.kde.org/show_bug.cgi?id=462827
--- Comment #6 from Jack ---
Just for clarification, is this when editing splits in a transaction in the
ledger, or when editing splits in a scheduled transaction?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=395339
--- Comment #4 from Jack ---
You need to report that to Neon. It sounds like the KMM they are distributing
was built with Qt 5.15.3, even though the rest of the distro is up to 5.15.7.
If so, they just need to rebuild KMM using the newer Qt
https://bugs.kde.org/show_bug.cgi?id=392755
Jack changed:
What|Removed |Added
Summary|kmymoney-4.8.1.1|Suggestion: Category for
|suggestion
https://bugs.kde.org/show_bug.cgi?id=392755
Jack changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Severity|normal
https://bugs.kde.org/show_bug.cgi?id=395503
Jack changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=343291
Jack changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=343291
--- Comment #10 from Jack ---
Yes, the consistency check continues to be improved to identify more and more
different issues.
However, what typo? If it's in my message, I plead too much hurry. If it's in
the program, we can fix it.
--
You
https://bugs.kde.org/show_bug.cgi?id=396301
Jack changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=384804
Jack changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Severity|normal
https://bugs.kde.org/show_bug.cgi?id=462246
--- Comment #1 from Jack ---
This is a valid wishlist. The underlying issue is that scheduled transactions
in the future are not really transactions until they are entered into the
ledger. They are shown in the ledger due to special handling which
https://bugs.kde.org/show_bug.cgi?id=343291
Jack changed:
What|Removed |Added
CC|ostroffjh@users.sourceforge |
|.net
https://bugs.kde.org/show_bug.cgi?id=462513
Jack changed:
What|Removed |Added
CC|ostroffjh@users.sourceforge |
|.net
https://bugs.kde.org/show_bug.cgi?id=462513
Jack changed:
What|Removed |Added
CC||ostroffjh@users.sourceforge
https://bugs.kde.org/show_bug.cgi?id=462366
Jack changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
, Jack via KMyMoney-devel wrote:
Check the content of the libalkimia-dev package for alkversion.h.
It might be in an unexpected location. My libalkimia 8.1.1 has it
in /usr/include/alkimia/Qt5/alkimia/alkversion.h. However, it
looks like KMM requires libalkimia > 5.0, so you should be
On 2022.11.14 07:25, Thomas Baumgart via KMyMoney-devel wrote:
On Samstag, 12. November 2022 16:48:15 CET Jack via KMyMoney-devel
wrote:
> On 11/12/22 09:27, Thomas Baumgart via KMyMoney-devel wrote:
> > [snip ...]
>
> > We may do a first alpha release towards the end
401 - 500 of 2627 matches
Mail list logo
