sikuli-driver team mailing list archive

[Devin <question818044@xxxxxxxxxxxxxxxxxxxxx>]

New question #818044 on SikuliX:
https://answers.launchpad.net/sikuli/+question/818044

Sorry if this is a duplicate. I searched the bugs but didn't find anything. I'm not sure if this should be a bug or a question. Thank you for your patience/guidance.

We've been using a snapshot of 2.0.6 for macOS testing on ARM (sorry I don't know exactly what version, let me know how to get this if needed and I will dig it up).

One thing we noticed is that every time we modify an existing test and save it with the 2.0.6 snapshot, the formatting for "similar" changes.

For example, with 2.0.5 we might have something like this:
click(Pattern("1591809287470.png").similar(0.90))

with the 2.0.6 snapshot, it would instead be changed to the following (note the 0 in front of the 0.90 was dropped):
click(Pattern("1591809287470.png").similar(.90))

The only real issue with this, for us, is that it makes code reviews frustrating since many lines will be flagged as changed, when in fact they are the same (minus the dropped 0).

What we've been doing as a workaround, is we modify the projects using snapshot 2.0.6, test them on macOS ARM, then copy/paste them to a Windows machine with 2.0.5, open the .sikuli project, modify it by adding a space, then delete the space, then save it. This will add all of the missing 0's back.

Then when we review changes, we see only things that were changed instead of all the additional lines with this formatting change.

-- 
You received this question notification because your team Sikuli Drivers
is an answer contact for SikuliX.