Quote:
Originally Posted by KevinH
So that just leaves the image buffers being garbage collected by python before they are used.
I will take a look at the plugin code and run some tests. Can you pm me a link to your epub so I can test with it? Or point me to a public epub that shows similar issues in your machine?
I will then modify the code to keep the proper image pointers and replace the use of image copy() to see if that helps.
|
I'm afraid the problem has become a little different. I was just making you a link to my book epub file which had the gif display problems with this plugin when I decided to have a quick recheck. Every gif now displays perfectly as a small image in the plugin window.
I went through all the other epub files where I previously found some gifs displayed and some didn't. Now they all display and I cannot find one that doesn't.
The only thing I've changed today is to download DiapDealer's AppImage : see
https://www.mobileread.com/forums/sh...12#post4373712
This AppImage is intended to provide all the bits and pieces for Qt6 operation in linux and avoids having to edit the wrapper file in /usr/local/bin/sigil to remove the QTLIB_DIR statement.
So with DiapDealer's AppImage in use, all the gifs now display.
To double-check, I changed the path in Sigil's plugin manager to use the system python and made sure the QTLIB_DIR statement was removed from the wrapper script. So I went back to the state where I had the gif display problems. And they're there again exactly as before: 001.gif - 073.gif will not display, 074.gif to 089.gif do display.
Going back to DiapDealer's AppImage again and all gifs display ok. It seems to be systematically repeatable.
In both cases, with AppImage and without, my Sigil 2.0.2 with Qt6 installation runs the testplugin with complete success.
That AppImage file must contain/provide something I was missing or which was deficient/corrupt in the installation work of Qt6 bits and pieces in that above-mentioned thread. But why only some gifs were affected remains a mystery.
Or something which is more tolerant of some deficiency in the plugin's code?
I don't know how useful it will be to pursue further down this rabbit hole.