SYSTEM, METHOD, AND COMPUTER-READABLE MEDIUM FOR DISPLAYING KEYBOARD CUES IN A WINDOW

Abstract

A mechanism for predicting whether user interface elements, such as keyboard cues, would be helpful to a computer user and either displaying or hiding the user interface elements based on that prediction is disclosed. Briefly described, an identification is made whether the last input device was a keyboard or a pointing device, such as a mouse. If the last input device was a pointing device, the keyboard cues are hidden. If the last input device was a keyboard, the keyboard cues are displayed. If the input device changes after the keyboard cues have been initially either hidden or displayed, a message so indicating is passed up the window hierarchy. Upon receiving the message, the top-level window responds by causing the display states of all the windows in the window hierarchy to be updated to reflect the changed input device.

Description

FIELD OF THE INVENTION

[0001] The present invention relates generally to computer software for displaying content on a computer display screen. More particularly, the present invention relates to computer software for displaying keyboard cues in a window portion of a computer display screen.

BACKGROUND OF THE INVENTION

[0002] Many users of computer systems become frustrated with excessive screen clutter. Some users dislike an application window that is cluttered with unnecessary graphics. Dialog box windows especially tend to suffer from this problem. For example, some operating systems provide keyboard cues such as focus indicators and keyboard accelerators. A focus indicator is typically a dashed-line box drawn on the screen within a button or around text that currently has the focus of the window. The focus indicator aids keyboard users identify what function will be activated by depressing the “enter” key on the keyboard. The focus indicator is unnecessary to users that rely heavily on a pointing device, such as a mouse, to input commands to the computer.

[0003] Keyboard accelerators are small lines that underline particular letters of words displayed in a control window. Usually, the underlined letter is depressed in combination with a keyboard key, such as the “Alt” key on keyboards commonly used with the Microsoft Windows operating system, to perform a function. Keyboard accelerators allow a user to select a control without having to navigate a pointing device to it. However, the keyboard accelerators are again of little benefit to a heavy mouse user. Moreover, the keyboard accelerators can sometimes confuse the novice keyboard user because the use of the keyboard accelerators is not intuitive. Accordingly, a need exists for a system or method for displaying or not displaying keyboard cues, such as focus indicators and keyboard accelerators, based on whether a user is predominantly a keyboard user or a mouse user.

SUMMARY OF THE INVENTION

[0004] The present invention allows a computer system to hide user interface elements, such as keyboard cues, based on whether the user is a keyboard user or a mouse user. Briefly stated, when a window is created, the window queries the system to determine whether the input that created the window resulted from a keyboard input device or a mouse input device. The window either displays or hides the keyboard cues based on that determination. In other words, the system predicts whether the keyboard cues are helpful to the user based on the last navigation mode, i.e. whether the user caused the window to be created with a keyboard or a mouse. If the input device that resulted in the window creation was a mouse, the window initially hides the keyboard cues. In this manner, extraneous window clutter is decreased for the mouse user. If the input device that resulted in the window creation was a keyboard, the keyboard cues are likely desired by the user and therefore displayed.

[0005] The window may change the display state of the keyboard cues. For example, the window may have been created with the keyboard cues initially hidden. If the window notices that the user has begun navigating with the keyboard, the window responds by displaying some or all of the keyboard cues. In one example, if the user depresses the “Tab” key to navigate from button to button or field to field, the window may display the focus indicator. In another example, if the user depresses the “Alt” key, the window may display the keyboard accelerators.

[0006] As is known to those skilled in the art, a window may have child windows. Examples of child windows are push buttons, radio buttons, check boxes, list boxes, scroll bars, and text-entry fields. The user may interact directly with a child window with either the mouse or keyboard, possibly resulting in a change in the display state of the keyboard cues in the child window. In that situation, rather than handling the change directly, the child window may pass that information to a window manager which, in turn, passes a message up the window hierarchy to the top-level window. The message may indicate that a change in the display state is warranted based on the input device used to navigate within the child window. The message does not, however, directly cause the change in the display state. When the message reaches the top-level window, the top-level window requests an update of the display state for itself and all its child windows. The system then issues commands to all the windows in the window hierarchy causing each of them to change their respective display states. This aspect ensures that the top-level window and all child windows share the same display state for the keyboard cues. Otherwise, the child window may change its display state while the remaining windows in the window hierarchy do not, resulting in some keyboard cues being displayed while others are not.

