sikuli-driver team mailing list archive

[RaiMan <question685378@xxxxxxxxxxxxxxxxxxxxx>]

Question #685378 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/685378

    Status: Open => Answered

RaiMan proposed the following answer:
Using sikulixapi.jar in a Java project: these are the defaults after startup in org.sikuli.basics.Settings:
  public static boolean ActionLogs = true;
  public static boolean InfoLogs = true;
  public static boolean DebugLogs = false;
  public static boolean ProfileLogs = false;
  public static boolean TraceLogs = false;
  public static boolean LogTime = false;

  public static boolean UserLogs = true;
  public static String UserLogPrefix = "user";
  public static boolean UserLogTime = true;

 -Dsikuli.Debug=3 currently does not do anything in your situation.

So only  Settings.LogTime = true; would be needed in this case.

if you want to see the SikuliX internal debug logs, you have to say 
Debug.on(3);
before using any SikuliX feature.

This is an example:

        Settings.LogTime = true;
        Debug.on(3);
        Debug.user("userlog *****");
        new Screen().click();

produces:

[user (24/10/2019, 20:47:03)] userlog *****

............ internal debug messages .........

[107 debug (24/10/2019, 20:47:05)] CLICK on L[640,400]@S(0) (1202 msec)

............ internal debug messages at termination .........

conclusion:
so only:

        Settings.LogTime = true;
        Debug.on(3);

is needed, to get similar output to the 1.1.3 situation.

I accept and register as a bug, that there are differences and
-Dsikuli.Debug=3 does not work as expected.

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