Quote:
Originally Posted by KevinH
It does.
1. If changing to a different shortcut still works to change keyboard layout without any crashing of Sigil, the actual changing of the keyboard layout itself can not be the underlying cause of the crash. Keyboard layouts can be changed successfully even by shortcut with no crashes.
2. Assuming Ctrl+2 works properly on Sigil to make text h2 (when *not* assigned to change keyboard layouts), the actual shortcut is not the problem either.
Given 1 and 2 that implies that Ctrl+2 is probably changing something else on your system besides just the keyboard layout (perhaps changing tabs, changing os workspaces, changing monitors, or ...) which is what is giving Sigil fits and causing the crash.
What bothers me is that if no keyboard layout (say the 4th) exists then Ctrl+4 does nothing (no crash at all) so that is inconsistent in that it implies some relation with changing keyboard layouts and Sigil which is inconsistent with the above.
Is there any error message at all?
Are you 100% sure it is a crash and not just hiding the Sigil window someplace off screen on another workspace or monitor or quitting out of Sigil? Have you tried checking the task manager to verify the program has exited completely?
Also just to rule out QtWebEngine, can you please try reproducing the crash when Preview has been turned off (use the Sigil View menu to hide it)? Does that change anything?
Addendum:
A search of the web showed some hits for similar issues on Windows 10 with other software including Excel, Office 365, and etc.
See for example:
https://adobe-video.uservoice.com/fo...s-aftereffects |
Hi,
I just tried Sigil with Preview closed - and it crashed again.
The crash message is (not responding) on Sigil's window top and then, when I close it, it says 'Sigil.... is not responding. .. Close the program | Wait for the program to respond. In short, a usual window when you try to close up a program that freezes up.
As for precedents, I remember I got a very similar effect on a version of MS Office, but it was ages ago (at least 10 years ago, or maybe more.). It was similar, but a little bit different - I'd open an Office program and first of all use a task bar to switch to any other language, and once I did that, every subsequent Ctrl+ would not cause any crash. (I remember I wrote to MS several times about it, but didn't obtain any reply.)
I tried to do the same with Sigil, but, alas, it doesn't work - even if I use a different method for switching IMEs first, any subsequent Ctrl+ (assigned to kbd changing) causes a crash.