[0007] In some situations, allowing a child window to prevent a change to the display state of the keyboard cues may be desirable. In that case, a child window, such as a control container manager, may be configured to intercept the message being passed up the window hierarchy before it reaches the top-level window. The window procedure for the intercepting child window may be configured to respond to the message in any conventional way but without continuing to pass the message up the window hierarchy. Because the message does not reach the top-level window, the display states of all the windows in the window hierarchy remains unchanged. Alternatively, the control container manager may issue another message to the window manager to have only those controls updated.

BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The foregoing aspects and many of the attendant advantages of this invention will become more readily appreciated as the same becomes better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:

[0009] FIG. 1 is a block diagram of a computer suitable for providing an exemplary operating environment for the present invention;

[0010] FIGS. 2A-2C are exemplary screen displays of a window having child windows and illustrating one embodiment of the present invention in various stages of keyboard cue display;

[0011] FIG. 3 is a flow chart illustrating a process for creating a window and determining whether to display the keyboard cues based on a last navigation mode;

[0012] FIG. 4 is a flow chart illustrating in detail the step from FIG. 3 of initializing the display state (UISTATE) of a window; and

[0013] FIG. 5 is a flow chart illustrating in detail the step from FIG. 3 of updating the display state (UISTATE) of a window.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

[0014] The present invention provides a mechanism for predicting whether keyboard cues would be helpful to a computer user, and either displaying or hiding the keyboard cues based on that prediction. Briefly described, the invention identifies whether a last input device was a keyboard or a pointing device, such as a mouse. If the last input device was a pointing device, the keyboard cues are hidden. If the last input device was a keyboard, the keyboard cues are displayed. The display state of the keyboard cues may change if the input device changes after the keyboard cues have been initially either hidden or displayed. The present invention may be embodied in a computer operating system, such as the “Windows NT” operating system owned and licensed by the Microsoft Corporation of Redmond, Wash.

[0015] FIG. 1 and the following discussion are intended to provide a brief, general description of a suitable computing environment in which the invention may be implemented. While the invention will be described in the general context of an operating system executing on a personal computer, those skilled in the art will recognize that the invention also may be implemented in combination with other program modules. Generally, program modules include routines, programs, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

[0016] With reference to FIG. 1, an exemplary system for implementing the invention includes a conventional personal computer 20, including a processing unit 21, a system memory 22, and a system bus 23 that couples the system memory to the processing unit 21. The system memory 22 includes read only memory (ROM) 24 and random access memory (RAM) 25. A basic input/output system 26 (BIOS), containing the basic routines that help to transfer information between elements within the personal computer 20, such as during start-up, is stored in ROM 24. The personal computer 20 further includes a hard disk drive 27, a magnetic disk drive 28, e.g., to read from or write to a removable disk 29, and an optical disk drive 30, e.g., for reading a CD-ROM disk 31 or to read from or write to other optical media. The hard disk drive 27, magnetic disk drive 28, and optical disk drive 30 are connected to the system bus 23 by a hard disk drive interface 32, a magnetic disk drive interface 33, and an optical drive interface 34, respectively. The drives and their associated computer-readable media provide nonvolatile storage for the personal computer 20. Although the description of computer-readable media above refers to a hard disk, a removable magnetic disk, and a CD-ROM disk, it should be appreciated by those skilled in the art that other types of media which are readable by a computer, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, ZIP disks, and the like, may also be used in the exemplary operating environment.

[0017] A number of program modules may be stored in the drives and RAM 25, including an operating system 35, such as the Windows NT operating system mentioned above and having one embodiment of the present invention, one or more application programs 36, and program data 38. A user may enter commands and information into the personal computer 20 through input devices such as a keyboard 40 or a mouse 42. Other input devices (not shown) may include a microphone, touchpad, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 21 through a serial port interface 46 that is coupled to the system bus, but may be connected by other interfaces, such as a game port or a universal serial bus (USB). A monitor 47 or other type of display device is also connected to the system bus 23 via an interface, such as a video adapter 48. In addition to the monitor, personal computers typically include other peripheral output devices (not shown), such as speakers or printers.

[0018] The personal computer 20 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 49. The remote computer 49 may be a server, a router, a peer device, or other common network node, and typically includes many or all of the elements described relative to the personal computer 20, although only a memory storage device 50 has been illustrated in FIG. 1. The logical connections depicted in FIG. 1 include a local area network (LAN) 51 and a wide area network (WAN) 52. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet.

[0019] When used in a LAN networking environment, the personal computer 20 is connected to the LAN 51 through a network interface 53. When used in a WAN networking environment, the personal computer 20 typically includes a modem 54 or other means for establishing communications over the WAN 52. The modem 54 is connected to the system bus 23 via the serial port interface 46. The modem 54 may be internal or external, digital or analog, have a twisted-pair connection or coaxial cable connection, or any other type of modem capable of providing remote connectivity to the personal computer 20. In a networked environment, program modules depicted relative to the personal computer 20, or portions thereof, may be stored in the 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.

[0020] The present invention is best described by example. Accordingly, FIGS. 2A-2C are sample screen displays of a window having “child windows,” such as controls, and illustrating one embodiment of the present invention in various stages of keyboard cue display. To begin the example, FIG. 2A illustrates the situation where a new dialog box 200 is created. In FIG. 2A, the dialog box 200 is a Find dialog box of the type commonly used by word processing application programs. A dialog box is typically used to present information and receive input from a user.

[0021] The dialog box 200 includes a window 201, which is a top-level window. The window 201 is composed of several child windows, such as the match case control 203, the direction control 205, the text box 207, the Find Next push button 209, and the Cancel push button 211. As is known to those skilled in the art, each of the child windows 203-211 are subordinate in a window hierarchy to the top-level window 201.

[0022] The dialog box 200 was invoked by some input event. For example, a Find dialog box is often invoked by triggering a Find menu option of a word processing application. Typically, the user can trigger the Find menu option with either a keyboard 40 or a pointing device, such as a mouse 42. Although this discussion focuses primarily on the use of a mouse as a pointing device, the present invention is applicable to any pointing device, such as a touchpad, a graphics tablet, a stylus, a light pen, a joystick, a puck, a trackball, a voice-activated pointer, or the like. In accordance with the present invention, the operating system 35 identifies which of those two input devices (either the keyboard or a pointing device) was used to trigger the Find menu option. The operating system 35 uses the input-device information to set two state bits associated with the window 201. For this discussion, those two state bits are referred to as the “UISTATE” of the window 201. Each of the child windows 203-211 has its own UISTATE and will be discussed below.

[0023] One of the UISTATE state bits represents the display state of the focus indicator, and the other of the UISTATE state bits represents the display state of the keyboard accelerators. While this embodiment uses two state bits, those skilled in the art will appreciate that more or fewer state bits may be used to identify the display state of other keyboard cues or window elements. For instance, one state bit may be used to singularly identify the display state for all keyboard cues.

[0024] Returning to the example, in response to the Find menu item being triggered, the operating system 35 creates the window 201. As part of its creation, the window 201 initializes the display state of its keyboard cues based on its UISTATE stored by the operating system 35. In this example, the input device used to invoke the dialog box 200 was the mouse 42. Consequently, the UISTATE of the top-level window 201 was set to initially hide both the keyboard accelerators and the focus indicator. The window 201 is accordingly drawn with all its keyboard cues hidden.

[0025] When the window 201 causes each of its child windows 203-211 to be created, each of those child windows 203-211 inherits the UISTATE of the top-level window 201. As each child window 203-211 is created, it requests the UISTATE of the top-level window 201. Then, as each child window 203-211 is drawn, their respective keyboard cues are hidden as well. The result is a clean presentation of the dialog box 200 to the mouse user free of undesirable screen clutter. The operating system 35 predicted, because the last input device was the mouse 42, that the keyboard cues would be undesirable to the user. Alternatively, if the keyboard 40 had been used to invoke the dialog box 200, then, when the top-level window 201 was created, the operating system 35 would have initialized the UISTATE to display the keyboard cues. And when each child window 203-211 inherited the UISTATE of the top-level window 201, each child window 203-211 would also have displayed their respective keyboard cues.

[0026] Continuing with the example, FIG. 2B illustrates the situation where the user begins navigating within the dialog box 200 with the keyboard 40. The user begins navigating from one control to another by depressing the Tab key on the keyboard 40. As is known to those skilled in the art, when the dialog box 200 is first created, one control within the window 201, such as the text box 207, initially has the focus of the window 201. The Tab key of the keyboard 40 is commonly used to move the focus from one control to another control, such as from the text box 207 to the match case control 203. Other keyboard keys may be used as well, such as the directional arrows commonly found on typical keyboards.

[0027] In this example, the window 201 recognizes that the Tab key was used to move the focus from the text box 207 to the match case control 213. Based on that, the window 201 recognizes that the user has changed navigation modes, i.e. the input device being used to navigate within the dialog box 200, from the mouse 42 to the keyboard 40. In response, the window 201 requests the operating system 35 to update the UISTATE of all windows within the dialog box 200.

[0028] The operating system 35 responds by issuing a message to each window in the dialog box 200. The message includes the new UISTATE for the windows based on the new navigation mode. Each window passes the message to a default window procedure that handles the message and updates, internally, the UISTATES for each of the windows. The default window procedure then causes the windows to update their respective display states for the keyboard cues to match the new UISTATEs. In this embodiment, the display state of the focus indicator 213 is associated with the Tab key, but the display state of the keyboard accelerators is not. Accordingly, the UISTATE for each window in the dialog box 200 is updated to display the focus indicator 213 as the window receives the focus. However, the UISTATE for each window continues to reflect a hidden display state for the keyboard accelerators. As a result, when the user depresses the Tab key on the keyboard 40, the focus indicator 213 is displayed by each control as the focus moves from control to control.

[0029] FIG. 2C illustrates the situation where the user begins to navigate within the dialog box 200 using the keyboard accelerators. Typically, the Alt key is used in combination with one letter of a word displayed by a control to invoke that control. The window 201 recognizes that the user has depressed the Alt key and responds by issuing a command to the operating system 35 to change the UISTATEs of all the windows in the dialog box 200. The operating system 35 responds by updating the UISTATEs of the all the windows and issuing a command to the windows indicating that the keyboard accelerators should be displayed. Each of the windows responds by displaying their respective keyboard accelerators, such as the up accelerator 215, the down accelerator 217, the text box accelerator 219, and the match case accelerator 221. The final result is that the dialog box 200 is displayed with all the keyboard cues shown because the input device being used in the keyboard.

[0030] The present invention may also be described as a process for creating windows having keyboard cues appropriately shown or hidden depending on the input device used to invoke the window. FIGS. 3-5, taken in conjunction with FIGS. 1 and 2, illustrate that process.

[0031] FIG. 3 is a flow chart illustrating a process for creating a window and determining whether to display keyboard cues based on the navigation mode, i.e. the input device type being used to navigate within the window. The process enters at starting block 301 where an input event has invoked the creation of a window, such as window 201 or text box 207. The operating system 35 recognizes the type of input device that invoked the creation of the window and stores that information. Processing continues at block 303.

[0032] At block 303, the window is created. Creating the window may include creating a window procedure for handling input messages directed to the window. Creating the window may also include drawing elements of the window on the computer display screen as well as other administrative tasks performed during the creation of a window, as is known in the art. Processing continues at block 305.

[0033] At block 305, the window initializes its UISTATE prior to drawing the keyboard cues associated with the window. Block 305 is illustrated in detail in FIG. 4 and described in detail below. Briefly described, at block 305, the window requests that its UISTATE be initialized by the operating system 35. Based on the input-device information stored above, the operating system 35 sets two UISTATE bits associated with the window. One of the two UISTATE bits is used to indicate whether to hide the focus indicator. The other UISTATE bit is used to indicate whether to hide the keyboard accelerators. As is known to those skilled in the art, a value of “0” may indicate that the corresponding keyboard cue should be hidden, while a value of “1” may indicate that the keyboard cue is to be displayed. The operating system 35 returns the UISTATE to the window. Processing continues at block 307.

[0034] At block 307, the window is displayed with its keyboard cues in the proper state of display based on the window's UISTATE. In other words, the window is displayed with the focus indicator hidden if the corresponding state bit of the UISTATE so indicates. Likewise, the window is displayed with the keyboard accelerators shown if the other state bit of the UISTATE so indicates. As mentioned above, the state of the UISTATE bits is dependent on the last input device recognized by the operating system 35. Processing then continues at block 308.

[0035] At block 308, the window processes input messages directed to the window. As is known to those skilled in the art, a window has an associated message queue through which input messages are passed to the window. The window procedure for the window operates on each input message as appropriate, and when finished with one message, awaits the next. Processing remains at block 308 until a message is received that includes information about the navigation mode used to create the message, such as if the user depressed the Tab key on the keyboard 40. If, at block 308, the message includes information about the navigation mode, processing proceeds to decision block 309.

[0036] At decision block 309, the window determines, based on the navigation mode information from block 308, whether the navigation mode has changed. In other words, the window determines whether the message resulted from a different input device than previously used, such as if the input device previously being used was the mouse 42 but the keyboard 40 was used to issue the most recent message. If the window senses that the user has not changed the navigation mode within the window, then processing follows the No branch and returns to block 308 where the window continues to process messages. If, however, at decision block 309, the window senses that the navigation mode has changed from either the keyboard to the mouse or from the mouse to the keyboard, then processing follows the Yes branch and continues at block 311.

