Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Screen recorder gives problematic SendKeys codes with DosBox #291

Open
mfasold opened this issue May 23, 2022 · 0 comments
Open

Screen recorder gives problematic SendKeys codes with DosBox #291

mfasold opened this issue May 23, 2022 · 0 comments

Comments

@mfasold
Copy link

mfasold commented May 23, 2022

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.

taskr-screenshot

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant