Re: Another possible gb.poppler bug?

[gbWilly <gbWilly@xxxxxxxxxxxxxx>]

On Tuesday, December 2nd, 2025 at 18:12, Gianluigi <gradobag@xxxxxxxxxxx> wrote:

> Il 02/12/25 17:26, Claus Dietrich ha scritto:
> 
> > Am 02.12.25 um 12:41 schrieb Gianluigi:
> > 
> > > You may not remember, but Hans also involved me in the PDF editor
> > > project.
> > > Did you see the video?
> > > Have you tried opening a file of more than 1,000 pages with the PDF-
> > > Reader project?
> > > Does it seem to work like Atril or similar programs?
> > > Also, PDF-Rider doesn't seem to work, it seems to freeze, and in some
> > > cases (out of memory) it doesn't even close the Open window.
> > > Then it opens, but then...
> > 
> > Hi Gianluigi
> > 
> > I have seen the video and it didn't surprise me.
> > 
> > It goes without saying that rendering takes time and if there are no
> > thumbnails and the number of pages is high then it takes plenty of time.
> > What makes you think that the rendering is the brake in a Gambas PDF
> > viewer? There are other controls that eat a lot of processing time as
> > well. Further you can hardly compare mature PDF viewers with a Gambas
> > PDF viewer without considering the differences in the programming
> > languages.
> > 
> > Have you ever loaded a huge PDF with Okular? Sometimes it takes an
> > eternity to display it.
> > 
> > This thread is purely based on the assumption, that most PDFs contain
> > thumbnails and that they are displayed by the standard PDF viewers. No
> > proof has been provided yet, that this assumption is correct.
> > 
> > I am assuming the opposite! Almost all PDFs I ever came across didn't
> > have embedded thumbnails.
> > 
> > I came to this conclusion because I tested it. This required a side trip
> > back into the Windows world and to Adobe Acrobat. I took a PDF generated
> > with LibreOffice (having no thumbnails) and added thumbnails to it with
> > Adobe Acrobat. Now I had two versions of the same PDF - one with and one
> > without thumbnails. When I loaded the self-made PDF with thumbnails in
> > my Gambas PDF Viewer the embedded thumbnails were found and displayed.
> > As expected the loading was faster and I noted that the embedded
> > thumbnails look totally different than the self rendered ones - which
> > was no surprise.
> > 
> > Have a look by yourself. I loaded both PDFs up into my cloud: https://
> > magentacloud.de/s/4TJeHaqcgQbNKri
> > 
> > and included screenshots of my Gambas PDF viewer, so that you can see
> > the difference (with/without thumbnails) yourself.
> > 
> > Is there a way to provide me with the 1000-pages PDF shown in the video?
> > This would allow me to compare the solution of gbWilly with my own and
> > to search for possible brakes in our apps.
> 
> Dear Claus,
> 
> Excuse me, but I'm not criticizing anything or anyone.
> I'm just showing the state of the art.
> 
> Benoit has said repeatedly that if you want to emulate DE readers, you
> need to open the PDF file, for example, as in the first gbWilly test
> (actually test number two), the one with only the indexes, and then
> gradually display the thumbnails as needed.
> I asked him if he could add a function like GridView_Data (assuming it
> isn't already there), or if he could give me a hint on how to do it.
> Unfortunately, my request was ignored.
> 
> I believe you when you say you've done all the necessary tests.
> Unfortunately, I don't have the time to do any testing right now.
> Just a clarification: there's a difference between rendering and
> refreshing, as Fabien Bodard pointed out to me.
> 
> I don't remember where it was, but I downloaded the 1,059-page PDF file
> from https://www.asus.com/support/download-center/
> I downloaded it by searching for motherboards (a memory from when I
> built my PC).
> 
Gianluigi,

Can you somehow get that file to me? Create a topic in Contributors corner on gambas one forum and upload it there. I really want to use this file for testing while creating the needed load improvements


gbWilly

GambOS
Gambas3 for Debian/Ubuntu

...there is always a Catch if things go wrong!