Dynamic Pointer Mode Switching for Remote Desktop Contexts

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional user devices struggle to seamlessly transition between native pointer mode and desktop-class pointer mode in response to context changes, such as establishing or closing remote desktop sessions, which can be cumbersome for users and disrupt workflow.

Innovation Solution

Implementing a dynamic switching mechanism that automatically transitions between native and desktop-class pointer modes based on real-time context changes, such as launching or terminating remote desktop sessions, using input devices like external mice, and managing cursor visibility and control between local and remote applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the user device uses native pointer mode for local applications, then the operation is simple and direct, but it cannot access remote desktop session resources

Engineering Contradiction:
Improveaccess to remote desktop resourcesVSAvoidpointer mode management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system dynamically switches between native pointer mode and desktop-class pointer mode based on the active context (local application vs. remote desktop session). The pointer mode is not static but adapts in real-time to user needs, automatically transitioning when applications are launched or closed.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The pointer system is designed to serve multiple functions: it can operate in native mode for local applications and in desktop-class mode for remote desktop sessions. A single pointer infrastructure handles both local and remote resource access, eliminating the need for separate pointer systems.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If the user manually switches between pointer modes, then control is precise, but workflow is disrupted and user burden increases

Engineering Contradiction:
Improveworkflow efficiencyVSAvoidmanual mode switching
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system automatically detects context changes (application launch/closure) and self-manages the pointer mode transitions without requiring user intervention. The pointer mode switching is handled autonomously by the system based on monitored application states.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system continuously monitors application states and uses this feedback to determine when to switch pointer modes. When a remote desktop session application is detected as active, the system switches to desktop-class pointer mode; when closed, it returns to native pointer mode.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If the device maintains desktop-class pointer mode continuously, then remote desktop access is enabled, but native application control is lost

Engineering Contradiction:
Improveremote desktop accessVSAvoidlocal application control
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The pointer mode dynamically adapts to the active context rather than remaining static. The system switches between native and desktop-class pointer modes based on whether a remote desktop application is active, ensuring optimal control for the current task.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11487559B2Dynamically switching between pointer modes
Publication Date: 2022.11.01 CITRIX SYSTEMS INC
  • US11487559B2 patent drawing
  • US11487559B2 patent drawing
  • US11487559B2 patent drawing

AI summary

Techniques process, in a user device, pointer input from an input device. Such techniques involve providing the input from the input device to a remote desktop session which is hosted on equipment that is remote from the user device. Such techniques further involve detecting an event on the user device, the event being indicative of deactivation of the remote desktop session. Such techniques further involve, in response to detecting the event, providing the input from the input device to at least one local application executable on the user device to enable continued processing of the input from the input device with use of the at least one local application instead of the remote desktop session.