[kmymoney] [Bug 484759] Transaction report fails to update when I expand the date range to include a large number of transactions

2024-05-08 Thread Andy
https://bugs.kde.org/show_bug.cgi?id=484759

--- Comment #15 from Andy  ---
(In reply to Jack from comment #14)
> Since there is a workaround, it is not critical, but should we reopen this,
> changing the subject to reflect that the problem seems to be in the display
> of the produced html, not in actually producing the html report?  Does
> anyone know/has anyone tested whether the same problem is still present in
> master branch?

Agreed. The work around is reasonable, but not obvious. Changing the Subject as
you suggested is a good idea.

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

[kmymoney] [Bug 484759] Transaction report fails to update when I expand the date range to include a large number of transactions

2024-05-08 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=484759

--- Comment #14 from Jack  ---
Since there is a workaround, it is not critical, but should we reopen this,
changing the subject to reflect that the problem seems to be in the display of
the produced html, not in actually producing the html report?  Does anyone
know/has anyone tested whether the same problem is still present in master
branch?

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

[kmymoney] [Bug 484759] Transaction report fails to update when I expand the date range to include a large number of transactions

2024-05-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=484759

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #13 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[kmymoney] [Bug 484759] Transaction report fails to update when I expand the date range to include a large number of transactions

2024-04-18 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=484759

--- Comment #12 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[kmymoney] [Bug 484759] Transaction report fails to update when I expand the date range to include a large number of transactions

2024-04-04 Thread Andy
https://bugs.kde.org/show_bug.cgi?id=484759

--- Comment #11 from Andy  ---
(In reply to Jack from comment #10)
> It almost sounds as if it has actually completed generating the report, but
> fails to display the results properly.  If it was still working on
> generating the report, I don't think you would be able to just close the
> report.  That might tie in with Thomas' comment about the time being taken
> up in the setHtml() function and the html output being much larger on
> Windows than on Linux.  I'm not sure how to test or resolve, but after it
> produces the blank output, can you export the report as html?  Then try
> opening it in a browser.

You are absolutely right. If I export the report it has been generated it's
just not displaying. That's a fix but still seems it would be good to have it
display. The html file is indeed over 2MB.

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

[kmymoney] [Bug 484759] Transaction report fails to update when I expand the date range to include a large number of transactions

2024-04-04 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=484759

--- Comment #10 from Jack  ---
It almost sounds as if it has actually completed generating the report, but
fails to display the results properly.  If it was still working on generating
the report, I don't think you would be able to just close the report.  That
might tie in with Thomas' comment about the time being taken up in the
setHtml() function and the html output being much larger on Windows than on
Linux.  I'm not sure how to test or resolve, but after it produces the blank
output, can you export the report as html?  Then try opening it in a browser.

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

[kmymoney] [Bug 484759] Transaction report fails to update when I expand the date range to include a large number of transactions

2024-04-04 Thread Andy
https://bugs.kde.org/show_bug.cgi?id=484759

--- Comment #9 from Andy  ---
(In reply to Andy from comment #7)
> I ran the report using all dates on the Lennox machine just to double check
> the time. It took four seconds. On the windows machine if I open the report
> with a 1 year date range, it runs in about 4 seconds also, but if I expand
> the date filter to 4 years and click apply, the machine is busy for 5-10
> seconds and then become idle again but the report does not change. The
> report filter still shows the expanded date range but the report does not
> update. The system is happy to let me shorten the date range and if short
> enough, it gives me the update.
> 
> If I close the report with a large date range in the filter, I get no
> output, even after waiting for 5 minutes. It will however allow me to
> shorten the date range from the blank report screen and runs the shortened
> range in 1 sec. I still think this is a bug.

The last part should say:

If I close the report with a large date range in the filter, when I reopen it,
I get no output, even after waiting for 5 minutes. It will however allow me to
shorten the date range from the blank report screen and runs the shortened
range in 1 sec. I still think this is a bug.

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

[kmymoney] [Bug 484759] Transaction report fails to update when I expand the date range to include a large number of transactions

2024-04-04 Thread Andy
https://bugs.kde.org/show_bug.cgi?id=484759

--- Comment #8 from Andy  ---
(In reply to Thomas Baumgart from comment #5)
> Looking at the runtime distribution using hotspot
> (https://github.com/KDAB/hotspot) I noticed that the time is burned in
> setHtml() of either QWebEngineView/KWebView (5.1) / QTextBrowser (master).
> The generated page sizes of the reports are ~380 KB vs. 2.7 MB.

I don't know what this comments means. Please give me some more explanation.
Thanks.

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

[kmymoney] [Bug 484759] Transaction report fails to update when I expand the date range to include a large number of transactions

2024-04-04 Thread Andy
https://bugs.kde.org/show_bug.cgi?id=484759

--- Comment #7 from Andy  ---
I ran the report using all dates on the Lennox machine just to double check the
time. It took four seconds. On the windows machine if I open the report with a
1 year date range, it runs in about 4 seconds also, but if I expand the date
filter to 4 years and click apply, the machine is busy for 5-10 seconds and
then become idle again but the report does not change. The report filter still
shows the expanded date range but the report does not update. The system is
happy to let me shorten the date range and if short enough, it gives me the
update.

If I close the report with a large date range in the filter, I get no output,
even after waiting for 5 minutes. It will however allow me to shorten the date
range from the blank report screen and runs the shortened range in 1 sec. I
still think this is a bug.

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

[kmymoney] [Bug 484759] Transaction report fails to update when I expand the date range to include a large number of transactions

2024-04-04 Thread Andy
https://bugs.kde.org/show_bug.cgi?id=484759

--- Comment #6 from Andy  ---
(In reply to Thomas Baumgart from comment #3)
> It's a matter of waiting :) The data set is large (many transactions) and
> creating the report over all of them takes a while. I tested against current
> master version on Windows (but it takes a long time on Linux too). You may
> take a look at CPU usage when changing the period.
> 
> ps : hope you don't mind that I requested to remove the file for privacy
> reasons.

I will try giving it more time. On my Linux machine the report finishes in
about 3 seconds, but it is a fast computer.

No problem on removing the file. There was nothing in there that anyone could
understand. I'm pretty sure.

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

[kmymoney] [Bug 484759] Transaction report fails to update when I expand the date range to include a large number of transactions

2024-04-01 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=484759

--- Comment #5 from Thomas Baumgart  ---
Looking at the runtime distribution using hotspot
(https://github.com/KDAB/hotspot) I noticed that the time is burned in
setHtml() of either QWebEngineView/KWebView (5.1) / QTextBrowser (master). The
generated page sizes of the reports are ~380 KB vs. 2.7 MB.

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

[kmymoney] [Bug 484759] Transaction report fails to update when I expand the date range to include a large number of transactions

2024-03-31 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=484759

Thomas Baumgart  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #4 from Thomas Baumgart  ---
Forgot to change status

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

[kmymoney] [Bug 484759] Transaction report fails to update when I expand the date range to include a large number of transactions

2024-03-31 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=484759

--- Comment #3 from Thomas Baumgart  ---
It's a matter of waiting :) The data set is large (many transactions) and
creating the report over all of them takes a while. I tested against current
master version on Windows (but it takes a long time on Linux too). You may take
a look at CPU usage when changing the period.

ps : hope you don't mind that I requested to remove the file for privacy
reasons.

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

[kmymoney] [Bug 484759] Transaction report fails to update when I expand the date range to include a large number of transactions

2024-03-30 Thread Andy
https://bugs.kde.org/show_bug.cgi?id=484759

--- Comment #2 from Andy  ---
Let me know if you are unable to duplicate the bug without a large transaction
set.

Thanks.

Andy

> On Mar 30, 2024, at 3:26 PM, Ben Cooksley  wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=484759
> 
> --- Comment #1 from Ben Cooksley  ---
> The content of attachment 167943 has been deleted for the following reason:
> 
> Removing confidential information
> 
> -- 
> You are receiving this mail because:
> You reported the bug.

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

[kmymoney] [Bug 484759] Transaction report fails to update when I expand the date range to include a large number of transactions

2024-03-30 Thread Ben Cooksley
https://bugs.kde.org/show_bug.cgi?id=484759

--- Comment #1 from Ben Cooksley  ---
The content of attachment 167943 has been deleted for the following reason:

Removing confidential information

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