Happens on Edge (chromium) and Chrome - although it seemed that Chrome was
loading faster.
Looking a the logs again, the “getting cover” messages reference the file name,
but when I navigate to another library page the “getting cover” references the
comic I’d.
On 25/03/2021, at 1:05 AM, Darryl L. Pierce <mcpierce@xxxxxxxxx> wrote:
I can't either, since the app doesn't pre-emptively load covers. The covers
are loaded when the browser itself (not the app) requests them. The app just
gives the browser the URL for the images. But it only does that for the
issues being shown on the library page (for multiple comics) or for the
single issue being viewed when you're on the comic details page. I literally
have not written any code to load all covers at any point, and there's no
code in the frontend to load covers at all.
On Wed, Mar 24, 2021 at 5:42 AM Guy Incognito <dmarc-noreply@xxxxxxxxxxxxx>
wrote:
Just fired up 0.8 on the db I created using 0.7 - 2.7k of comics.
0.7 loads them lightning quick, 0.8...not so much. It’s been at least 5
minutes, and it looks like 1700 comics have been loaded.
I’m showing 10 comics per page, the first page is showing 10 issues of
Echo...the log I’m watching has 2k worth of “Getting cover for...” messages
(occurring in batches of 100), and is currently working through Marvel. My
library is currently grouped by publisher - Echo is Abstract Studios, so
should be first...I can’t think of any reason my CX is looking for Marcel
covers that wouldn’t be displayed on the first page.
--
Darryl L. Pierce <mcpierce@xxxxxxxxx>
"Le centre du monde est partout." - Blaise Pascal
"Let's try and find some point of transcendence and leap together." - Gord
Downie
