Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Desktop platforms: Mouse and Keyboard classes or DependencyServices #3739

@ToolmakerSteve

Description

@ToolmakerSteve

Description

There should be a standard way to query whether a physical keyboard exists, and if so, to use its functionality.

Similarly, there should be standard mouse detection, including screen position, down/move/up, and view/subview enter/exit/hover/tooltip.

Public API Changes

WPF, .NET Framework, and Windows Desktop all support System.Input.Keyboard class.

Expose this as MAUI.Input.Keyboard? Or in MAUI.Essentials as Device.Input.Keyboard?

See also Input Overview - WPF .Net Framework.

And the related Proposal for Mouse Input.

Would it make sense for this to be done as a DependencyService?

Intended Use-Case

Desktop platforms generally have a physical keyboard that does not require on-screen visibility.

Desktop apps traditionally have some "global" keys, that are not tied to a Focused element.

Or if they are associated with current VisualElement, perform some action other than changing Text.

Metadata

Metadata

Assignees

No one assigned

    Labels

    legacy-area-desktopWindows / WinUI / Project Reunion & Mac Catalyst / macOS specifics (Menus & other Controls))partnerIssue or Request from a partner teamproposal/opent/desktopThe issue relates to desktop scenarios (MacOS/MacCatalyst/Windows/WinUI/WinAppSDK)t/enhancement ☀️New feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions