Quote:
Originally Posted by KevinH
Thank you for your bug report:
I wish more people would report crashes when they happen so that they can be tracked down and eliminated. It can only help.
Repeatable crashes can always be fixed if we can recreate them.
I added 3 keyboard layouts to my mac and changed them when Sigil was running with no difficulties. I even modified the change keyboard layout shortcut to match the default Ctrl+2 (h2 Sigil shortcut) to match your case. The Ctrl+2 key event is properly intercepted by the OS which properly changes the keyboard layout. That shortcut never reaches the Sigil app at all. No issues whatsoever.
So whatever is causing this is Windows or system specific and does not happen with macOS.
Is anyone else who uses Linux or Windows seeing similar crashing when changing keyboard layouts?
We will need more info please to track this down:
1. What keyboard layouts do you have installed? Which one causes the crash?
2. What else on your system uses the Ctrl+2 shortcut?
3. Have you tried rebooting Windows into safe mode to prevent broken shell extensions from loading?
4. Does the problem keyboard layout use a different IM or result in a different keyboard driver being used?
5. Have you tried changing the keyboard change shortcut key Ctrl+2 sequence to something else to see if that impacts the issue?
Any details that could help us recreate the crash would be very useful.
Thanks,
KevinH
|
Hi again, sorry for a late reply,
I've just tested Sigil 1.9.20 for Windows on two machines - a plain vanilla Windows 10 desktop and a Macbook Pro with Sigil installed on Windows 10 installed through Parallels (both have almost the same set of languages (keyboards) installed: UK English (Ctrl+1), Russian (Ctrl+2), Italian (Ctrl+3) and French (Ctrl+4) - only on the desktop. On both systems, hitting Ctrl+2, Ctrl+3 (and Ctrl+4 on the desktop) while in Sigil causes its crash, while Ctrl+1 does not. Selecting a required language using any other method (status bar, touch bar etc.) does not cause a crash (Hitting a 'non-assigned' Ctrl+number combination on both machines does not cause a crash, i.e. Ctrl+4 on MBP + Windows + Parallels does not.)
NB it's only Sigil that crashes when I hit these CTRL+number combinations, any other software works perfectly.
I haven't checked the machines in Safe Mode, the first one because its keyboard driver seems not to be compatible with Safe Mode and only works in the normal mode, and as for the second machine, well, I believe since these two machines are completely different in every way, except for being set for CTRL+ combinations turning on a specific IME, the problem is not in the hardware.
Please note that in order for this experiment be clear, I disabled Sigil-own CTRL+ shortcuts on both machines, but, as you see, this didn't help.
I tried to change the shortcut keys for my languages from CTRL+number to Left Alt-Shift+number. This combination works on both machines without causing any crash. (neither Ctrl+number, nor Left-Alt+number)
Unfortunately, I cannot use it, because it requires pressing three keys and not two and it's really inconvenient for me (my work depends on the speed of typing) and I will not keep this new 'working' shortcuts on either machine.
I hope this helps.