JP2009282996A - System and method for interfacing with computer device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system, method and product of a functionally enhanced user navigation to compliment (but not necessarily replace) a computer keyboard and a mouse. <P>SOLUTION: This system includes: a minimally necessary group of commands; combining the functionality of a set of at least two command calls into a single logical button; for a single button, prioritizing a set of command calls from the highest priority order to the lowest priority order, and then calling each command until one command is accepted; logically re-mapping commands to buttons for a navigational device coupled to a physically rotatable display device; and arranging a substitute command to a logical button when the button is used in a prescribed manner other than the primary manner in which the logical button is engaged (for example, double-clicking, flicking, press-and-hold) so that particularly a substitute command can be in fact issued. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates generally to the field of user interfaces, and more particularly to event processing such as navigational control devices used in conjunction with a computer system environment. However, the present invention is not limited to being used in a computer. Conversely, with the various embodiments of the present invention disclosed herein, the present invention may be used in various devices and other systems for daily use.

  The computer industry has long focused on using keys, wheels and on-screen buttons for navigation. Therefore, in order to support the various navigation models used today, both a normal size keyboard, application-specific command buttons, a mouse, and various on-screen interfaces are required. However, current navigation devices are not adapted to new and groundbreaking computerized technologies (such as tablet PCs aimed at becoming an evolutionary successor of laptops), as well as keyboards, mice, Other current devices, or combinations thereof, do not adequately or accurately address the navigation of these newly evolving technologies. Simply put, the computer industry has not fully addressed the obvious technical needs directed at a simple model of navigation that complements or replaces other current models.

  The present invention is not limited to use on a computer, but relates to various embodiments of a user navigation interface that are very suitable for use in a computer system environment. These related inventions provide enhanced user navigation systems and methods that complement (but not necessarily replace) computer keyboards and mice by providing single user navigation that is more powerful than a mouse but less complex than a keyboard. I will provide a. In many embodiments, the related invention is expected to be used as a device with substantial functionality to date that requires only one hand for use (like a mouse) and is called directly from a computer keyboard.

  An embodiment of the present invention relates to a user interface system having an interface that allows a user to generate a logical input for one command in a command group applied to an object. The command group is disclosed. In an alternative embodiment, the minimum required command group comprises four commands for the user interface system, eg, ENTER, UP, DOWN, OUT. In other embodiments, some commands are executed by manipulating wheel or dogbone device variants (described below).

  One embodiment of the invention relates to a method of integrating a set of functions consisting of at least two command calls (including but not limited to keyboard keys) into a single logical button. In some embodiments, the embedding prioritizes a set of command calls from top to bottom, and then uses operating system shell hooks to select other than the lowest priority command. All except the lowest priority command until one is “accepted” (approved and executed), or all but the lowest priority command are “rejected” (not approved) This is done by making an application command call for the command and then issuing the lowest command as an operating system command. For example, in some alternative embodiments, OUT can be equivalent to a Back command call or an Escape command call, but an important combination employed in many other embodiments of the related invention is the Back command call. The call and the Escape command call are merged into an OUT command. An operating system shell hook is used to issue a command as an application command to an application, and if the application command is rejected, the command is cascaded by issuing another command directly to the operating system. In many embodiments, this method is a key point for making the functions of a navigation device that can be operated with one hand relatively easy. Other embodiments employ another strategy for extending the core command functionality afforded by a limited number of logical buttons.

Of the various cascaded embodiments, certain cascaded connections are particularly beneficial for many embodiments of the present invention. Some of the cascade events indicated by the names of logical buttons and their corresponding cascade commands (from high priority commands to low priority commands step by step) are shown below.
・ UP: APPCOMMAND_UP → Up Arrow → Scroll Up → Page Up
・ DOWN: APPCOMMAND_DOWN → Down Arrow → Scroll Down → Page Down
・ NEXT: APPCOMMAND_NEXT → Tab → Right Arrow
・ PREV: APPCOMMAND_PREV → Shift-Tab → Left Arrow
・ ENTER: APPCOMMAND_ENTER → Return → Enter → `` Play ''
・ OUT: APPCOMMAND_OUT → Browser Back → Escape → `` Stop '' → Alt-F4
・ SWITCH: APPCOMMAND_SWITCH → Alt-Escape → Alt-Tab → Windows Key → Home
・ MENU: APPCOMMAND_MENU → Shift-F10 → `` Settings ''

  In this specification, `` Play '' and `` Stop '' are special commands for special contexts such as media applications, and `` Setting '' is for menu settings for other special contexts. Special command.

  Other alternative embodiments are coupled to a physically rotatable display device by first determining the orientation of the display device and logically remapping commands to logical buttons based on the orientation of the display device. A method and system for logically remapping commands to buttons on a navigation device is disclosed. In some embodiments, if the display orientation of the display device changes to another direction, the logical mapping of commands to logical buttons is automatic, perhaps to accommodate the change in the physical orientation of the display device. Get up. In other embodiments, the display direction is determined based on the display direction of the display device itself. In some special embodiments, the navigational interface is a vertical line that is asymmetric with respect to the horizontal line, and the logical remapping is a command that is converted to a logical button in a predetermined manner consistent with the logical use by the end user. Remap.

  A further alternative embodiment is when the button is involved in a predetermined method other than the primary method in which the logical button is involved (double click, flicking, press-and-hold, etc.) Disclosed are systems and products that extend the functionality of a navigational control device by mapping substitute commands to logical buttons and actually issuing substitute commands.

And FIG. 11 is a block diagram illustrating a computer system incorporating aspects of the present invention. 1 is a block diagram illustrating a network incorporating aspects of the present invention. 6 is a flowchart illustrating the logic of an ENTER button in some embodiments of the present invention. 6 is a flowchart illustrating the logic of an ENTER button in some embodiments of the present invention. 6 is a flowchart illustrating the logic of an UP button in some embodiments of the invention. 10 is a flowchart illustrating a variation of the UP button logic in some embodiments of the invention. 6 is a flowchart illustrating the logic of a DOWN button in some embodiments of the invention. 6 is a flowchart illustrating a variation of DOWN button logic in some embodiments of the invention. 6 is a flowchart illustrating the logic of an OUT button in some embodiments of the invention. Figure 6 is a flow chart illustrating more complex logic of the OUT button method in some embodiments of the invention. FIG. 4 is a diagram illustrating a four button arrangement in some embodiments of the invention. It is a figure which shows another embodiment of this invention which has arrange | positioned 4 buttons vertically. It is a figure which shows another embodiment of this invention which has arrange | positioned the button horizontally. FIG. 6 shows another embodiment of the present invention in which buttons are arranged in an improved vertical manner. FIG. 6 is a diagram illustrating another four button arrangement in some embodiments of the present invention. FIG. 4 illustrates a wheel / button in some embodiments of the invention. FIG. 6 illustrates another layout of a wheel / button embodiment in some embodiments of the invention. FIG. 6 illustrates another layout of an embodiment of a wheel / button combination in some embodiments of the invention. It is a figure which shows a clicking wheel. It is a figure which shows a rocking wheel. FIG. 4 illustrates a dogbone / button combination of some embodiments of the present invention. FIG. 6 illustrates another layout of a dogbone / button embodiment in some embodiments of the invention. FIG. 6 illustrates another layout of a dogbone / button embodiment in some embodiments of the invention. It is a figure which shows a clicking dog bone. It is a figure which shows a rocking dog bone. FIG. 6 shows an embodiment of the present invention using a super wheel. FIG. 2 shows an embodiment of the present invention using super dogbone. It is a figure which shows 9 button apparatus. It is a figure which shows 8 button apparatus. It is the table | surface which listed up the direct command (or logical input) of each button of FIG. 15A. It is a figure which shows the display apparatus of the "vertical for right hand" direction which attached the rocking dog bone on the right side. FIG. 16B shows the device of FIG. 16A after being rotated 90 degrees (1/2) to the right in the “lower lateral” direction. FIG. 16B shows the apparatus of FIG. 16B rotated 90 degrees to the right (180 degrees in total or ½ to the right) to “vertical for left hand”. FIG. 16C shows the apparatus of FIG. 16C rotated 90 degrees right (totally 270 degrees or 3/4 right) to “upside”. FIG. 5 is a table illustrating some embodiments of the present invention that use a logical rotation scheme of a fixed navigation device to accommodate logical buttons for special commands that depend on these directions. FIG. 6 shows another display device with a locking dogbone incorporated at the bottom of the device and oriented in the “front end longitudinal” direction. FIG. 18B shows the apparatus of FIG. 18A rotated 1/4 to the right. FIG. 18B shows the device of FIG. 18A rotated 1/2 to the right. FIG. 18B shows the device of FIG. 18A rotated 3/4 to the right. It is a figure which shows the display apparatus of the vertical direction (original direction) for right hands provided with the rotatable navigation apparatus. It is a figure which shows the display apparatus which rotated 90 degree | times to the right, while the rotatable navigation apparatus rotated 90 degree | times right from the visual field of the display apparatus, and maintained the same absolute direction. FIG. 19B shows the device of FIG. 19B rotated 90 degrees further, except that the navigation device maintains the same absolute direction. FIG. 19B shows the device of FIG. 19B rotated 90 degrees further, except that the navigation device maintains the same absolute direction. It is a figure which shows 4 button arrange | positioned at a rhombus. It is a figure which shows 4 button arrange | positioned at the linear direction. It is a figure which shows the button of FIG. 20A without a label. It is a figure which shows the button of FIG. 20B without a label. It is a figure which shows 8 buttons arrange | positioned in a "compass" without a label. FIG. 21B shows the button of FIG. 21A with directional labels. It is a figure which shows the button of FIG. 21A provided with the compass label.

