Comment 5 for bug 1362011

Both situations (auto capture as default and cannot-capture-menu-entries) are different things.

The first belongs to the usage, that you are working in the IDE and either use a CommandList entry with auto capture on or one of the capture buttons (inline with auto capture off or the tool bar button). In this case it will not be possible with standard OS X applications to capture menu entries, since the last click will be in the IDE, which switches focus and closes any open menu.

So as long as I know Sikuli (since 2009), you always had to use the capture hotkey, to have a chance to get menu images with the means of the IDE (which is the second area).

The alternate way (using the OS X capture feature and insert the image) always worked in the past.

BTW: the command list is only for absolute beginners and something like a poor man's auto completion. People writing more complex scripts will usually assign images to variables and use one of the new IDE features (compact image buttons and pure text editing) or even work with a mature IDE like Eclipse.

Nevertheless: the capture feature will be revised with version 1.2 anyway and if I succeed in implementing some auto completion, then this will be the end of the command list (which already now can be switched off completely)