Sigil 2.7.5 Release Candidate (RC) Now Available - Page 4

BeckyEbook · Yesterday, 05:15 PM

This bug is so annoying because without Qt::MSWindowsFixedSizeDialogHint, it simply doesn't listen to what's in the code.

KevinH · Yesterday, 05:16 PM

That is what I feared. Yes they should all easily resize.

So hopefully DiapDealer can include the official Qt fix.

DNSB · Yesterday, 05:32 PM

Quote:

Originally Posted by KevinH

That is what I feared. Yes they should all easily resize.

So hopefully DiapDealer can include the official Qt fix.

That would be better than trying to work around the bug.

DiapDealer · Yesterday, 05:48 PM

I've patched/rebuilt the windows platform plugin after the fact one other time. It shouldn't be too big of a deal (he said with trepidation).

philja · Yesterday, 05:57 PM

I've tried 2.7.5 RC2 AppImage on my Linux UbuntuStudio 24.04 LTS. Tests were not exhaustive but I didn't see any problems in regular use nor with some plugins: testplugin, Tagmechanic, EpubCheck.

All 3 windows (About, Reports, Spellcheck) show the minimise, maximise, and quit buttons and they can all be resized by dragging. I checked on 2.6.2 and 2.7.0 and these versions too have all the buttons and can be resized. Frankly, I never noticed before and they don't affect my use much.

There was one weird detail, but that is not unique to 2.7.5 AppImage, it happens in 2.6.2 and 2.7.0 . When running tagmechanic, a small 'plugin runner' window opens up right in the middle of Code View with the main tagmechanic window over to the right (in the preview pane position). The plugin runner is in the way and obstructive. It can be resized and moved but doing so causes the Tagmechanic window to minimise. It can be resurrected from the task bar but I don't recall having this problem with other plugins.

DNSB · Yesterday, 06:03 PM

For me, the tagmechanic plugin runner window pops up in the middle of the Code View window but the tagmechanic window pops up over it so it doesn't bother me. I can drag the tagmechanic window elsewhere and it will pop up there until I move it again.

DiapDealer · Yesterday, 06:23 PM

I've never had any trouble with the Plugin Runner dialog being in front of the TagMechanic, but the Plugin Runner Window is always going to be present in some form (for every plugin). You can't move the TagMechanic Window to cover the minimal PluginRunner so you don't see it anymore? It should remember its position after that.

KevinH · Yesterday, 06:58 PM

Quote:

Originally Posted by BeckyEbook

This bug is so annoying because without Qt::MSWindowsFixedSizeDialogHint, it simply doesn't listen to what's in the code.

Yes it is very annoying and impossible to easily work around, which is why that Qt bug was given a Priority 1 rating by Qt. How this breakage got through even with only the most basic of testing by Qt is strange. Windows users have to be their largest customer base.

DiapDealer · Yesterday, 07:08 PM

Quote:

Originally Posted by KevinH

That is what I feared. Yes they should all easily resize.

So hopefully DiapDealer can include the official Qt fix.

The patch applied cleanly and everything works as it did previously! Give me a bit more time and I'll update my Qt6.10.2 bundle that is used for CI and include the patch in the source.

I'll attach the new qwindows platform plugin somewhere in case anyone wants to quickly get up to speed instead of redownloading the Qt6.10.2 bundle and expanding it just for one changed dll.

DNSB · Yesterday, 07:08 PM

If I am to believe some of the devs where I last worked, Qt did not have a customer base, they had an alpha tester base.

KevinH · Yesterday, 07:18 PM

Quote:

Originally Posted by DNSB

If I am to believe some of the devs where I last worked, Qt did not have a customer base, they had an alpha tester base.

I thought that changed when Qt stopped giving LTS updates to everyone to force money making commercial developers to buy a commercial support license from them. If they break releases I assume all the devs who make Qt-based projects for Windows are going to be upset. Commericial projects can not afford to be updating Qt every month just to get critical CVE bug fixes which is what most open source projects without a budget (like us) are forced to do. The opensources users of Qt are true forced guinea pigs!

We are just lucky there was one more upcoming public release of Qt 6.10.3 coming or we would have had to update to 6.11 or 6.12 just to get a critical fix.

DiapDealer · Yesterday, 07:26 PM

For anyone who builds their own Sigil on Windows and wants a quick fix, I'm attaching the patched, zipped up qwindows.dll file. It should replace the one in your Qt6.0.2 you use to build Sigil. It will go in the plugins/platforms/windows folder.

Do yourself a favor and delete/move the existing qwindows.dll and reboot before copying the new qwindows.dll to its home. I've had that damn thing stay in memory and make me think I'd lost my mind before.

You can also delete the one from your existing Sigil 2.7.5 installation and replace it with this new one to try it out. Just remember you may have to delete, reboot, then copy the new one.

DNSB · Yesterday, 07:32 PM

I seem to remember multiple complaints that every 3 bug fixes seemed to supply at least one new bug. The situation had improved by the time I retired but their testing framework was getting overly large and slow from originally taking 30 minutes or so and ending up with let it run over the weekend. This had the side effect of making any changes glacial—they would rather spend their time writing new code rather than debugging their tools.

DiapDealer · Yesterday, 07:35 PM