(Introduction)
This subject matter is described in a special way to meet statutory requirements. However, this description is not intended to limit the scope of the patent. Rather, the inventor will consider that the claimed subject matter may be combined with other patents or other technologies in the future to include other components or combinations of components similar to those described in this document. I think that it may be embodied.

(Computer environment)
Many embodiments of the invention can be implemented on a computer. FIG. 1 and the following description are intended to provide a simple and general description of a computer environment suitable for carrying out the present invention. Although not required, the invention will be described using the general context of computer-executable instructions, such as program modules, being executed by computers such as client workstations and servers. Program modules typically include routines, programs, objects, components, data structures, etc. that perform special tasks and implement special abstract data types. Also, those skilled in the art will be able to implement the present invention using computer system configurations such as handheld computers, multiprocessor systems, programmable home electronics based microprocessors, network PCs, minicomputers, mainframe computers and the like. You will understand. The invention may also be practiced in distributed computing environments where tasks are processed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

  As shown in FIG. 1, a general-purpose computing system includes a conventional personal computer 20 having a processing unit 21, a system memory 22, and a system bus 23 that connects system components including the system memory to the processing unit 21. Is provided. The system bus 23 may be any of several types of bus structures, such as a memory bus or memory controller, a peripheral bus, or a local bus using any of a variety of bus structures. The system memory includes a read only memory (ROM) 24 and a random access memory (RAM) 25. The basic input / output system 26 (BIOS) includes basic routines useful for transferring information between components of the personal computer 20 at startup, and is stored in the ROM 24. The personal computer 20 is detachable from a hard disk drive 27 that reads from and writes to a hard disk (not shown), a magnetic disk drive that reads from and writes to a movable magnetic disk 29, and a CD ROM or other optical media. And an optical disk drive 30 that reads from and writes to the other optical disk 31. The hard disk drive 27, magnetic disk drive 28, and optical disk drive 30 are connected to a hard disk drive interface 32, a magnetic disk drive interface 33, and an optical drive interface 34, respectively. These drives and their associated computer readable media provide non-volatile storage for computer 20 readable instructions, data structures, program modules and other data. In the example environment described herein, a hard disk, a movable magnetic disk 29 and a movable optical disk 31 are used, but other types of computer readable media capable of storing data accessible from a computer, such as magnetic Those skilled in the art understand that cassettes, flash memory cards, digital video disks, Bernoulli cartridges, random access memory (RAM), read only memory (ROM), etc. may be used in this example operating environment. Should do.

  A large number of program modules including an operating system 35, one or more application programs 36, other program modules 37 and program data 38 can be stored in the hard disk, magnetic disk 29, optical disk 31, ROM.24, or RAM 25. . A user can input commands and information into the personal computer 20 via input devices such as a keyboard 40 and a pointing device 42. Other input devices (not shown) can include a microphone, joystick, game pad, satellite disk, scanner, and the like. These input devices and other input devices are often connected to the processing unit 21 via a serial port interface 46 connected to the system bus. However, other devices such as a parallel port, a game port, or a universal serial bus (USB) are used. It may be connected via the interface. A monitor 47 or other type of display device is connected to the system bus 23 via an interface, such as a video adapter 48. The monitor 47 and personal computer are usually provided with other peripheral output devices (not shown) such as speakers and printers. The system example of FIG. 1 includes a host adapter 55, a small computer system interface (SCSI) bus 56, and an external storage device 62 connected to the SCSI bus 56.

  The personal computer 20 can operate in a network environment using a logical connection with one or more remote computers such as the remote computer 49. The remote computer 49 may be another personal computer, server, router, network PC, peer device, or other common network node, and only one storage device 50 is shown in FIG. However, it typically includes many or all of the above-described components associated with the personal computer 20. The logical connection shown in FIG. 1 includes a local area network (LAN) 51 and a wide area network (WAN) 52. This networking environment is commonplace in offices, enterprise-wide computer networks, intranets and the Internet.

  When used in a LAN networking environment, the personal computer 20 is connected to the LAN 51 via a network interface or adapter 53. When used in a WAN networking environment, the personal computer 20 typically includes a modem 54 or other means for establishing communications over a wide area network 52 such as the Internet. The modem 54 may be internal or external and is connected to the system bus 23 via the serial port interface 46. In a network environment, program modules associated with the personal computer 20 or portions thereof can be stored in a remote memory storage device. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used. Although many embodiments of the present invention are envisioned to be particularly suitable for computerized systems, this document does not intend to limit the invention to those embodiments. In contrast, the term computer system is intended to encompass any or all of devices that include a push button or that can determine that a button or button equivalent has been pressed. Is independent of whether it is electrical, mechanical, logical or virtual.

(Network environment)
FIG. 2 illustrates an example network environment in which aspects of the invention may be implemented. The actual network and database environment can be deployed in a variety of configurations. However, the example environment shown here shows a framework for understanding the type of environment in which the present invention operates.

  The network includes a client computer 20a, a server computer 20b, a data source computer 20c, and databases 70, 72a, 72b. The client computer 20a and the data source computer 20c perform electrical communication with the server computer 20b via a communication network 80 such as an intranet. The client computer 20a and the data source computer 20c are connected to a communication network via a communication interface 82. The communication interface 82 is any of well-known communication interfaces such as Ethernet (registered trademark) coupling and modem coupling.

  The server computer 20b manages the database 70 using database server system software, which will be described in detail later. Accordingly, the server 20b serves as a repository for data sent from various types of data sources, and provides the data to various data consumers.

  In the example of FIG. 2, the data source is provided by the data source computer 20c. The data source computer 20c communicates data with the server computer 20b via a communication network 80 such as a LAN, WAN, intranet, or the Internet. Data source computer 20c stores data locally in databases 72a, 72b, which may be relational database servers, Excel spreadsheets, files, and the like. For example, the database 72a shows data stored in the tables 150, 152, and 154. Data provided by the data source 20c is combined and stored in a large database such as a data repository maintained by the server 20b. A client computer 20 a wishing to use data stored by the server computer 20 b can access the database 70 via the communication network 80. The client computer 20a requests the data stored in the database 70 using an SQL query (eg, update, insert, delete).

