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

Record the relative time intervals between each key press #43

Open
2 tasks done
whoyawn opened this issue Feb 1, 2021 · 3 comments
Open
2 tasks done

Record the relative time intervals between each key press #43

whoyawn opened this issue Feb 1, 2021 · 3 comments

Comments

@whoyawn
Copy link

whoyawn commented Feb 1, 2021

Checklist

  • I use the latest release of atbswp
  • The issue is not existing yet

Verbose log

PASTE VERBOSE LOG HERE

Miscellaneous information

Operating System

Windows 10

Desktop Environment/Window Manager

Write here

Python version

3.9

Description

Currently, each keypress has a consistent delay in between and I'm trying to find a way to record the exact time in between them.

For example, if the script generated could look like this:

pyautogui.moveTo(2586, 674)
pyautogui.mouseDown(2531, 466, 'left')
pyautogui.mouseUp(2531, 466, 'left')
time.sleep(1)
pyautogui.keyDown('enter')
pyautogui.keyUp('enter')
pyautogui.keyDown('enter')
timer.sleep(.234) # DELAY
pyautogui.keyUp('enter')
timer.sleep(.333) # DELAY
pyautogui.keyDown('e')
pyautogui.keyDown('n')

It seems like the easiest way to do this would be to set a timer in between each record call, but if there's an easier way to do this, let me know.

@whoyawn whoyawn changed the title Record the relative time intervals between each key press? Record the relative time intervals between each key press Feb 1, 2021
@borderline23
Copy link

also muose movement speed will be great! thanks for your work

@bmn001
Copy link

bmn001 commented May 18, 2022

It looks like maybe this has been added?

I see things like "time.sleep(1)" and (2) in my scripts. Full-second delays are maybe not as granular as OP was hoping for, but it looks like there is support for it now.

@RMPR
Copy link
Owner

RMPR commented May 18, 2022

Yes, you're right. It was solved, and even made more accurate with #85 but since that commit has been merged, no release was made. I'll close the issue after making the release.

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

4 participants