← Back to team overview

sikuli-driver team mailing list archive

[Bug 1466231] Re: KeyModifier being sent to Sikuli, not to app

 

You should try again with the build from today (2015-06-19).

In any case you should move the generated SikuliX.app to /Applications.

If it does not work running the script from the IDE started as app
(double clicking SikuliX.app or run from Launchpad), then you can try
out running your script from command line.

Another option is to start the IDE using the provided scripts:
- doubleclick runsikulix
- in a Terminal use runsikulix (if you want to provide parameters)
- in a Terminal use /Applications/SikuliX.app/run (equivalent to runsikulix)

especially with OS X 10.10 there are some odd behaviours (partly known
Mac issues) when using the IDE started as application.


** Summary changed:

- KeyModifier being sent to Sikuli, not to app
+ [1.1.0] OS X 10.10: KeyModifier being sent to Sikuli, not to app

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1466231

Title:
  [1.1.0] OS X 10.10: KeyModifier being sent to Sikuli, not to app

Status in Sikuli:
  New

Bug description:
  Not yet attempted in Sikuli 1.0.1.

  OS: Mac OSX Yosemite (10.10.3)

  METHOD:
  Script is as follows:
  App.focus("NameOfApp");
  type("r"); # just to confirm that the app has focus
  type("o", KeyModifier.KEY_CMD); # Cmd-O to open a file

  RESULT:
  After the second line, the app reacts to the letter R correctly, proving that the app has focus. However, the Cmd-O opens Sikuli's File Open dialog, not my product's.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1466231/+subscriptions


References