-
Notifications
You must be signed in to change notification settings - Fork 26
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
#10 generation skipping some characters #20
#10 generation skipping some characters #20
Conversation
I will review this soon- super excited |
@jasonjmcghee This project is so pretty in its usefulness to size ratio. It's like the perfect solo open source project. I'm so jealous I didn't think of it first. 🤣 |
You're going to kill me, but I don't agree with the "Enter" change. That will break a lot of use cases, like typing into an input that triggers submit on enter |
Fwiw, definitely not the first to think of this, people reached out to me that said they built this before / 10 years ago etc. But I built a prototype and it was immediately useful to me, so I wanted to share! And hopefully find developers like you so we could make the project better together. |
no killing here. Wasn't super confident with it. Tell me if you can reproduce it tho. Feel free to edit that out of this PR. The top part fixes the missing text tho, or seem to anyway. |
I'm trying to understand why your changeset fixes it. The buffer should get joined and simulated at the end, after the Also, people were reporting this happening in the middle of text, not at the end... Can you spoon feed me why it fixes it? 😅 |
But it adds it to the buffer, which isn't cleared, so it should still be there for the next iteration once it has enough text 🤔 what am I missing 😂 I wonder if trying to simulate empty string it screwing with things? |
I reproduced it with your changeset: Screen.Recording.2024-02-01.at.6.29.43.PM.mov |
Was it the newlines that fixed it? I will try that too |
For what it's worth, my current supposition on this issue is something like the system is i/o blocking and enigo can't detect that and fails to enter the text. i plan to log an issue in the |
Something is up with my "fix". It definitely introduced the new line problem. I'm going to sleep on it. It's weird cuz, I tested it several times and diffed the text inserted against the text in the console. Hopefully, I've not wasted your time. |
Of course you haven’t. You taking the time to work on a fix is absolutely awesome- regardless of whether it ends up working! |
@jasonjmcghee You were on the money...
I couldn't get it out of my mind, so I had a theory in the middle of the night... "I wonder if enigo has an issue if the string starts with newline (maybe macos only)" I confirmed it this morning and hacked a workaround, but I'm at work and should wait to commit with my personal account. Not sure you want a semi-hacky workaround anyway.
|
@jasonjmcghee TLDR try out the latest version and look at the code. |
This is a workaround for an issue with enigo with strings that start with newline (maybe macos only?)
I made sure it never passes a string to enigo.text("\nbad") that started with a newline