[Sikuli-driver] [Question #686982]: Save image match data to metadata file
New question #686982 on Sikuli: https://answers.launchpad.net/sikuli/+question/686982 Hello, we have been using Sikuli for almost a year now and it has made our automation for a Unity based game much better. One issue we do have is the game is a 2d style design which consist of majority UI. The problem is the game is constantly getting updated graphics wise. The location of a button and where its at and the size of it always stays the same for the most part but the graphics will be updated with a new design and such. This requires me to go back through and recapture most of the images which is in the 1,000's at this point. So I was wondering if had any recomendations on how to save the last successful match to a properties file named the same as the image. Then when I had this feature enabled if it fails to find a match then it would proceed to read the region info and make a new capture in the same location the last match was found and add it to the current folder its going through looking for the image. There will be some images that are supposed to not return a match, but I planned to include a argument with it that tells the function whether this is a image that needs to be recaptured when that feature is enabled. Is there any suggestions on how to handle this? I wanted to make sure I wasnt over complicating it by taking the match it just found and saving that xyz etc to a file named the same but with dfferent extension. Then when capturing used the built in capture to capture the new image and save it. FYI: All of our code is in Java. Thanks for any suggestions they are much appreciated -- You received this question notification because your team Sikuli Drivers is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Bug 1476773] Re: [1.1.0] observe: setInactive/setActive not working --- use 1.1.4+
** Changed in: sikuli Status: Fix Released => In Progress ** Changed in: sikuli Importance: Undecided => High ** Changed in: sikuli Milestone: None => 2.0.2 ** Summary changed: - [1.1.0] observe: setInactive/setActive not working --- use 1.1.4+ + [2.0.1] observe: setInactive/setActive not working ** Summary changed: - [2.0.1] observe: setInactive/setActive not working + [2.0.1] observe: setInactive/setActive not working --- to be checked -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1476773 Title: [2.0.1] observe: setInactive/setActive not working --- to be checked Status in Sikuli: In Progress Bug description: Hi again. Im writting a code that will check if an image appeared on a Region. After the image appears the program will scan the same region to see if it desappears. When the image desappears it will start to scan to see if it appears again, and so on. So, im using OnAppear and OnVanish on the same region with a single handler. (calling Repeat() in the end) The problem with this solution is that the handler will continue to be called with type = APPEAR even if the handler was already triggered one time with APPEAR. The same happen when the image disappears and the handler is called with type = VANISH. It will continue to be called with VANISH until the image appears again. Is there a way to avoid this? Is it possible to unregister OnAppear/OnVanish and register it again in a Region? Do i have to use two different regions with the same dimmensions? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1476773/+subscriptions ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Bug 1855413] Re: Issue in SikuliX while running script in remote desktop.
[40337 debug] Region: wait: waiting 3.0 secs for C:\Users\sttester\Desktop\Sarthik\sikulix\images\DNA\Login\check\DNALoginSecurityMessageNew.PNG to appear in R[0,0 1920x1080]@S(0) [40509 debug] Finder2: makeMat: INT_RGB (1920x1080) [40634 debug] Finder2: makeMat: TYPE_4BYTE_ABGR (97x18) [40900 debug] Finder2: doFind: start (stdDev: 223.4544 mean: 664.706186) [41822 debug] Finder2: doFind: in original: %49.5025 (?70) 719 msec [41884 debug] Finder2: doFind: end 781 msec [42056 debug] Finder2: makeMat: INT_RGB (1920x1080) [42119 debug] Finder2: doFind: start (stdDev: 223.4544 mean: 664.706186) [43025 debug] Finder2: doFind: in original: %41.0638 (?70) 813 msec [43119 debug] Finder2: doFind: end 907 msec [43275 debug] Finder2: makeMat: INT_RGB (1920x1080) [43306 debug] Finder2: doFind: start (stdDev: 223.4544 mean: 664.706186) [43853 debug] Finder2: doFind: in original: %100. (?70) 547 msec [43916 debug] Finder2: doFind: end 610 msec [43978 debug] Region: wait: C:\Users\sttester\Desktop\Sarthik\sikulix\images\DNA\Login\check\DNALoginSecurityMessageNew.PNG appeared (M[229,153 97x18]@S(0) S:1.00 C:277,162 [3641 msec]) [44072 debug] Device: Mouse: moved externally: now (596,247) was (596,246) (mouseMovedResponse 0) [44650 debug] TYPE "#ENTER." [44650 debug] Region: TYPE "#ENTER." -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1855413 Title: Issue in SikuliX while running script in remote desktop. Status in Sikuli: New Bug description: We have an automation framework using sikulix and Java. We have handled different resolution by using different set of resolution for some standard resolution. But there is some crazy behavior when we run this script in remote desktop. My system screen size is 1280*720. Remote desktop screen size was 1980*1280. When i run script in remote desktop it identifies images but clicks in some other location(I'm sure that proper image was recognized). Any help to fix this issue would be appreciated. Client machine : windows 10, 64 bit. To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1855413/+subscriptions ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Question #269185]: Status of bug #1476773 changed to 'In Progress' in Sikuli
Bug #1476773 status changed in Sikuli: Fix Released => In Progress https://bugs.launchpad.net/sikuli/+bug/1476773 "[1.1.0] observe: setInactive/setActive not working --- use 1.1.4+" This bug is linked to #269185. OnAppear and OnVanish on the same region https://answers.launchpad.net/sikuli/+question/269185 -- You received this question notification because your team Sikuli Drivers is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #269185]: OnAppear and OnVanish on the same region
Question #269185 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/269185 RaiMan proposed the following answer: ok, I have to put the bug alive again and check. -- You received this question notification because your team Sikuli Drivers is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Bug 1855413] Re: Issue in SikuliX while running script in remote desktop.
there are some lines missing in the log after the error -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1855413 Title: Issue in SikuliX while running script in remote desktop. Status in Sikuli: New Bug description: We have an automation framework using sikulix and Java. We have handled different resolution by using different set of resolution for some standard resolution. But there is some crazy behavior when we run this script in remote desktop. My system screen size is 1280*720. Remote desktop screen size was 1980*1280. When i run script in remote desktop it identifies images but clicks in some other location(I'm sure that proper image was recognized). Any help to fix this issue would be appreciated. Client machine : windows 10, 64 bit. To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1855413/+subscriptions ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #269185]: OnAppear and OnVanish on the same region
Question #269185 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/269185 panadol007 proposed the following answer: @Raiman, Thanks for the quick respond, I'm currently using SikulixIDE 2.0.1 Remote Desktop into Windows 7 -- You received this question notification because your team Sikuli Drivers is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #269185]: OnAppear and OnVanish on the same region
Question #269185 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/269185 RaiMan proposed the following answer: @panadol007 as mentioned in the related bug: use 1.1.4+ ... which currently is 2.0.1 -- You received this question notification because your team Sikuli Drivers is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
