[digikam] [Bug 391840] Timeline does not show any pictures if range is too big

https://bugs.kde.org/show_bug.cgi?id=391840 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In|

[digikam] [Bug 391840] Timeline does not show any pictures if range is too big

https://bugs.kde.org/show_bug.cgi?id=391840 --- Comment #10 from IWBR --- I no longer have this issue, at least using the linux version of Digikam (in my new computer I don't have a windows installation, so I can't try it). If it were for me, you can close it. -- You are receiving this mail

[digikam] [Bug 391840] Timeline does not show any pictures if range is too big

https://bugs.kde.org/show_bug.cgi?id=391840 --- Comment #9 from Maik Qualmann --- Git commit 1f8edbda8bff2a3e201b8870a686f0066e20d590 by Maik Qualmann. Committed on 22/04/2019 at 18:35. Pushed by mqualmann into branch 'master'. use QReadWriteLock for the CollectionManager Loading a large item

[digikam] [Bug 391840] Timeline does not show any pictures if range is too big

https://bugs.kde.org/show_bug.cgi?id=391840 --- Comment #8 from Maik Qualmann --- Git commit abd32eefb24ac94c6a5343869578eabdd9ec9f9d by Maik Qualmann. Committed on 03/01/2019 at 19:43. Pushed by mqualmann into branch 'master'. use ReadWriteLock for the CollectionManager Loading a large item

[digikam] [Bug 391840] Timeline does not show any pictures if range is too big

https://bugs.kde.org/show_bug.cgi?id=391840 --- Comment #7 from Maik Qualmann --- Git commit f27ab9c1051bd0a0bba6e79bc77899c74a7e6bf8 by Maik Qualmann. Committed on 07/10/2018 at 13:47. Pushed by mqualmann into branch 'master'. add a global cache for grouped images When we load the images into

[digikam] [Bug 391840] Timeline does not show any pictures if range is too big

https://bugs.kde.org/show_bug.cgi?id=391840 --- Comment #6 from Maik Qualmann --- I'll take a look at it in the next few days. Was not there something with only 200 items in the block reading, so that the GUI does not freeze? Maik -- You are receiving this mail because:

[digikam] [Bug 391840] Timeline does not show any pictures if range is too big

https://bugs.kde.org/show_bug.cgi?id=391840 --- Comment #5 from IWBR --- Gilles, I am not sure if that is what you asked, but the database stopped responding at some point between the selection of 68438 (works just fine) and 72600 elements (empty response). That was the

[digikam] [Bug 391840] Timeline does not show any pictures if range is too big

https://bugs.kde.org/show_bug.cgi?id=391840 --- Comment #4 from caulier.gil...@gmail.com --- MAik, Look in core/libs/database/items/imagelisterreceiver.cpp::ImageListerJobGrowingPartsSendingReceiver::receive(). What is that : m_limit m_maxLimit ??? Gilles -- You are receiving this mail

[digikam] [Bug 391840] Timeline does not show any pictures if range is too big

https://bugs.kde.org/show_bug.cgi?id=391840 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment

[digikam] [Bug 391840] Timeline does not show any pictures if range is too big

https://bugs.kde.org/show_bug.cgi?id=391840 --- Comment #2 from IWBR --- In this case, I can tell that it is not because digikam is still loading all the items, since if that was the case, it would become a bit irresponsive for a few seconds. When selecting more than

[digikam] [Bug 391840] Timeline does not show any pictures if range is too big

https://bugs.kde.org/show_bug.cgi?id=391840 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com

[digikam] [Bug 391840] Timeline does not show any pictures if range is too big

https://bugs.kde.org/show_bug.cgi?id=391840 IWBR changed: What|Removed |Added CC||iwannaber...@gmail.com -- You