[0037] At block 311, the UISTATEs of all windows in the window hierarchy are updated to reflect the new navigation mode unveiled by the message at block 308. Block 311 is illustrated in detail in FIG. 5 and described below. Briefly described, at block 311, the window sends a message to the operating system 35 that causes the UISTATEs of all windows in the window hierarchy to be updated in accordance with the new navigation mode identified at decision block 309. Processing then returns to block 308 where the window continues processing messages in the window's message queue.

[0038] FIG. 4 is a flow chart illustrating in detail block 305 of the flow chart illustrated in FIG. 3. Block 305 involves the step of initializing the UISTATE of the window. The flow chart of FIG. 4 enters from block 303 where an event has occurred causing the creation of the window. Processing proceeds to decision block 313.

[0039] At decision block 313, a determination is made whether the current window being created is a top-level window. As discussed above, windows may exist in a window hierarchy having a top-level window and child windows for which the top-level window is the parent. The first window created in response to a triggering event is often, but not always, the top-level window. If the current window is not the top-level window, processing follows the No branch to block 319, discussed below. If the current window is the top-level window of the window hierarchy, processing follows the Yes branch to block 315.

[0040] At block 315, the current window requests the operating system 35 to initialize the UISTATEs for all windows in the window hierarchy for which the current window is the top-level. In one example, the current window may issue a “CHANGEUISTATE” message to the operating system 35. The CHANGEUISTATE message may indicate to the operating system 35 that a change in the UISTATE is being requested by the window. The CHANGEUISTATE message may have several parameters. One such parameter may be a “UI_INITIALIZE” statement that causes the operating system 35 to create and assign values to the UISTATE for the current window based on the last input device recognized by the operating system 35. As mentioned above, the operating system 35 monitors the input device type that invoked the creation of the current window. Accordingly, based on that input-device information, the operating system 35 responds to the UI_INITIALIZE parameter by assigning the proper value to the UISTATE bits of the current window. In addition, the operating system 35 may maintain an indication that the UISTATE of the current window is to be inherited by each child window of the current window. Processing proceeds from block 315 to block 317.

[0041] At block 317, the operating system 35 returns to the current window a message defining the current window's initial UISTATE based on the last input device. In this embodiment, that message may be an “UPDATEUISTATE” message having as a parameter the current UISTATE of the current window. The UPDATEUISTATE message may be an imperative message that causes the current window to either display or not display the keyboard cues based on the UISTATE parameter passed. For example, if the UISTATE reflects that the mouse was the last input device, then the UPDATEUISTATE message causes the current window to hide all keyboard cues. Processing then returns to block 308 of the flow chart illustrated in FIG. 3.

[0042] At block 319, to which the No branch of decision block 313 leads, the current window requests, from the operating system 35, the UISTATE of the current window inherited from its parent window. If processing reaches block 319, the current window is not a top-level window, it is a child window, such as the direction control 205 illustrated in FIG. 2. In that case, the operating system 35 assigned to the current window the UISTATE of its parent window when the creation of the current window began. Therefore, rather than requesting the operating system 35 to initialize the window's UISTATE based on the last input device, the window requests the operating system 35 to provide the UISTATE inherited from the parent window. The current window may send a “QUERYUISTATE” message to the operating system 35 requesting its UISTATE. Processing proceeds from block 319 to block 321.

[0043] At block 321, the operating system 35 returns the UISTATE of the current window. Because the UISTATE of each child window is inherited from its parent window, the entire window hierarchy reflects the same display state for the keyboard cues. In that manner, the user is presented with a consistent and aesthetic window appearance free of extraneous window clutter. From block 321, processing returns to block 308 of the flow chart illustrated in FIG. 3.

[0044] FIG. 5 is a flow chart illustrating in detail the block 311 shown in FIG. 3 that updates the UISTATE for the window hierarchy. The flow chart of FIG. 5 enters from decision block 309 where a determination was made that the navigation mode has changed. Processing begins at decision block 329.

[0045] At decision block 329, in response to the determination that the navigation mode has changed, a determination is made whether to allow that change to affect the display state of the keyboard cues. More specifically, some use of the keyboard may not result in a change to the display state of the keyboard. For example, if the user is currently typing text in a text box, such as text box 207, and begins navigating through the text using arrow keys on the keyboard rather than the mouse, that use of the keyboard may not warrant displaying the keyboard cues.

[0046] One mechanism for tolerating some keyboard use without changing the display state of the keyboard cues is to configure the window procedure of the current window to handle the CHANGEUISTATE message. As mentioned above and discussed below, the CHANGEUISTATE message indicates to the operating system 35 that a change in the UISTATE is being requested. If however, the window procedure of the current window is configured to handle the CHANGEUISTATE message, then the window procedure does not issue that message, as discussed below, to the operating system. In this manner, the disclosed embodiment provides a mechanism to allow a window to override the change in the display state of the keyboard cues. This concept will become more clear after the discussion below regarding block 339. If the window procedure for the current window handles the CHANGEUISTATE message, processing follows the Yes branch to block 331.

[0047] At block 331, the window procedure for the current window responds to the change in navigation mode as defined within that window procedure, rather than by sending the CHANGEUISTATE message to the operating system 35. By allowing the window procedure for the current window to handle the CHANGEUISTATE message, a window may prevent a change to its display state for the keyboard cues and the display state of all the windows in the window hierarchy. As will be apparent to those skilled in the art, the window procedure of the current window may be configured to handle the CHANGEUISTATE message in any conventional manner, such as by ignoring the message or making some other change to the display state of the window. Processing then returns from block 331 to block 308 of the flow chart illustrated in FIG. 3.

[0048] If, at decision block 329, the window procedure for the current window does not handle the CHANGEUISTATE message, processing follows the No branch to block 335. At block 335, the window procedure for the current window sends the CHANGEUISTATE message to the Default Window Procedure of the operating system 35. As is known to those skilled in the art, the Default Window Procedure is an operating system service that handles input and output messages that are not handled by a unique window procedure.

[0049] As discussed above, the CHANGEUISTATE message indicates to the operating system that a change in the UISTATE is being requested by the window. In addition to the UI_INITIALIZE parameter discussed above, other parameters may be passed with the CHANGEUISTATE message to indicate the proper state of the UISTATE bits. For example, a parameter of the nature “HIDEFOCUS=0” may be passed with the CHANGEUISTATE message. That parameter may instruct the operating system 35 to set one bit in the current window's UISTATE to reflect that the focus indicator should be displayed. Likewise, another parameter of the nature “HIDEACCEL=1” may instruct the operating system to set the other bit to reflect that the keyboard accelerators should be hidden.

[0050] The particular parameters selected to be passed with the CHANGEUISTATE message depend on the navigation mode information gathered at block 308 of the flow chart illustrated in FIG. 3. The navigation mode information indicates, if the input device was the keyboard 40, which key or key combination was depressed. Based on that information, this embodiment of the invention determines which parameters to pass and the value for each parameter. For example, depressing the Alt key may be used as an indication that the keyboard accelerators should be displayed because the Alt key is typically used to invoke a keyboard accelerated function. Consequently, if the navigation mode information gathered above indicates that the Alt key was depressed during the last input event, the window procedure for the current window selects a parameter, such as “HIDEACCEL=0,” to pass with the CHANGEUISTATE. On the other hand, because the Tab key is often used to navigate from one control to another control, if the navigation mode information indicates that the Tab key was depressed, a different parameter, such as “HIDEFOCUS=0,” may be selected. From block 335, processing proceeds to decision block 337.

[0051] At decision block 337, in response to the CHANGEUISTATE message from block 335, the Default Window Procedure first determines whether the current window is a top-level window. If the window is not a top-level window, processing follows the No branch to block 339.

[0052] At block 339, the Default Window Procedure sends the CHANGEUISTATE message, including the selected parameters, to the parent window of the current window. In this manner, the CHANGEUISTATE message is passed up the window hierarchy until it reaches the top-level window. No changes to the actual UISTATE bits of the windows in the window hierarchy occurs until the top-level window receives the CHANGEUISTATE message. When the Default Window Procedure passes the CHANGEUISTATE message to the parent window, the parent window becomes the current window and processing returns to decision block 329, which again performs as described above.

[0053] Those skilled in the art should now appreciate that decision block 329 provides the mechanism for any window in the window hierarchy between the window receiving the input message and the top-level window to intercept the CHANGEUISTATE message. In that way, a window may prevent a change to the display state for any or all of the keyboard cues if the window procedure of that window is configured to handle the CHANGEUISTATE message rather than pass it to the Default Window Procedure. For example, a control container window having multiple subordinate control windows may not be a top-level window. Allowing the window procedure for the control container window to intercept the CHANGEUISTATE message as it travels up the window hierarchy allows the control container window to independently dictate whether the UISTATEs of the subordinate controls, or any upper-level windows, are modified.

[0054] Returning to decision block 337, if a determination was made that the current window is a top-level window, processing follows the Yes branch and processing continues at block 341. At block 341, the Default Window Procedure, recognizing that the current window is the top-level window, updates the UISTATEs of all windows in the window hierarchy in accordance with the parameters passed with the CHANGEUISTATE message. In this way, all of the windows in the window hierarchy share the same UISTATE.

[0055] In addition, the Default Window Procedure sends another message, such as an “UPDATEUISTATE” message, to all the windows in the window hierarchy. The UPDATEUISTATE message may be an imperative message that causes each receiving window to alter its display of the keyboard cues in accordance with the new UISTATE. The Default Window Procedure may include parameters with the UPDATEUISTATE message similar to those passed with the CHANGEUISTATE message to indicate the proper display state for each of the keyboard cues. Consequently, each window in the window hierarchy receiving the UPDATEUISTATE message responds by either displaying or hiding the appropriate keyboard cues as defined by the parameters of the UPDATEUISTATE message. From block 341, processing returns to block 308 of the flow chart illustrated in FIG. 3.

[0056] Alternative Embodiments

[0057] While embodiments of the invention have been illustrated and described, it will be appreciated that various changes and modifications can be made without departing from the spirit and scope of the invention. For example, those skilled in the art will appreciate that the parameters and values provided in this description are merely examples and many other parameters associated with many other keyboard keys or input devices will become obvious upon a study of this discussion, and are equivalent to the examples provided here. For example, if the mouse is identified as the last input device, parameters such as “HIDEACCEL=1” and “HIDEFOCUS=1” may simultaneously be passed.

[0058] In addition, other user interface elements not specifically identified here may be displayed or hidden in an equivalent manner through the use of the present invention. For instance, the present invention may be applied to many other user interface elements, such as three-dimensional versus two-dimensional display elements, color versus black-and-white display, icon toolbars versus textual menus, graphical icons versus text-based icons, or the like. Other input devices may also be used in a system embodying the present invention, such as a voice-recognition navigation mechanism.

[0059] As another alternative, the benefits of the present invention may provide the ability to force “user interface modes” to accommodate particular users' needs or preferences. For example, keyboard use is not always a matter of personal preference, but may be an accessibility issue for some people. Keyboard cues have a critical value for people that cannot use a mouse. Unfortunately, with existing technologies, software applications can alter the display state of the keyboard cues programmatically. That capability can result in keyboard cues being turned off inappropriately, i.e. even when the user is using the keyboard out of necessity. Therefore, a configuration switch may be used in combination with the present invention to force the display state of the keyboard cues to a predetermined state. The operating system may be configured to override a software application's attempt to alter the display state of the keyboard cues. The configuration switch may also be used to allow the user to customize the behavior of the system. Moreover, the configuration switch addresses the issue of backward compatibility by allowing the system to simulate the behavior of existing technologies. Thus, the embodiments described are for illustrative purposes only, and the present invention is limited only by the following claims.

Claims

1. A computer-readable medium having computer-executable instructions for displaying a window, which, when executed, comprise: recognizing a first input event that invokes the creation of the window; identifying an input device type associated with the first input event; if the input device type associated with the first input event is not a keyboard, displaying the window with a user interface element hidden.

2. The computer-readable medium of claim 1, further comprising: if the input device type associated with the first input event is the keyboard, displaying the window with the user interface element displayed.

3. The computer-readable medium of claim 1, further comprising: recognizing a second input event associated with the window; identifying the input device type associated with the second input event; and if the input device type associated with the second input event is different from the input device type associated with the first input event, changing the display state of the user interface element.

4. The computer-readable medium of claim 1, wherein the user interface element is a keyboard cue.

5. The computer-readable medium of claim 4 wherein the input device associated with the first input event is not a keyboard and the input device associated with the second input event is the keyboard, further comprising changing the display state of the keyboard cue from hidden to displayed.

6. The computer-readable medium of claim 5, wherein if the second input event includes depressing a pre-selected key on the keyboard, displaying a corresponding keyboard cue.

7. The computer-readable medium of claim 6, wherein the pre-selected key is an Alt key on the keyboard and the corresponding keyboard cue is a keyboard accelerator.

8. The computer-readable medium of claim 6, wherein the pre-selected key is a Tab key on the keyboard and the corresponding keyboard cue is a focus indicator.

9. In a computer system having an operating system, the operating system configured to display windows in a window hierarchy wherein a top-level window is superior to a child window, a method of displaying a keyboard cue, comprising: recognizing a first input event, triggered by an input device, that invokes the creation of a window in the window hierarchy; passing to the window a state indicator configured to reflect the input device; in response to one state of the state indicator, displaying the window with the keyboard cue displayed; and in response to a second state of the state indicator, displaying the window with the keyboard cue hidden.

10. The method of claim 9, further comprising: recognizing a second input event; determining if the second input event was triggered by the input device; if the second input event was not triggered by the input device, causing the state of the state indicator to be changed to reflect that the second input event was not triggered by the input device; and updating the display of the window to reflect the changed state indicator.

11. The method of claim 10, wherein the input device is a pointing device and further comprising: if the second input event includes depressing a pre-selected key on a keyboard, displaying a corresponding keyboard cue.

12. The method of claim 11, wherein the pre-selected key is an Alt key on the keyboard and the corresponding keyboard cue is a keyboard accelerator.

13. The method of claim 11, wherein the pre-selected key is a Tab key on the keyboard and the corresponding keyboard cue is a focus indicator.

14. The method of claim 9, further comprising: recognizing a second input event; determining if the second input event was triggered by the input device; if the second input event was not triggered by the input device, determining if the window is the top-level window in the window hierarchy; and if the window is the top-level window in the window hierarchy, causing the state of the state indicator to be changed to reflect that the second input event was not triggered by the input device.

15. The method of claim 14, further comprising causing all of the windows in the window hierarchy to be updated to reflect the changed state indicator.

16. The method of claim 14, further comprising if the window is not the top-level window in the window hierarchy, passing to a parent window of the window a request to change the state of the state indicator to reflect that the second input event was not triggered by the input device.

17. The method of claim 16, further comprising: upon the receipt by the parent window of the request to change the state of the state indicator, causing the state of the state indicator to be changed to reflect that the second input event was not triggered by the input device; and causing all of the windows in the window hierarchy to be updated to reflect the changed state indicator.

18. The method of claim 16, further comprising: upon the receipt by the parent window of the request to change the state of the state indicator, handling the request within the parent window.

19. The method of claim 14, wherein: if the window is not the top-level window in the window hierarchy, causing a message to be passed up the window hierarchy to the top-level window requesting a change to the state of the state indicator to reflect that the second input event was not triggered by the input device

20. A computer-readable medium having computer-executable instructions for displaying a window in a window hierarchy, which when executed, comprise: recognizing that an input event directed to a current window in the window hierarchy was generated by an input device different from a prior input device; identifying whether the current window is a top-level window in the window hierarchy; if the current window is not the top-level window in the window hierarchy, passing a message up the window hierarchy indicating a change in the input device; and receiving from an operating system a message directing the current window to: if the input device that generated the input event is a keyboard, display a keyboard cue in the current window.

21. The computer-readable medium of claim 20, further comprising: if the input device that generated the input event is a pointing device, hiding a keyboard cue in the current window.

22. A computer-implemented method for displaying a window having a user interface element, comprising: identifying a last input device; and if the last input device is a pointing device, hiding the user interface element as the window is displayed.

23. The computer-implemented method of claim 21, wherein the pointing device is a selected one from a group comprising a mouse, a touchpad, a graphics tablet, a stylus, a light pen, a joystick, a puck, a trackball, and a voice-activated pointer.

24. A computer-implemented method for causing a window to be displayed in a user interface mode, comprising: providing an identifier associated with the window and configured to identify the user interface mode; and based on the state of the identifier, displaying the window in the identified user interface mode.

25. The computer-implemented method of claim 24, wherein the user interface mode comprises a display state for at least one screen display element.

26. The computer-implemented method of claim 25, wherein the at least one screen display element comprises a keyboard cue.

27. The computer-implemented method of claim 24, wherein displaying the window in the identified user interface mode comprises: issuing to the window a command, based on the identifier, causing the window to be displayed in the identified user interface mode.

28. The computer-implemented method of claim 24, wherein the window is associated with a window hierarchy including at least one child window of the window, and further comprising: issuing to the window hierarchy a series of commands, based on the identifier, causing all the windows in the window hierarchy to be displayed in the identified user interface mode.

29. The computer-implemented method of claim 28, wherein the identifier is maintained by an operating system and wherein the operating system is configured to override an attempt by a software application to alter the user interface mode.

30. The computer-implemented method of claim 29, wherein the identifier is set by sensing an input event.

31. The computer-implemented method of claim 29, wherein the identifier is set by pre-selecting the user interface mode with a configuration setting maintained by the operating system.