(Overview)
For some embodiments of the present invention, an “object” includes, but is not limited to, a dialog box, menu, web page, text page, movable drawing object, or other computer system known and understood by those skilled in the art. It is composed of items. For purposes of explaining the present invention, it is assumed that all objects can be classified into four categories for convenience. The four categories are (1) a selection box such as a dialog box or a menu for the user to select one element from a plurality of elements, (2) a content object such as an editable text object, (3 ) Movable drawing objects (MDOs), and (4) audio objects. In practice, more categories are conceivable and desired, but when those categories are included, the logic described herein can be used by those skilled in the art to accommodate the unique characteristics of additional object groups. Such extensions should be considered as anticipated and disclosed by the present invention because they merely require extensions.

  As soon as a button is pressed on the input device, or a wheel or dogbone (described below) is rolled or rotated or locked, the present invention can be controlled by basic physical interaction. Appropriate electrical signals are generated that constitute the logical input for use with (such logical input is widely known and understood by those skilled in the art). Generated by physical interaction using input devices other than buttons, wheels, and dogbones (eg, but not limited to voice recognition input, infrared signal input, patent recognition input, etc.) Such logical inputs may be suitable for use with various embodiments of the present invention. Accordingly, nothing in this specification should be construed as merely limiting the logical input to the device groups explicitly disclosed herein. However, for convenience, references to components (eg, buttons) that are useful for physical interactions shall be direct references to the logical inputs generated by each physical interaction. In other words, the components of the input device, including buttons, wheels, dogbones, or other such devices, will be the logical ones of the embodiments described herein when physically acted upon. It shall constitute the input. Thus, as a non-limiting example, an “ENTER button” is a form of “logical input for ENTER”.

  The main button / wheel / dogbone group that provides the basis for an interface device that can be readily identified by the user and used to navigate information in a simple and consistent manner is at the heart of various embodiments of the present invention. To position. This embodiment generally comprises a core group of logical buttons for a group of minimally required commands (core commands), some embodiments for an auxiliary set of navigation commands (auxiliary commands) With additional logical buttons. Logical buttons comprise individual buttons or logical equivalents of obvious input events from wheels or dogbones (defined and described in detail later), or combinations of logical buttons, utilized by various embodiments. To produce core commands and auxiliary commands. In other embodiments, it can handle a significant number of logical buttons with relatively few physical components to perform surprising navigational functions far beyond core and auxiliary commands, Functions may include general commands that may be objects, applications, or specific and / or changeable devices in some cases.

  The core commands in many embodiments of the present invention are roughly equivalent to the Up, Down, Enter, and Escape keyboard key events. Because these core commands are usually the most relevant command calls with the two most basic navigation functions, scanning and switching-scanning view and selection, accepting or rejecting and selecting in a view- Because. The Up and Down cross keys are not the only way to scan. However, since menus, lists, and scrolling views are all arranged along the vertical axis and always respond to these two keystrokes, these keys are most well established for this basic user task. It is a thing. This relevance forms the basis of the user's conceptual model for the scanning axis in the present invention. Similarly, the Enter key is almost universally known to computer users as a very reliable means of activating or executing all currently selected functions on a screen (graphical user interface or GUI). Also, in general, Escape is semantically considered the opposite of Enter, and handles many common backout scenarios such as closing a mail message and closing a dialog box. However, an important aspect of many embodiments of the present invention is that the functionality of navigation can vary based on the context or application object being navigated. Further, the navigation additional function is executed by an auxiliary command.

  Regarding the Escape function, another important aspect of the various embodiments of the invention described herein has been over the years despite the fact that the conventional Escape function is suitable for dates. The execution of the Escape function is actually completely limited to serve as a core command for many embodiments of the invention described herein. For example, when closing a window object in an application, it is widely understood that most windows do not actually respond to the Escape key, but only respond to keystrokes on the “Alt-F4” keyboard. Navigation “history” —that is, navigation is along some logical path that is the result of navigation, and is tree-structured data or other tree-structured objects. -For applications with-, the act of closing a window is go back (ie, returning to the previous content in the current context or different content with the window open based on the viewing history) It is not as important and widely used as the need and desire of things. Thus, in many embodiments of the present invention, the Escape concept is replaced by a more powerful “Out” (described below) for the OUT button. However, in other embodiments, Escape or Back is mapped to OUT as appropriate.

  Based on this principle, the various embodiments of the present invention are suitable for devices with four logical buttons, OUT, UP, DOWN and ENTER, which collectively represent core navigation commands. The main functionality group forms the basis of many enhanced embodiments of the invention that make use of auxiliary commands. The basic button group and the functionality of responding to core commands can be matched to the constant changes of the user application. For example, four basic navigation button functions or “navbuttons”, wireless display, remote control, key fobs, wrist watch, smart phone, music device, and other user applications Regardless of whether these devices are recognized as traditional computing devices.

  For embodiments that disclose real-visible results, such as visible effects on a display monitor, invisible effects are also predicted and included. For example, if a set of buttons is described as moving the cursor up and down on a display device, the audible effect (eg, volume up or down), tactile effect (eg, surface temperature rise or fall) Alternative embodiments where the effect is not visible are expected. Accordingly, invisible results from this specification can be sufficiently predicted, and nothing in this specification should be construed as limiting the various embodiments of the invention to visual results.

  Finally, many of the embodiments disclosed herein are ideally in a stand-alone device, but may be incorporated as part of a larger device. For example, many embodiments include, without limitation, as a group of buttons (possibly between a group of cross keys and a group of paging keys) on a keyboard or alongside a display (plus other buttons and interfaces). It may appear as a group of buttons or as a virtual button (or other virtual embodiment) in a touch screen. In any event, nothing in this specification should be construed as limiting aspects of the invention to standalone embodiments.

(Core commands and related embodiments)
The following commands consist of some of the key core commands used herein and how they are interpreted by the system within a specific context.