The new Qt6.10.2 bundle has been uploaded to my personal repo at

https://github.com/dougmassay/win-qt...s/tag/v5.212-1

Those who build their own Windows Sigil are free to download it. The github ci should now be using it to build working installers.

@Kevin, you may want to go ahead and revert your commit to try and force the About dialog to behave. Once that's done, a new Windows 2.7.5-RC build should be able to be created with github CI.

KevinH · Yesterday, 07:37 PM

Okay, I will do that now and create a Windows RC2 build and post it.

Yesterday, 06:03 PM	#51
DNSB Bibliophagist Posts: 50,380 Karma: 178402650 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	For me, the tagmechanic plugin runner window pops up in the middle of the Code View window but the tagmechanic window pops up over it so it doesn't bother me. I can drag the tagmechanic window elsewhere and it will pop up there until I move it again. Attached Thumbnails

Yesterday, 06:23 PM	#52
DiapDealer Grand Sorcerer Posts: 29,115 Karma: 211348980 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	I've never had any trouble with the Plugin Runner dialog being in front of the TagMechanic, but the Plugin Runner Window is always going to be present in some form (for every plugin). You can't move the TagMechanic Window to cover the minimal PluginRunner so you don't see it anymore? It should remember its position after that. Last edited by DiapDealer; Yesterday at 06:45 PM.

Yesterday, 07:37 PM	#60
KevinH Sigil Developer Posts: 9,393 Karma: 6686152 Join Date: Nov 2009 Device: many	Okay, I will do that now and create a Windows RC2 build and post it. Last edited by KevinH; Yesterday at 07:45 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
release candidate 0.2-rc6	lunohod	OpenInkpot	0	12-04-2009 06:24 PM
release candidate 0.2-rc5	dottedmag	OpenInkpot	50	12-04-2009 05:44 AM
release candidate 0.2-rc4	dottedmag	OpenInkpot	10	11-12-2009 01:35 PM
release candidate 0.2-rc3	dottedmag	OpenInkpot	10	11-05-2009 03:18 AM
release candidate 0.2-rc1	dottedmag	OpenInkpot	36	10-18-2009 01:07 AM

Yesterday, 05:15 PM	#46
BeckyEbook Guru Posts: 947 Karma: 3501230 Join Date: Jan 2017 Location: Poland Device: Various	This bug is so annoying because without Qt::MSWindowsFixedSizeDialogHint, it simply doesn't listen to what's in the code.

Yesterday, 05:16 PM	#47
KevinH Sigil Developer Posts: 9,393 Karma: 6686152 Join Date: Nov 2009 Device: many	That is what I feared. Yes they should all easily resize. So hopefully DiapDealer can include the official Qt fix.

Yesterday, 05:48 PM	#49
DiapDealer Grand Sorcerer Posts: 29,115 Karma: 211348980 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	I've patched/rebuilt the windows platform plugin after the fact one other time. It shouldn't be too big of a deal (he said with trepidation).

Yesterday, 05:57 PM	#50
philja Addict Posts: 329 Karma: 516 Join Date: Nov 2015 Location: Europe EEC Device: Kindle Fire HD6 & HD8	I've tried 2.7.5 RC2 AppImage on my Linux UbuntuStudio 24.04 LTS. Tests were not exhaustive but I didn't see any problems in regular use nor with some plugins: testplugin, Tagmechanic, EpubCheck. All 3 windows (About, Reports, Spellcheck) show the minimise, maximise, and quit buttons and they can all be resized by dragging. I checked on 2.6.2 and 2.7.0 and these versions too have all the buttons and can be resized. Frankly, I never noticed before and they don't affect my use much. There was one weird detail, but that is not unique to 2.7.5 AppImage, it happens in 2.6.2 and 2.7.0 . When running tagmechanic, a small 'plugin runner' window opens up right in the middle of Code View with the main tagmechanic window over to the right (in the preview pane position). The plugin runner is in the way and obstructive. It can be resized and moved but doing so causes the Tagmechanic window to minimise. It can be resurrected from the task bar but I don't recall having this problem with other plugins.

Yesterday, 07:08 PM	#55
DNSB Bibliophagist Posts: 50,380 Karma: 178402650 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	If I am to believe some of the devs where I last worked, Qt did not have a customer base, they had an alpha tester base.

Yesterday, 07:32 PM	#58
DNSB Bibliophagist Posts: 50,380 Karma: 178402650 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	I seem to remember multiple complaints that every 3 bug fixes seemed to supply at least one new bug. The situation had improved by the time I retired but their testing framework was getting overly large and slow from originally taking 30 minutes or so and ending up with let it run over the weekend. This had the side effect of making any changes glacial—they would rather spend their time writing new code rather than debugging their tools.

Yesterday, 07:35 PM	#59
DiapDealer Grand Sorcerer Posts: 29,115 Karma: 211348980 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	The new Qt6.10.2 bundle has been uploaded to my personal repo at https://github.com/dougmassay/win-qt...s/tag/v5.212-1 Those who build their own Windows Sigil are free to download it. The github ci should now be using it to build working installers. @Kevin, you may want to go ahead and revert your commit to try and force the About dialog to behave. Once that's done, a new Windows 2.7.5-RC build should be able to be created with github CI.

Advert

Advert