sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #19158
Re: [Question #232139]: observe quitting long before it should
Question #232139 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/232139
Tames McTigue posted a new comment:
Hi RaiMan,
Thank you for the tips, you may be right that there is a better way of
doing this. The reason I am doing it this way is the fact that the
dialog pages can be completely different depending on which OS and which
features are chosen. I thought this would be a quick way of accounting
for all of the patterns. Your way would probably be better overall since
I'd know if something doesn't show up that I'm expecting to.
I do however think this is a bug. I wasn't aware that it would stop once
it sees every onAppear image. To make sure this isn't happening, I used
an image that there is no way would show up for one of the onAppear
images. It still quits even though it should not. I ran it from the
command line with d:3 and it doesn't give me any more information than
the GUI does. Just shows it running the first few handlers like it
should, then "[info] Exit code: 0".
--
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.