-UP: Move (advance) one unit, line, cell, scroll increment, page, or screen up; MS Windows APPCOMMAND_NAVPAD_UP event or USB HID NAVPAD_UP event-DOWN: one unit, line, cell, Scroll increment, move page or screen down (advance); MS Windows APPCOMMAND_NAVPAD_DOWN event or USB HID event • NEXT: move to next object, field, link, or window frame (skip) MS Windows APPCOMMAND_NAVPAD_NEXT event or USB HID NAVPAD_DOWN event • PREV: Move to the previous object, field, link, or window pane “(skip); MS Windows APPCOMMAND_NAVPAD_PREV event or USB HID NAVPAD_PREV event ENTER: (key Operate (execute) on the current object (similar to the board Enter key or other context OK buttons); MS Windows APPCOMMAND_NAVPAD_ENTER event or USB HID NAVPAD_ENTER event • CENTER: (similar to the keyboard Enter key) Manipulating (executing) on the current object; MS Windows APPCOMMAND_NAVPAD_CENTER event or USB HID NAVPAD_CENTER event • OUT: Returning to the previous open object, page, or view; Closing an active object (similar to a cascaded Esc / Back combination as described elsewhere in this document as Esc, Back, or as an MS Windows APPCOMMAND_NAVPAD_OUT event or USB HID NAVPAD_OUT event) MORE: Details about the options available for the current object Or execute that option; MS Windows APPCOMMAND_NAVPAD_MORE event or USB HID NAVPAD_MORE event • SWITCH: Switch to the next window, screen, page, application, or functional offering; MS Windows APPCOMMAND_NAVPAD_SWITCH Event or USB HID NAVPAD_SWITCH event.

  FIG. 3A is a flowchart illustrating the logic of the ENTER button in one embodiment of the present invention. When the ENTER button is pressed at block 302, the ENTER button system determines at block 304 whether the object is a selected object (and not a content object or movable drawing object). In the embodiment, no other events occur, and the system returns at block 350 (events other than the null event of the present invention always occur for content objects and movable drawing objects, as will be appreciated by those skilled in the art. Will be understood by.) On the other hand, if the object is actually a selected object, at block 306, the system determines whether the active element in the object has already been selected. If the active element has already been selected, at block 312 an `` execute '' event is generated that is equivalent to pressing the Enter key on the keyboard (the result is that the selected element is Open, Accept, or OK, and these events are known and understood by those skilled in the art.) In block 350, the system returns. On the other hand, if the active element is not selected, at block 308, the system determines whether the element of the object is marked as Initial Focus (the default selected element) and marks If so, at block 314, the element marked as initial focus is selected, after which the system returns at block 350. Finally, if there is no initial focus, at block 316, the system selects the element of the first placed object and returns at block 350.

  Of course, variations to the flowchart of FIG. 3B may be desirable under certain circumstances. For example, consider FIG. 3B, which is a flowchart showing a variation in the logic of the ENTER button of FIG. 3A. In this embodiment, (a) in block 304, whether or not the object is a selected object, (b) in block 306 whether the active element is not selected, (c) in block 308, the object After determining whether (2) has initial focus (in the same manner as in FIG. 3A), at block 310, the system of FIG. 3B further determines whether the active element is visible, If so, the first visible element is selected at block 318, and if not visible, the first listed element is selected at block 316. The present invention discloses this and other subtle variations within the logic herein.

  Note that by using the methods of these specific embodiments and others described herein, the user can select an element by pressing the ENTER button once (when none has been selected). The element can be selected and the element can be executed by pressing the ENTER button again (equivalent to pressing the Enter key on the keyboard).

  FIG. 4A is a flowchart illustrating the UP button logic in one embodiment of the invention. When the UP button is pressed at block 402, at block 404, the UP button system determines whether the object is a selected object. If not, at block 422, the system determines whether the object is a content object or a movable drawing object. If the object is a movable drawing object, at block 432, the system pushes the object up (moves up) by a predetermined distance (eg, 1 pixel) and can be inferred from here (and elsewhere in the figure) If no further movement in that direction is possible or allowed, do nothing. Although the logic to handle null events when movement in the desired direction is not possible or not permitted is not clarified at this stage, an example of that logic is a hash-line blocks ) And will be described later for the content object. The logic can be inferred and implied for the remaining drawings as needed.

  Returning to the drawing again, if the object is actually a content object, at block 424, the system determines whether the text in the object consists of one or more lines. If the text object consists of multiple lines (in order to represent logic to handle a null event when movement in the desired direction is not possible or not allowed), the system determines that the insertion point is Determine if it is currently on the first line, and if so, the system does nothing and returns at block 450. Otherwise, at block 434, the system moves the insertion point up one line and returns at block 450. Conversely, if the text object consists of only one line, at block 428, the system determines whether the insertion point is currently before the first character of the line and if so, The system does nothing and returns at block 450. Otherwise, at block 436, the system moves the insertion point one character to the left and returns at block 450.

  If, at block 404, the system determines that the object is a selected object, at block 406, the system determines whether an element within the object has already been selected. If an active element has already been selected, at block 412, the system selects the previous element in the list (implicitly, the selected previous element has not been selected) and the system blocks 450. Return at. In contrast, if the active element is not selected, at block 408, the system determines whether the element of the object is marked as initial focus (as a default selected element) and if so. In block 414, the element marked as initial focus is selected, after which the system returns in block 450. Finally, if there is no initial focus, at block 416, the system selects the first placed element of the object and returns at block 450.

  FIG. 4B is a flowchart illustrating a variation of the UP button logic of FIG. 4A based on a variation similar to that introduced earlier in the specification to distinguish FIGS. 3B and 3A. In the embodiment of FIG. 4B, again, (a) whether the object is a selected object in block 404, (b) whether an active element is not selected in block 406, (c) block After determining at 408 whether the object is not in initial focus (same as the method of FIG. 4A) (in the same way as the method of FIG. 4A)-at block 410, the system of FIG. Is visible, if so, the first visible element is selected at block 418; otherwise, the system selects the first listed element at block 416 To do.

  FIG. 5A is a flowchart illustrating the logic of the DOWN button in one embodiment of the present invention. When the DOWN button is pressed at block 502, at block 504, the DOWN button system determines whether the object is a selected object. If not, at block 522, the system determines whether the object is a content object or a movable drawing object. If the object is a movable drawing object, at block 532, the system simply pushes (moves) the object a predetermined distance (eg, 1 pixel), or here (or elsewhere in the drawing). ) If you can't move further in that direction, or you are not allowed, you can do nothing. In contrast, if the object is a content object, at block 524, the system determines whether the text in the object consists of one or more lines. If the text object consists of multiple lines, at block 526, the system further determines whether the insertion point is currently at the last line, and if so, the system does nothing and blocks 550. Return at. Otherwise, at block 534, the system moves the insertion point down one row and returns at block 550. Conversely, if the text object consists of just one line, at block 528, the system determines whether the insertion point is currently behind the last character in the line, and if so, the system Does nothing and returns at block 550. Otherwise, at block 536, the system moves the insertion point one character to the right and returns at block 550.

  If at block 504 the system determines that the object is a selected object, at block 506 the system determines whether an active element within the object has already been selected. If an active element has already been selected, at block 512, the system selects the next element in the list (implicitly, the previously selected element is not selected) and the system Return at block 550. In contrast, if the active element is not selected, at block 508, the system determines whether the element of the object is marked as the initial focus (as the default selected element) and if so. In block 514, the element marked as initial focus is selected, after which the system returns at 550. Finally, if there is no initial focus, at block 516 the system selects the last element on the object and returns at block 550.

  FIG. 5B is a flow chart illustrating a variation of the logic of the DOWN button of FIG. 5A based on a variation similar to that previously introduced in the specification to distinguish FIGS. 3B and 3A and FIGS. 4B and 4A. It is. In the embodiment of FIG. 5B, again, (a) whether the object is a selected object in block 504, (b) whether an active element is not selected in block 506, (c) block After determining at 508 that the object is not initial focus (in the same manner as in FIG. 5A) --- in block 510, the system of FIG. 5B further determines whether the active element is visible. If so, the last visible element is selected at block 518; otherwise, the system selects the last listed element at block 516.

  Despite the fact that the traditional Escape feature has been used for a long time, it is still quite limited and very specialized. For example, to close a window, most windows do not actually respond to the Escape key at all, but instead respond to the "Alt-F4" keystroke. As far as applications with navigation “history” are concerned—that is, when navigation follows a certain logical path—the act of closing a window is a go back (ie, leaving the window open). And the need and desire to return to previous content in the current content or to different content based on viewing history (and not widely used). Thus, when referring to the OUT button, we replace the Escape or Back concept with the more powerful “Out” concept for one embodiment of the present invention.

  Overlapping the embodiments, OUT can be a logical and well-coordinated combination of the functions provided by the Back and Escape command calls. In an operating system where all windows respond to Escape, fusing these two buttons is very beneficial. This is because these keys are rarely used sufficiently and consistently in various application contexts. In a few applications that use both Back and Escape, each with a distinct feature, it is impractical and inefficient to let the user guess which keyboard key the OUT button will be duplicated on . One solution provided by one embodiment of the present invention is that when the application understands the Back key command, it uses the OUT button to generate the Back key command, and the application receives the Back key command. If you don't understand, instead, generate an Escape key command--that is, cascade a Back command accompanied by an Escape command. In this way, applications with history can be moved to --- back more frequently than closing windows via Escape, etc. On the other hand, an application that does not have the Back key function will automatically get whatever function is provided by the Escape key. In order to perform this methodology of Back / Escape key selection via the OUT button, one embodiment of the present invention first uses an operating system shell hook to create an “App command” (application command to an application program). ), A Back key is generated, and if the Back command is rejected by the application, an Escape command equivalent to pressing the Escape key on the keyboard is generated. In other embodiments, Escape or Back can simply be mapped to OUT as appropriate. This document does not include anything intended to limit the basic functionality of OUT. Nevertheless, it is assumed herein that OUT refers to the Back / Escape cascade function.

  FIG. 6A is a flowchart illustrating the logic of the OUT button method in one embodiment of the invention. When the OUT button is pressed at block 602, at block 604, the OUT button system is labeled (sometimes as a Browser Back key or other equivalent, using an operating system shell hook, and its operation is Issue application commands to the application that are equivalent to commands generated by the user pressing the Back key on the keyboard (sometimes executed as a right mouse click). Next, at block 606, the system determines whether the Back application command has been rejected. If not, the system returns at block 650; otherwise, at block 608, the system issues an Escape command. Then, the process returns at block 650.

  6B is a flowchart illustrating more complex logic of the OUT. Button method based on the methodology illustrated in FIG. 6A. In FIG. 6B, when the OUT button is pressed at block 602, at block 610, the system first checks to see if the window is at the beginning of its history (and therefore returns nowhere). In that case, the method may do one of the following two things: (a) It ignores the OUT button (null event) and returns immediately. If possible, (b) it closes the window via Escape. To implement the latter option, one of the following two methods may be used. (I) If the system takes a procedure to send a Back command and this application command is presumed to be rejected by the application (because there is no return destination), the system will (with the methodology shown in FIG. 6A) Take a procedure to send an Escape command, or (ii) the system may send an Escape command immediately. This is shown in this drawing. Thus, if at block 610 the system determines that the window is at the beginning of its history, the system immediately takes the procedure of block 608, issues an Escape command, and returns at block 650. Otherwise, at block 604, the system again uses the operating system shell hook to issue an application command for Back to the application, and then at block 606, whether the Back application command has been rejected or not. If it is determined and not rejected, the process returns at block 650; otherwise, the block 608 issues an Escape command and returns at block 650.

  Various physical embodiments of the present invention are contemplated. One embodiment shown in FIG. 7A is an arrangement of four buttons comprising, for example, ENTER 702, OUT 704, UP 706, DOWN 708 buttons arranged in a diamond shape on a pad or device. FIG. 7B is an alternative embodiment of the present invention, which has a similar geometry except that it includes, for example, four buttons arranged vertically along the right edge of the computing device. FIG. 7C is another alternative embodiment of the present invention showing buttons positioned horizontally, for example along the tip of a computing device. In contrast, FIG. 7D is yet another embodiment of the present invention, which comprises an ENTER 702 in the center and UP 706 and DOWN 708 vertically above and below the ENTER 702, respectively, and three linearly arranged. The button arranged by the improved vertical method with OUT704 in the upper left of the button is shown. Of course, various combinations of commands may be assigned to a 4-button device. The device of FIG. 7E shows a device similar to that of FIG. 7A, except that the four buttons correspond to the commands UP, DOWN, PREV, and NEXT.

  However, because the 4-button schema disclosed herein is logical and not physical, some embodiments of the present invention may utilize different physical components. . For example, one embodiment of the invention shown in FIG. 8A consists of a wheel / button combination with one vertical wheel 802 and two buttons 804 and 806, where wheel 802 is a wheel (shown). Button 804 and button 806, respectively, when they are pressed are considered logically equivalent to both UP and DOWN functions based on the direction directed (up or down). , ENTER and OUT are interrelated. The wheel 802 in this embodiment operates in a manner similar to the wheel of a mouse device, as is well known and understood in the art, with a slight roll up or down as input. FIG. 8B shows another layout of one embodiment of the wheel / button combination, and FIG. 8C shows yet another layout of the embodiment.

  FIG. 9 illustrates another alternative embodiment of the present invention in which the wheel 902 not only supports up and down movements corresponding to UP and DOWN, but when a predetermined minimum threshold pressure is applied, Acts as an ENTER button. Due to this pressure input feature, the wheel 902, referred to herein as the clicking wheel, can accept three different inputs, while the fourth input, OUT, is a button 904 proximate to the clicking wheel 902. Corresponding to

  In another embodiment of the present invention, as shown in FIG. 10, a four button schema is used by a single physical element, the locking wheel. The locking wheel 1002 further supports a side-to-side locking mechanism without compromising the vertical rotational motion. With this feature, locking to the right is related to ENTER, locking to the left is related to OUT, while UP and DOWN are obtained by rolling up and down the wheel 1002 (as shown). Continue to be received. Also, if the locking wheel shown for this embodiment further incorporates the pressure input of the clicking wheel of FIG. 9, that embodiment obtains a fifth button function, and the fifth button function is May be used with some of the 5+ button configurations that provide some interesting embodiments discussed in detail in.

  FIG. 11A shows another embodiment of the present invention that is similar to the invention disclosed in FIG. 8A, utilizing a dogbone 1102 instead of a conventional wheel. The dock bone 1102 is inherently an ergonomically improved wheel device, while the conventional wheel is relatively suitable for use with the index finger, while the dog bone is particularly suitable for thumb involvement. In this embodiment, the operation of the dockbone 1102 rolling up or down vertically is logically regarded as equivalent to both UP and DOWN functions (as shown in the figure), while the button When 1104 and 1106 are pressed, they are interrelated with ENTER and OUT, respectively. FIG. 11B shows another layout of the dockbone / button combination, and FIG. 11C shows yet another layout of the embodiment.

  FIG. 12 illustrates another alternative embodiment of the present invention in which the dockbone 1202 not only supports up and down movements corresponding to UP and DOWN, but when a predetermined minimum threshold pressure is applied. , Works as ENTER button. Due to this pressure input feature, the dock bone 1202, referred to herein as the clicking dock bone, can accept three different inputs, while the fourth input, OUT, is input to the clicking dog bone 1202. Corresponds to the adjacent button 1202.

  Finally, in another embodiment of the invention shown in FIG. 13, a 4-button schema is used by a single physical element, namely the locking dogbone 1302. The locking bone 1302 is similar to the locking wheel 1002 shown in FIG. 10 by further supporting a side-to-side locking mechanism without compromising vertical rotational motion. With this feature, locking dogbone 1302 to the left is correlated with ENTER, locking dogbone 1302 to the right is correlated with OUT, while UP and DOWN Continue to be obtained from the up and down rolling of the dogbone 1302 (as shown). Also, if the rocking dogbone shown for this embodiment further incorporates the pressure input of the clicking dogbone of FIG. 12, the embodiment obtains a fifth button function and the fifth button The functionality may be used with some of the 5+ button configurations that provide some interesting embodiments that will be discussed in detail later.

(Extended commands and related embodiments)
The embodiments of the present invention disclosed so far in this specification include four buttons (or buttons in the case of wheels and dogbones) that map directly to the four basic commands ENTER, UP, DOWN, and OUT. Focuses on schemes with logical equivalents). It does not deny the ability of a simple schema with the most useful commands for navigating objects, but it can be used in one of four ways: physically, temporally, logically, combinatorially. By expanding the functions, a wider range of functions become effective. For example, additional commands that some embodiments may map separately from the four basic commands ENTER, UP, DOWN, and OUT are PREV and NEXT for 6-logical button embodiments. Equipped with PREV, NEXT, MORE, SWITCH for the 8-logical button embodiment.

  One way to extend the logical 4-command array is to simply add more buttons (or logical equivalents of buttons) and map additional commands to the physical 4- Expand the button layout. For example, if the 4-button function of the locking wheel shown in FIG. 10 includes the pressure input function of the clicking field of FIG. 9, this enhanced wheel (hereinafter referred to as the super wheel) is logically. Reveal the fifth button and use the fifth command directly (or be used in a logical or combinational schema as described later in this document). Similarly, when the 4-button function of the rocking dog bone shown in FIG. 12 further includes the pressure input function of the clicking wheel of FIG. 13, this enhanced dog bone (hereinafter referred to as a super dog bone). Can logically reveal the fifth button and use the fifth command directly (or again, as used later in this document, logically or in a combined schema) . FIG. 14A illustrates one embodiment of the present invention that utilizes a super wheel, while FIG. 14B illustrates one embodiment of the present invention that utilizes a super dogbone.

  Combining a super wheel or super dog bone with an additional button results in a powerful navigation device that can be operated with one hand (or even with one finger or thumb). For example, in some embodiments, the device uses two buttons on the locking button (6 logical buttons in total) or uses 4 buttons on the locking button (8 in total). Two logical buttons), and corresponding commands are mapped to logical buttons. Similarly, in each of these embodiments, a 7-button device or 9-button device, respectively, is obtained by using a super dogbone instead of a rocking dogbone.

  FIG. 15A illustrates one embodiment of a navigation device that utilizes a super dog bone and four additional physical buttons arranged vertically with the super dog bone in the center of the array. This 9-button device will hereinafter be referred to as a “niner”, while the 9-button device shown in FIG. 15A shall be referred to as a vertical nineer. Referring to FIG. 15A, the vertical ninner 1502 includes a super dogbone 1504 with two buttons 1506 and 1508 on the upper side and two buttons 1510 and 1512 on the lower side. Direct commands (or logical inputs) for each button are listed in the table of FIG. 15C. In this embodiment, the functions of ENTER, UP, DOWN, and OUT are the same as the functions already disclosed in this specification, and the ENTER command is two (not required but allowed). Corresponds to a logical button. Similarly, another embodiment comprises the 8-button device shown in FIG. 15B and has a similar command mapping, except that ENTER corresponds only to a single logical button. Note that PREV and NEXT corresponding to the Tab and Alt-Tab command calls are executed instead of the Left Arrow and Right Arrow functions. The reason is that the PREV and NEXT functions are relatively useful in the context of navigation. That said, in some situations it is desirable to combine the PREV and Left Arrow commands together in a manner similar to, for example, the combination of Escape and Back in an OUT command.

  Another way to extend the functionality of a logical button is to provide a special function when the button is pressed and "" held down "for a predetermined time. For example, if the user pressed and pressed the UP button, it would be logical for some embodiments of the invention to interpret it as a different command, for example, a PAGEUP command that duplicates the keyboard's Page Up key. . Instead, the system may automatically repeat the UP command quickly, which is similar to the effect of pressing and pressing the Up Arrow key on the keyboard.

  Another way to extend the functionality of the button schema described herein is to distinguish different types of “motion” from the way the mouse distinguishes between single clicks and double clicks. Similar. For example, when using a wheel or dogbone schema, it would be a logical extension to consider the flick above or below the wheel (a flick that is a large action in a short time) as a separate logical button. . For example, normal rotation of the dogbone up or down will result in UP or DOWN, while flicking the wheel up or down may catch a PAGEUP or PAGEDOWN command, which will cause the keyboard Page Up, Matches with Page Down key.

  Another powerful means of extending the functionality of a button is to consider the various combinations of buttons used to represent different commands than those normally associated with individual buttons when pressed simultaneously. is there. For example, one embodiment of the present invention comprises four physical navigation buttons, a locking dogbone, or a locking wheel as the main navigation logical button group, and possibly secondary to the four logical buttons. Perhaps with a change button that allows you to have a different mapping. The change button would be equivalent in many respects to the 'Fn' key on many computing devices such as laptops, tablet PCs and the like. Further, the modifier can be a “double-tapped” that performs additional commands such as invoking a special menu that is particularly useful for special computer devices. The special menu is, for example, a menu for rotating the display between the vertical direction and the horizontal direction in the apparatus, and the function is particularly relevant and useful in the apparatus. This will be described in detail below.

  The embodiments described so far are largely based on mapping different logical results based on different physical user interactions within a given context. However, according to another embodiment, a single special physical interaction can produce different logical results (steps, scrolls, pages, etc.) within different contexts (such as text documents, virtual books, or slide shows). It will be possible to make it happen. For example, rolling down with a rocking dogbone can be one line in a context, stepping down, one page in another context, scrolling down, and yet another context Within one context, it is considered equivalent to paging down and has a rolling up with a corresponding opposite logical result within each context. Similarly, a rocking left with a rocking dogbone again skips between panes in one context, skips between links in another context, or a tree in another context It can enter the lower branch of the type hierarchy and has a rolling down with a corresponding opposite logical result within each context. Other embodiments include rocking wheel, super dogbone, super wheel, diamond shaped 4 buttons, 8 buttons equally configured along a circle resembling 32 orientations, joystick, D-pad, touch pad, touch strip Etc. are followed in the same functioning policy. Other commands may include ENTER and OUT (along with "access") as well as two other abstracts (generally "abstract") to combat the command, apart from steps, scrolls and pages. it can.

