Quote:
Originally Posted by KevinH
@Pargeo
If 4 people with 4 different Windows systems can use Ctrl+2 ... to switch keyboards successfully with no hangs or crashes with Sigil, then most likely this has probably something to do with a keyboard utility or driver that uses an older version of Qt but does not properly hide those symbols. That is why you are seeing this issue with just Sigil as it is probably the only other Qt based software you have running at that time.
Are you installing a particular keyboard driver or a keyboard related shell extensions into your Desktop Windows machine and Virtual machine systems?
Is there any way to boot your system into safe mode to temporarily disable your third party extensions to test for that.
Unless ... all of this was somehow fixed on the Windows side of things by an update they have but you do not?
Anything else you can tell us that might help someone recreate what you are seeing?
|
I gave up trying safe mode on my systems because both Windows installations (one is Windows 10 Pro that came from the machine, and the other one is out-of-the-box Windows 10 Home edition (UK version) both exhibit the same behaviour and they are totally different systems, with every update and every patch installed. The only common thing between these systems is Trados Studio 2019 installed on both of them, but it's a 32-bit system, and both Windows installations are 64-bit. (whether this Trados Studio is Qt based, I don't know.)
There aren't any other commonalities between them, except that they both have Ctrl+1 mapped to switch to UK English, Ctrl+2 to Russian and Ctrl+3 to Italian using standard Windows 10 functions.
Unfortunately, CTRL+ switches apparently don't work in Safe Mode (and I couldn't even start Safe Mode on my desktop, because my keyboard doesn't work in Safe Mode, so I cannot log in.