Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update tests and comments once a Windows version which can fail IsOpcodeSupported is released #77

Open
beweedon opened this issue May 11, 2021 · 0 comments
Open

Update tests and comments once a Windows version which can fail IsOpcodeSupported is released #77

beweedon opened this issue May 11, 2021 · 0 comments

Comments

@beweedon
Copy link
Contributor

No description provided.

beweedon added a commit to beweedon/Microsoft-UI-UIAutomation that referenced this issue May 11, 2021
@beweedon
Add IsOpcodeSupported support to WinRT and C++ wrappers
dc487cf 
IsOpcodeSupported is an API provided by CoreAutomationRemoteOperation
which determines whether a given remote operation opcode is supported by
the current provider connection. Which opcodes are supported depends on
both the client and provider UIA versions.

This change simply plumbs IsOpcodeSupported through
Microsoft.UI.UIAutomation and UiaOperationAbstraction. A more elegant
design taking advantage of the characteristics of each wrapper can be
made in the future.

For UiaOperationAbstraction, we always return true from
IsOpcodeSupported in the local case.

Note, IsOpcodeSupported will throw E_FAIL on future versions of Windows
when no connection has yet been established. Once such versions of
Windows are released, we should update tests and comments with the
specifics. This is tracked by issue microsoft#77.
@beweedon beweedon mentioned this issue May 11, 2021
Merged
beweedon added a commit that referenced this issue May 17, 2021
@beweedon
Add IsOpcodeSupported support to WinRT and C++ wrappers (#78)
451f315 
IsOpcodeSupported is an API provided by CoreAutomationRemoteOperation
which determines whether a given remote operation opcode is supported by
the current provider connection. Which opcodes are supported depends on
both the client and provider UIA versions.

This change simply plumbs IsOpcodeSupported through
Microsoft.UI.UIAutomation and UiaOperationAbstraction. A more elegant
design taking advantage of the characteristics of each wrapper can be
made in the future.

For UiaOperationAbstraction, we always return true from
IsOpcodeSupported in the local case.

Note, IsOpcodeSupported will throw E_FAIL on future versions of Windows
when no connection has yet been established. Once such versions of
Windows are released, we should update tests and comments with the
specifics. This is tracked by issue #77.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@beweedon