(Flexible orientation)
In devices where menus that rotate the display between portrait and landscape are particularly relevant and useful, another important element of the present invention incorporated into various embodiments is that logical button commands are converted to physical buttons. Ability to reset. For example, consider the device of FIG. 16A showing a display device such as a tablet PC in a “right-handed portrait” orientation with a locking bone 1604 attached to its right side. For convenience, the functions of the logical buttons of the locking dogbone 1604, ie, the functions of the rolling up, rolling down, locking left, and locking right logical buttons, are named A, B, C, and D, respectively. Consistent with dogbone 1604. In contrast, the commands for each logical button of the locking dogbone 1604, labeled U, D, P, N for UP, DOWN, PREV, and NEXT commands, are actually this special physical Associated with the locking dogbone 1604 in the direction (ie, the vertical direction for the right hand), and logical mapping of logical buttons to commands can be expressed as follows (label on the left, right: Command)

A = U
B = D
C = P
D = N

  However, for some embodiments of the present invention, when the display device 1602 is rotated, the logical button assignments are accurately remapped. For example, consider FIG. 16B showing device 1602 after being rotated 90 degrees (1/4) to the right in a “bottom landscape” orientation. This is considered to occur after the user instructs the device to change the display orientation. The remapping of commands to logical buttons automatically follows. In this rotated direction, the logical mapping to the rocking dogbone 1604 can be expressed as follows (label on the left, command on the right).

