You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not an expert in sdef or the underlying APIs here, but children elements of classes are a pretty big gap in the generated type definitions.
For example, the System Events application (Application('System Events')) has at least 4 defined child elements:
In most (all?) cases, these are accessible in at least 3 ways:
Application('System Events').processes();// returns arrayApplication('System Events').processes['TextEdit'];// alias for processes.byName('TextEdit')Application('System Events').processes[0];// alias for processes.at(0)
If the generated types just included these methods for accessing children, it would make this 1000% more useful for UI automation. System Events relies heavily on child elements.
Thanks!
The text was updated successfully, but these errors were encountered:
If only we could figure out the function signature of the elusive parameterTypeForNameInCommands(), the translated definitions could be obtained within their own execution environment...
I'm not an expert in sdef or the underlying APIs here, but children elements of classes are a pretty big gap in the generated type definitions.
For example, the System Events application (
Application('System Events')
) has at least 4 defined child elements:In most (all?) cases, these are accessible in at least 3 ways:
If the generated types just included these methods for accessing children, it would make this 1000% more useful for UI automation. System Events relies heavily on child elements.
Thanks!
The text was updated successfully, but these errors were encountered: