Sigil-1.4.1 Released with Critical Fix

[Turtle91]

I have also seen the wait-cursor get "stuck". IIRC it was after I cancel out of some operation. I can't remember if it was only plugin's or when I had right-clicked on a file in the book browser. It did stay "stuck" until I restarted Sigil, then it was fine. It is definitely NOT something that would hold up a critical release - just an annoyance.

I'll try and get it to reoccur and post my steps.

[KevinH]

So is there anything we can do in Sigil code or python plugin code to make that spinning disk go away?

Originally Posted by Doitsu

The spinning blue disk cursor is a generic Windows system cursor that can be displayed for any number of reasons.

[DiapDealer]

For the record, Qt itself is almost always riddled with cursor bugs. We've been using the same Qt build for several releases, so it's not inconceivable that that version has more than its fair share of cursor-related glitchiness. Any PyQt5 plugins would be susceptible to those same bugs since they share the same Qt libraries that Sigil itself uses.

[KevinH]

Please post any follow-ups on the Sigil 1.4.2 Release thread not here.

And sorry for the two quick follow-on critical update releases. We will try to do better next time but two bug fixes since Sigil 1.3.0 seemed to have impacts outside of the fix itself we had not foreseen.

[julid]

Ah! Okay. Thank you, folks. I haven't had Windows 10 long and this was the first time I've seen that notice. I'm glad to know everything's "ok". I'll go ahead and use the file then (yes, I did get it from your site Kevin H. Just don't know all Windows 10 funkiness yet! )

Originally Posted by Doitsu

Brand-new files will often trigger this warning on Windows 10 machines. If you're worried about viruses you can always visit Virustotal, click the URL link, paste the link to the installer in the box and click the magnifier icon.
You'll then see that not a single antivirus program thinks that the installer is infected.
You can also click here to the see the results for the Sigil 1.4.1 installer.

[Thasaidon]

Originally Posted by KevinH

Please post any follow-ups on the Sigil 1.4.2 Release thread not here.

And sorry for the two quick follow-on critical update releases. We will try to do better next time but two bug fixes since Sigil 1.3.0 seemed to have impacts outside of the fix itself we had not foreseen.

KevinH You and Diapdealer are doing a great job Do not worry about it. No reasonable person expects omniscience from you two.

Though it sometimes seems....

[Monaghan]

Originally Posted by KevinH

Yes just rename sigil.ini and let Sigil create its own new version. Please try to generate a debug log file of a crash by setting the SIGIL_DEBUG_LOGFILE environment variable.

Originally Posted by Turtle91

I think all you have to do is rename the existing sigil.ini into something else like sigil.bak. Then reopen Sigil and it will create a new .ini if it can't find the old one.

This seems to have solved the issue, touch wood. Thank you for the help, both.