A = D
B = U
C = P
D = N

  Note that commands for logical buttons A and B are interchanged (ie, UP and DOWN commands are interchanged), while commands for logical buttons C and D remain the same. This is because the dogbone 1604 actually only rolls along one axis that is initially shown oriented vertically. The axis should preferably be mapped to the vertical direction of the display, because the vertical display operation is generally more important than the horizontal display operation, and more frequently This is because it is used. Therefore, the rolling ability of the dogbone 1604 should always be logically mapped to vertical motion, in which case it is natural to match the rightward rolling motion to the downward movement of the display. Yes (and at least harmonize with other orientations and reading text documents). Similarly, in this case, the remapping of the locking that matches the locking up with the leftward movement of the display is natural (and at least harmonized with other orientations and reading of the text document). By remapping the logical relationship between the logical button and the command that the logical button calls (actually partial remapping), the user can change the orientation of the device, The user interface can be used in a very compatible way.

  FIG. 16C shows the same device rotated further 90 degrees to the right (180 degrees in total or 1/2 to the right) and when displayed automatically or manually with the new direction as seen in the direction of this device. It is explanatory drawing of the resulting remapping. In this direction, the logical mapping of the locking dogbone 1604 can be expressed as follows (label on the left, command on the right):

A = D
B = U
C = N
D = P

  This orientation, the “left-handed portrait” orientation, is particularly useful for left-handed users. Compared to the previous direction, the commands for logical buttons C and D are interchanged, while the commands for logical buttons A and B remain the same. This remapping (180 degrees) is actually only a partial remapping (90 degrees to the right) from the previous direction, but is completely remapped from the first direction.

  FIG. 16D shows the same device rotated 90 degrees to the right (total 270 degrees or 3/4 to the right) to form the “top landscape” orientation. Remapping results when a new orientation is displayed either automatically or manually as seen in FIG. In this direction, the logical mapping of the locking dogbone 1604 can be expressed as follows (label on the left, command on the right):

A = U
B = D
C = N
D = P

  Compared with the previous direction, logical buttons C and D remain the same, whereas logical buttons A and B are interchanged. Assuming that the device has been rotated one more time and returned to its initial position, the commands of logical buttons A and B remain the same, while logical buttons C and D are interchanged. In summary, some embodiments of the present invention use a fixed navigation device logical rotation scheme so that logical buttons correspond to special commands that depend on their orientation. The exact mapping is shown in the table of FIG. This mapping is best suited for devices that are symmetrical along one physical axis, such as with wheels or dogbones.

  FIG. 18A shows another display device 1802, ie, as a non-limiting example, a “front end longitudinal” pocket display device incorporating a locking dogbone 1804 at the bottom of the device, the device being ¼ each. Rotate 3 times to the right and remap the logical commands in a manner similar to the device shown in FIGS.

  Another solution for the rotating display dilemma is to rotate the physical user interface itself. FIG. 19A shows a display device 1902 with a rotatable navigation device 1904, which has a right hand vertical direction. FIG. 19B shows the display device 1902 rotated 90 degrees to the right while the rotatable navigation device 1904 rotates 90 degrees to the right from the view of the display device 1902 and maintains the same absolute direction. 19C and 19D show the same device rotated by 90 degrees. In each case, the navigation device 1904 maintains the same absolute direction.

  In a similar manner, rotation is virtual for navigational devices that are not physically distinguishable when rotated, and only need to cause logical rotation. Although this methodology is not suitable for navigational devices that utilize wheels or dogbones with a primary axis of rotation, other embodiments such as the 4-button navigational device of FIG. Similar to the function implemented for a display device with a rotatable navigational device, such as the device disclosed in FIGS. 19A-D, the functions implemented on the rotating device are simplified between physical buttons. To direct remapping (logical rotation). The rotation of commands between physical buttons is well suited for navigational devices that are symmetrical in both the vertical and horizontal directions, such as the case with the rhombus arrangement already described.

(Navigation independent of dimensions)
In many embodiments described so far, and particularly in those embodiments with a plurality of symmetrical buttons, the function of the logical button corresponds to the physical position of the button. That is, the logical dimension indicates the physical dimension. However, another embodiment of the present invention breaks the relationship between the physical and logical dimensions to further extend the functionality of the user interface device.

  Symmetric buttons are a combination of logical buttons (which may or may not include all of the device's logical buttons) and their physical equivalents (push buttons, wheels or dogbones). Yes, the latter means that they are physically arranged on the device in a multidimensional manner, and the button functions are logically interrelated and determined from the physical layout. For example, consider FIGS. 20A and 20B, which consist of four buttons arranged in different physical configurations. Both of these embodiments have the same buttons, but the buttons in FIG. 20A are multi-dimensionally arranged along two axes (UP and DOWN are arranged vertically, while LEFT and RIGHT are Placed horizontally.) In contrast, the buttons of FIG. 20B are arranged one-dimensionally along a single horizontal axis. The function of each button in FIG. 20A is a result of the physical layout, but is indicated by the interrelationship between the buttons. However, the button function of FIG. 20B is indeterminate. For example, the button layout of FIG. 20C is similar to the layout of FIG. 20A except that there is no clear label, but the function of each of these buttons can be naturally estimated to be related to each other (A And C are in the opposite relationship, B and D are in the opposite relationship, the former is related to the vertical axis while the latter is related to the horizontal axis.) In addition, the movement in the direction related to each button Corresponding to However, the button layout of FIG. 20D is similar to the layout of FIG. 20B, except that there is no clear label, but the suggestion of interrelationship or function is related to two-dimensional (vertical and horizontal) movement. Not give.

  Indeed, the 4-button “diamond” arrangement of FIGS. 20A and 20C and equivalents (eg, including a locking wheel and a locking dogbone) strongly suggests multidimensional motion along the horizontal and vertical axes. Therefore, this function is often automatically inferred. In addition, the physical relationship between buttons (such as horizontal and vertical placement) is easily inferred to correspond to the functions (such as horizontal and vertical movement) inherent in these buttons. Also, conventional techniques with multidimensionality that automatically infer multidimensional motion in space (in relation to X, Y and axes and various diagonals) are difficult to understand. For example, consider the “compass” button arrangement of FIG. 21A. This arrangement is naturally inferred to be associated with directions along four axes in a two-dimensional space, even without labels, as clearly shown by the similar arrangements of FIGS. 21B and 21C. However, in many user navigation contexts, functions that are related to each other simply based on the physical relationship of the buttons, for example, when vertical motion is important but horizontal motion is not important, and vice versa. Sometimes it may not be as efficient as possible.

  In order to maximize the versatility and applicability of a single user interface device in various contexts, another embodiment of the present invention is associated asymmetrically (not symmetrically) (ie, logically relative to each other). It consists of multiple symmetrical buttons that correspond to (unrelated) logical buttons (physically related to each other). For example, in one embodiment of the present invention with a 4-button multi-dimensional arrangement, such as the arrangement of FIG. And corresponding. Similarly, in another embodiment of the present invention, a horizontal button corresponds to a horizontal action and a vertical button corresponds to something other than a vertical action. In yet another embodiment, the horizontal button corresponds to something other than a horizontal action, and the vertical button corresponds to something other than a vertical action. Another embodiment using this method comprises a variety of symmetric pluralities, including, without limitation, a 4-button rhombus arrangement, an 8-button compass arrangement, a (super dogbone) and a locking bone (with a superwheel) locking Includes wheels, D-Pads, joysticks, various button arrangements, and / or combinations of the foregoing and their equivalents. Furthermore, the method is not limited to two-dimensional physical or logical embodiments, but provides true multidimensionality with respect to physical elements and logical functions.

(Conclusion)
Various techniques described in this specification are executed by hardware or software, or a combination thereof. Accordingly, the method and apparatus of the present invention, or some aspects or portions thereof, are contained within a tangible medium such as a floppy diskette, CD-ROM, hard drive, or other machine-readable storage medium. When the program code is stored and executed in a machine such as a computer, the machine becomes a device for executing the present invention. When the program code is executed on a programmable computer, the computer typically has a processor, a storage medium (volatile and non-volatile memory and / or storage elements) readable by the processor, at least one. One input device and at least one output device. The one or more programs are preferably executed in a high level procedural programming language or object oriented programming language to communicate with the computer system. However, the program is executed in assembly or machine language, if necessary. In any case, the language is compiled or interpreted and combined with the hardware implementation.

  The method and apparatus of the present invention may be transmitted over several transmission media, eg, electrical wiring or cable lines, through optical fibers, or in other transmission formats, where EPROM, gate array, programmable logic device (PLD) When a machine such as a client computer, video recorder, etc. receives, stores and executes the program code, the machine becomes a device for carrying out the present invention. When program code is implemented in a general-purpose processor, the program code combines with the processor to provide a unique apparatus that functions to achieve the indexing functionality of the present invention.

  Although the present invention has been described in connection with embodiments of the various drawings, other similar embodiments can be used and described without departing from the present invention in order to achieve the same function as the present invention. Changes or additions can be made to the described embodiments. For example, although one embodiment of the invention is described in the context of a digital device that emulates the functionality of a personal computer, those skilled in the art will recognize that the invention is not limited to that digital device. . The invention can also be applied to existing or emerging computer devices or computer environments such as game consoles, handheld computers, portable computers, mobile phones, watches, music players, certain mechanical devices, etc., whether wired or wireless. Regardless, it can also be applied to computer devices that are connected via a communication network or interacting across the network. In addition, for example, “buttons” (and other physical devices used herein) can vary in size, shape, spacing, etc., to enhance certain ergonomic effects. . Similarly, each button is labeled with a word, symbol, or not labeled, and is distinguished by giving the button a different color, shape, or other feature (or Do not distinguish).

  It should be emphasized that a variety of computer platforms including handheld device operating systems and other application specific operating systems are contemplated herein, particularly as the number of wireless network devices continues to increase. Accordingly, the present invention should not be limited to a single embodiment, but should be construed in breadth and scope based on the appended claims.

Claims (44)

In a method for extending the functionality of a navigational device comprising at least one logical button,
The logical button issuing a first command in a first context;
And a logical button for issuing a second command in a second context.   The method of claim 1, wherein the first command is not the same as the second command and the first context is not the same as the second context.   The method of claim 1, further comprising the logical button issuing a third command in a third context.   The method of claim 3, wherein the command is a step.   The method of claim 3, wherein the command is scrolling.   4. The method of claim 3, wherein the command is a page.   The method of claim 3, wherein the command is access.   4. The method of claim 3, wherein the command is abstract.   The method of claim 1, further comprising the logical button issuing an nth command in an nth context.   A system for performing the method of claim 1.   A computer readable medium having computer readable instructions for performing the method of claim 1.   A hardware control apparatus for executing the method according to claim 1. In a hardware control device comprising at least one logical button that issues a command when pressed,
Means for the logical button to issue a first command in a first context;
A hardware control device, wherein the logical button comprises means for issuing a second command in a second context. In a method for extending the functionality of a navigational control device comprising at least one logical button that issues a command when pressed,
Mapping a substitute command to a logical button if the button is used in a predetermined manner other than pressing;
Issuing a substitute command if the logical button is used in a predetermined manner other than pressing.   15. The method of claim 14, wherein if the logical button is used in a predetermined manner other than pressing, the logical button is pressed twice within a predetermined time frame and issues a substitute command.   15. The method of claim 14, wherein when the logical button is used in a predetermined manner other than pressing, the logical button is kept pressed for a predetermined time and issues a substitute command. In a method for extending the functionality of a navigational control device comprising at least one logical button for issuing commands when used by rolling,
Mapping a substitution command to a logical button if the logical button is used in a predetermined manner other than rolling; and
Issuing a substitute command if the logical button is used in a predetermined manner other than rolling.   18. The method of claim 17, wherein if the logical button is used in a predetermined manner beyond rolling, the logical button is tapped and issues a substitute command. In a method for extending the functionality of a navigational control device comprising at least one logical button that issues commands when used by locking,
Mapping a substitute command to a logical button if the logical button is used in a predetermined manner other than locking;
Issuing a substitute command if the logical button is used in a predetermined manner other than locking.   20. The method of claim 19, wherein if the logical button is used in a predetermined manner other than locking, the logical button remains locked and issues a substitute command. In a system for performing a method for extending the functionality of a navigational control device comprising at least one logical button that issues a command when used by pressing,
Mapping a substitute command to a logical button when the button is used in a predetermined manner other than pressing;
Issuing a substitute command when the logical button is used in a predetermined manner other than pressing.   The system of claim 21, wherein if the logical button is used in a predetermined manner other than pressing, the logical button is pressed twice within a predetermined time frame and issues a substitute command.   23. The system of claim 21, wherein when the logical button is used in a predetermined manner other than pressing, the logical button remains pressed for a predetermined time and issues a substitute command. In a system for performing a method for extending the functionality of a navigational control device comprising at least one logical button for issuing commands when used by rolling,
Mapping a substitution command to the logical button when the logical button is used in a predetermined manner other than rolling;
Issuing a substitute command when the logical button is used in a predetermined manner other than rolling.   25. The system of claim 24, wherein when the logical button is used in a predetermined manner other than rolling, the logical button is tapped and issues a substitute command. In a system for performing a method for extending the functionality of a navigational control device comprising at least one logical button that issues a command when used by locking,
Mapping a substitute command to a logical button when the logical button is used in a predetermined manner other than locking;
Issuing a substitute command when the logical button is used in a predetermined manner other than locking.   27. The system of claim 26, wherein if the logical button is used in a predetermined manner other than locking, the logical button remains locked and issues a substitute command. In a computer readable medium having computer readable instructions for a method of extending the functionality of a navigational control device comprising at least one logical button that issues a command when used by pressing, the method comprises:
Mapping a substitute command to a logical button when the button is used in a predetermined manner other than pressing;
Issuing a substitute command when the logical button is used in a predetermined manner other than pressing, a computer readable medium comprising:   29. The computer-readable medium of claim 28, wherein if the logical button is used in a predetermined manner other than pressing, the logical button is pressed twice within a predetermined time frame and issues a substitute command.   29. The computer according to claim 28, wherein when the logical button is used in a predetermined method other than pressing, the logical button remains pressed for a predetermined time and issues a substitute command. A readable medium. In a computer readable medium having computer readable instructions for a method for extending the functionality of a navigational control device comprising at least one logical button for issuing commands when used by rolling, the method comprises:
Mapping a substitute command to a logical button when the logical button is used in a predetermined manner other than rolling;
Issuing a substitute command when the logical button is used in a predetermined manner other than rolling.   32. The computer-readable medium of claim 31, wherein when the logical button is used in a predetermined manner other than rolling, the logical button is tapped and issues a substitute command. In a computer readable medium having computer readable instructions for a method of extending the functionality of a navigational control device comprising at least one logical button that issues commands when used by locking, the method comprises:
Mapping a substitute command to a logical button when the logical button is used in a predetermined manner other than locking;
Issuing a surrogate command when the logical button is used in a predetermined manner other than locking.   The computer-readable medium of claim 33, wherein the logical button remains locked and issues a substitute command when the logical button is used in a predetermined manner other than locking. In a hardware controller for a method for extending the functionality of a navigational controller comprising at least one logical button that issues a command when used by pressing, said method comprising:
Mapping a substitute command to a logical button when the button is used in a predetermined manner other than pressing;
Issuing a substitute command when the logical button is used in a predetermined method other than pressing, a hardware control device comprising:   36. The hardware control of claim 35, wherein when the logical button is used in a predetermined method other than pressing, the logical button is pressed twice within a predetermined time frame and issues a substitute command. apparatus.   36. The hardware according to claim 35, wherein when the logical button is used in a predetermined method other than pressing, the logical button is kept pressed for a predetermined time and a substitute command is issued. Wear control device. In a hardware control device comprising at least one logical button for issuing a command when used by pressing,
Means for mapping a substitute command to a logical button when the button is used in a predetermined manner other than pressing;
A hardware control device comprising means for issuing a substitute command when a logical button is used by a method other than pressing. In a hardware controller for a method for extending the functionality of a navigational controller comprising at least one logical button for issuing commands when used by rolling, said method comprises:
Mapping a substitution command to a logical button when the logical button is used in a predetermined manner other than rolling;
Issuing a substitute command when the logical button is used in a predetermined method other than rolling.   40. The hardware control device according to claim 39, wherein when the logical button is used in a predetermined method other than rolling, the logical button is tapped and issues a substitute command. In a hardware controller comprising at least one logical button for issuing a command when used by rolling,
Means for mapping a substitute command to a logical button when the logical button is used in a predetermined manner other than rolling;
A hardware control device comprising means for issuing a substitute command when the logical button is used in a predetermined method other than rolling. In a hardware controller for a method of extending the functionality of a navigational controller comprising at least one logical button that issues a command when used by locking, the method comprises:
Mapping a substitute command to a logical button when the logical button is used in a predetermined manner other than locking;
Issuing a substitute command when used in a predetermined method other than logical button locking.   43. The hardware control device according to claim 42, wherein when the logical button is used in a predetermined method other than locking, the logical button remains locked and issues a substitute command. In a hardware controller that includes at least one logical button that issues a command when used by locking,
Means for mapping a substitute command to a logical button if the logical button is used in a predetermined manner other than locking;
A hardware control device comprising: means for issuing a substitute command when the logical button is used by a predetermined method other than locking.

Images