RPA.Windows.Get Elements does not support executable locator type

[CodexEmpirium]

Running a basic test, where I have a known executable already detected using 'regex' and 'type' locators. Then I added 'executable' locator to prevent scanning desktop but to focus only within the executable, results in the following warning in the debug console:

[ WARN ] Invalid locator strategy "locator='executable"! (assuming 'name')

I have double-checked the code, I did not add an extra ' in front of executable, the warning is generated based on this line of my code:

@{AsdfStartupElements} = Wait Until Keyword Succeeds 10 6 RPA.Windows.Get Elements locator=executable:AsdfConfigurator.exe and regex:"Configuration in directory.*" and type:WindowControl search_depth=10 timeout=9

[mikahanninen]

The `executable:` locator strategy is fully supported (see `_WINDOWS_LOCATOR_STRATEGIES` and `_get_control_with_locator_part` in `packages/core/src/RPA/core/windows/locators.py`) — this isn't a missing feature.

The warning text you saw, `Invalid locator strategy "locator='executable"!`, shows the actual issue: a literal `locator='` prefix (from the keyword's named-argument syntax plus a stray quote) ended up glued onto the strategy token during parsing, so it was tokenized as `locator='executable` instead of `executable`. This is a real tokenizer weakness — the parser had no defense against that kind of stray text.

Fixed in #1343: the tokenizer now strips a leading `locator=` prefix (case-insensitive) and any unmatched leading quote before matching the strategy, with a clearer warning if that happens. Should resolve your case once merged and released (`rpaframework-core` 13.0.2).