-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
windowOpened fires too quickly #5
Comments
Hi @Omzig, thank you for alerting me to this issue. Yeah there is a little bit of delicate timing when interacting with this UI. I already have seen this type of issue when finding the Since this race turns out differently on my computer and yours, can I send you a debug build that logs which step is the problem, and you can tell me which error message you see? Once we know which element isn't being found in time, I can add retry logic to fix it. |
ya, my corporate environment is quite strict, but i can tell you what line gets a null Extensions.cs public static IEnumerable<AutomationElement> children(this AutomationElement parent) {
if(parent == null)
{
return null; //this is where i traced it to, that led me to putting in the delay. Funny thing, when i am in debug, it works because debug slows it down, but then when i run it as normal, it gets kranky.
}
return parent.FindAll(TreeScope.Children, Condition.TrueCondition).Cast<AutomationElement>();
} |
Interesting, that is a method that gets retried when it throws an exception (for example if Can you try changing the |
Hi, I am getting the same issue, I am also not sure why this happens because it is in a try loop. |
Thanks for the additional info. I will try reproducing it on more computers, and also upload a development build that both increases the timeout and prints log messages, which may be useful for spotting the cause. At this point there is still something I am not understanding about the root cause here, because the given workaround doesn't seem like it should change the behavior, so there's more to it than I currently can see. |
This issue did not reproduce on two additional computers I tested with. Here is a development build with a longer timeout for finding You can try this out and let me know if it fixes the problem, and what the stdout is. Here is what I'm expecting:
|
Yes thanks, it is working nicely now
|
Thank you very much, adding this fix to the upcoming 0.2.0 release. |
Released in 0.2.0. |
Problem
nothing happens when the exe is running
Solution
put a pause in and wait for the window to open before selecting the usb key option
The text was updated successfully, but these errors were encountered: