3D input device function mapping

• US 20060152495A1
• Filed: 10/21/2002
• Published: 07/13/2006
• Est. Priority Date: 03/12/2002
• Status: Abandoned Application

• Current Assignee: 3DCONNEXION GmbH (Logitech International SA)
• Original Assignee: 3DCONNEXION GmbH (Logitech International SA)
• Inventors: Gombert, Bernd
• Application Number:
  US10/513,001
• Publication Number:
  US 20060152495A1
• Time in Patent Office: Days
• US Class Current: 345/172
• CPC Class Codes: G06F 3/03543 Mice or pucks G06F3/03541 takes precedence
• CPC Class Codes: G06F 3/038 Control and interface arrangements therefor, e.g. drivers or device-embedded control circuitry
• CPC Class Codes: G06F 3/0481 based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
• CPC Class Codes: G06F 3/04815 Interaction with a metaphor-based environment or interaction object displayed as three-dimensional, e.g. changing the user viewpoint with respect to the environment or object
• CPC Class Codes: G06F 3/0486 Drag-and-drop
• CPC Class Codes: G06F 9/4411 Configuring for operating with peripheral devices; Loading of device drivers

Abstract

A method for mapping functions of a multi-dimensional input device is proposed, wherein a graphical representation of a button or an other degree of freedom of the input device (130, 140, 150) is displayed on a screen or monitor. Furthermore at least one available driver function for the input device (130, 140, 150) is displayed. A selected function can be mapped by a user to a button or other degree of freedom of the input device (130, 140, 150) by graphically associating the specific function with the button or degree of freedom.

Claims

1. A method for mapping functions of a multi-dimensional input device, operatively connected to a monitor, the method comprising the following steps:

displaying a graphical representation of a button or an other degree of freedom of the input device (130, 140, 150),

displaying at least one available driver function for the input device (130, 140, 150), and

mapping a selected function to a button or other degree of freedom of the input device (130, 140, 150) by graphically associating the specific function with the button or degree of freedom.

2. A method-according to claim 1, characterized in that the driver function is an event triggered upon activation of the associated button or other degree of freedom of the input device (130, 140, 150).

3. A method according to claim 1 or 2, characterized in that the step of graphically associating the specific function with the button or degree of freedom is implemented by drag-and-dropping.

4. A method according to anyone of the preceding claims, characterized in that upon an event, the buttons and/or other degrees of freedom of the input device (130, 140, 150) are automatically identified (240) and displayed.

5. A method according to anyone of the preceding claims, characterized in that upon an event, the buttons and/or other degrees of freedom of the input device (130, 140, 150) are automatically named.

6. A method according to anyone of the preceding claims, characterized in that the mapping is carried out application-selective, i.e. an application program is associated with each mapping.

7. A method according to claim 6, characterized in that available application programs are identified and displayed for the mapping.

8. A method according to claim 7, characterized in that only running application programs are identified and displayed for the mapping.

9. A method according to anyone of the preceding claims, characterized in that the mapping is stored in a configuration file (265) such that it can be re-used throughout a network.

10. A method according to anyone of the preceding claims, characterized in that the mapping is stored in a device driver (220).

11. A method according to claim 9 or 10, characterized in that an application program is stored associated with a mapping.

12. A method according to anyone of the preceding claims,. characterized in that when physically manipulating the input device in a degree-of-freedom, the manipulated degree-of-freedom is graphically illustrated to facilitate the mapping operation.

13. A method according to claim 12, characterized in that the graphical illustration is carried out by means of a 3d -graphical feedback.

14. A method according to anyone of the preceding claims, characterized in that when physically manipulating the input device in a degree-of-freedom, the manipulated degree-of-freedom is activated for a following mapping operation.

15. A multi-dimensional input device driver mapping software, characterized in that it supports a method according to anyone of the preceding claims when running on a computing device.

16. A computer-readable medium characterized in that it has recorded thereon a software according to claim 14.

17. A multi-dimensional input device having a mapping configuration module (200), the mapping configuration module (200) comprising:

a feedback interface (297) for controlling a display device (120) to display a graphical representation of a button or other degree of freedom of the input device (130, 140, 150), and to display at least one available driver function (220) for the input device (130, 140, 150), and

a configuration file (265) for storing mappings of a selected function to a button or other degree of freedom of the input device (130, 140, 150), the mapping being effected by graphically associating the specific function with the button or degree of freedom.

18. A device according to claim 17, characterized in that the graphical association of the specific function with the button or degree of freedom is implemented by drag-and-dropping.

19. A device according to anyone of claims 17 or 18, characterized by a device identifier (240) for identifying and displaying, upon an event, the buttons and/or other degrees of freedom of the input device (130, 140, 150).

20. A device according to anyone of claims 17 to 19, characterized by an application context selector (270) for associating an application program with each mapping.

21. A device according to anyone of claims 17 to 20, characterized in that the mapping is stored in a configuration file (265) such that it can be re-used throughout a network.

22. A device according to claim 21, characterized in that an application program is stored in association with the mapping.