I have been recording a skript while running a DosBox program, and observed the following issues with the recorded Send Keystrokes sequences:
It records keys that later will yield an error on execution, e.g. "{LWin}"
Key combinations will be recorded as key sequences, e.g. {LControlKey}{F5} instead of ^{F5} when pressing CTRL-F5
Some key combinations will not be recorded at all, e.g. ALT-G
Some keys will be not correctly translated, e.g. " " instead of "{SPACE}"
Additionally I saw the previoulsy observed issue #124 and cases where the XML could not be saved following a screen recording due to characterer encoding problems (see screenshot below). However, both of those issees were not seen when I only recorded keyboard input in the recording, deactivating all other checkboxes in the screen recorder options.
Please excuse my ignorance if above behaviour is expected or already known in my setting. Note that used taskt 3.5.0.0 on Windows 10 Pro.
I have been recording a skript while running a DosBox program, and observed the following issues with the recorded Send Keystrokes sequences:
Additionally I saw the previoulsy observed issue #124 and cases where the XML could not be saved following a screen recording due to characterer encoding problems (see screenshot below). However, both of those issees were not seen when I only recorded keyboard input in the recording, deactivating all other checkboxes in the screen recorder options.
Please excuse my ignorance if above behaviour is expected or already known in my setting. Note that used taskt 3.5.0.0 on Windows 10 Pro.