User interface with stacked application management

RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application Ser. No. 61/389,000, filed Oct. 1, 2010, entitled “DUAL DISPLAY WINDOWING SYSTEM”; Provisional Application Ser. No. 61/389,117, filed Oct. 1, 2010, entitled “MULTI-OPERATING SYSTEM PORTABLE DOCKETING DEVICE”; and Provisional Application Ser. No. 61/389,087, filed Oct. 1, 2010, entitled “TABLET COMPUTING USER INTERFACE”. Each and every part of the foregoing provisional applications is hereby incorporated by reference in their entirety.

BACKGROUND

As the computing and communication functions of handheld computing devices become more powerful, the user interface and display elements of such devices have evolved by attempting to adapt user interface regimes developed for personal computers for use with handheld computing devices. However, this attempt to adapt prior user interface regimes has been met with various hurdles.

For instance, the majority of current handheld computing devices make use of a physical keypad for user interface. Many different implementations of physical keypads exist that vary in orientation and relationship to the device screen. However, in every case the physical keypads take up a certain percentage of the physical space of the device and increase the weight of the device. In addition to the disadvantages of size and weight, physical keypads are not configurable in the same manner as a touch screen based user interface. While certain limited forms of physical keypads currently have, on the keys themselves, configurable displays, such as eInk or OLED surfaces, to allow for reconfiguration of the keys, even in these cases, the physical layout of keys is not modifiable. Rather, only the values associated with the physical keys on the keypad may be changed.

Other methods may provide increased user configurability of physical keypads. These methods may include stickers and/or labels that can be added to keys to reference modified functions or plastic overlays on top of the keypad denoting different functional suites. For instance, the ZBoard keyboard, meant for laptop or desktop computer use, incorporates a dual layered physical keyboard which separates the keys and their layout from the connections which send signals to the machine. As such, different physical keyboard inserts for different applications can be inserted into a holder allowing full configurability such that the orientation and layout of the keys in addition to their denotation of function is configurable. This model could be extended to handheld computing devices; however, the rate at which such a modular keypad can change functions is much slower than a touch screen user interface. Furthermore, for each potential functional suite, an additional physical key layout must be carried by the user, greatly increasing the overall physical size and weight of such implementations. One advantage of a physical keypad for handheld computing devices is that the user input space is extended beyond the user display space such that none of the keys themselves, the housing of the keys, a user's fingers, or a pointing device obscure any screen space during user interface activities.

A substantial number of handheld computing devices make use of a small touch screen display to deliver display information to the user and to receive inputs from the user. In this case, while the configurability of the device may be greatly increased and a wide variety of user interface options may be available to the user, this flexibility comes at a price. Namely, such arrangements require shared screen space between the display and the user interface. While this issue is shared with other types of touch screen display/user interface technology, the small form factor of handheld computing devices results in a tension between the displayed graphics and area provided for receiving inputs. For instance, the small display further constrains the display space, which may increase the difficulty of interpreting actions or results while a keypad or other user interface scheme is laid overtop or to the side of the applications in use such that the application is squeezed into an even smaller portion of the display. Thus a single display touch screen solution, which solves the problem of flexibility of the user interface may create an even more substantial set of problems of obfuscation of the display, visual clutter, and an overall conflict of action and attention between the user interface and the display.

Single display touch screen devices thus benefit from user interface flexibility, but are crippled by their limited screen space such that when users are entering information into the device through the display, the ability to interpret information in the display can be severely hampered. This problem is exacerbated in several key situations when complex interaction between display and interface is required, such as when manipulating layers on maps, playing a game, or modifying data received from a scientific application. This conflict between user interface and screen space severely limits the degree to which the touch based user interface may be used in an intuitive manner.

SUMMARY

A first aspect includes a method for controlling a handheld computing device. The method includes logically associating one or more applications with a first display of the handheld computing device. Additionally, the method involves establishing a first application stack corresponding to the one or more applications logically associated with the first display. The method also includes receiving a gesture input at a gesture sensor of the handheld computing device. Furthermore, the method includes moving a first application belonging to the first application stack to a second application stack associated with a second display in response to the receiving step such that the first application is logically associated with the second display.

A second aspect includes a method of controlling a handheld computing device. The method includes receiving a first portion of a gesture input and targeting the first portion of the gesture input to a first display having a first actively displayed screen corresponding to a first application. In turn, the method includes maintaining the first actively displayed screen in the first display in response to the first portion of the gesture input. Additionally, the method includes receiving a second portion of the gesture input and targeting a different screen than the actively displayed screen in the first display with the second portion. As a result, the different screen undergoes a change in position with respect to the first display and at least a second display in response to the second portion of the gesture input.

A third aspect includes a system for controlling a handheld computing device. The system includes a processor, and a first display and a second display that are in operative communication with the processor. The system further includes a gesture sensor that is in operative communication with the processor and is operative to receive a gesture input. The gesture input is interpretable by the processor to move an application from a first application stack associated with the first display to a second application stack associated with the second display.

A number of feature refinements and additional features are applicable to the foregoing aspects. These feature refinements and additional features may be used individually or in any combination. As such, each of the following features that will be discussed may be, but are not required to be, used with any other feature or combination of features of any of the aspects presented herein.

In one embodiment, the first application may be an actively displayed screen of the first display prior to the moving step. The first application may, in turn, be an actively displayed screen of the second display after the moving step. As such, an underlying screen may be revealed in the first display after the moving step. The underlying screen may be one of a desktop screen and an application screen corresponding to a second application logically associated with the first display such that the second application belongs to the first application stack. The first application may obscure a second screen in the second display that comprises an actively displayed screen of the second display prior to the moving step. In yet another embodiment, the moving may further include that the first application is expanded to be the actively displayed screen of the first display and the actively displayed screen of the second display such that the first application belongs to the first application stack and the second application stack.

In another embodiment, the gesture input may have a first gesture portion and a second gesture portion. The gesture input comprises a pin and drag gesture. As such, the first gesture portion may maintain the actively displayed screen in a corresponding application stack, and the second gesture portion may result in movement of the first application relative to the actively displayed screen of the corresponding application stack. As such, the corresponding application stack may the first application stack, and the second gesture portion may be directed away from the first gesture portion. The first application may be revealed in the second display after the moving step. Additionally or alternatively, the corresponding application stack may the second application stack, and the second gesture portion may be directed toward the first gesture portion. In this regard, the first application may be hidden in the second display after the moving step.

In still another embodiment, the first portion and the second portion of the gesture input may be received at a gesture sensor associated with the first display such that the different screen corresponds to a second application residing behind said first application. The first portion of the gesture input may be received at a gesture sensor associated with the first display and the second portion of the gesture input may be received at a gesture sensor associated with the second display. The different screen may be moved from the second display to the first display behind the first screen. The screens targeted in the corresponding may at least partially depend upon a location where the corresponding portion of the gesture input is received.

BRIEF DESCRIPTION OF THE DRAWINGS

<figref idref="DRAWINGS">FIG. 1</figref> is a schematic view of an embodiment of a handheld computing device.

<figref idref="DRAWINGS">FIGS. 2A-D</figref> are graphical representations of an embodiment of a handheld computing device in various instances of operation.

<figref idref="DRAWINGS">FIGS. 3A-K</figref> are graphical representations of an embodiment of a handheld computing device provided in different positions, orientations, and instances of operation.

<figref idref="DRAWINGS">FIG. 4</figref> includes graphical representations of various gesture inputs for controlling a handheld computing device.

<figref idref="DRAWINGS">FIG. 5</figref> is a graphical representation of the relative positions of screens executing on displays of an embodiment of a handheld computing device.

<figref idref="DRAWINGS">FIGS. 6A-6C</figref> are graphical representations of an embodiment of a handheld computing device functioning in response to a gesture input.

<figref idref="DRAWINGS">FIGS. 7A-7B</figref> are graphical representations of the embodiment of the handheld computing device shown in <figref idref="DRAWINGS">FIGS. 6A-6C</figref> functioning in response to a different gesture input.

<figref idref="DRAWINGS">FIGS. 8A-8E</figref> are graphical representations of another embodiment of a handheld computing device functioning in response to a gesture input.

<figref idref="DRAWINGS">FIGS. 9A and 9B</figref> are schematic views of embodiments of a handheld computing device provided with touch sensitive devices.

<figref idref="DRAWINGS">FIG. 10</figref> is a graphical representation of an embodiment of a gesture input.

DETAILED DESCRIPTION

The present disclosure is generally related to gesture inputs for interaction with a computing device. The interface controls are particularly suited for control of devices that have one or more displays capable of displaying graphical user interfaces (GUIs) on a handheld portable device. The following disclosure may, in various embodiments, be applied to other computing devices capable of displaying and responding to a GUI (e.g., laptop computers, tablet computers, desktop computers, touch screen monitors, etc.) and is not intended to be limited to handheld computing devices unless otherwise explicitly specified.

<figref idref="DRAWINGS">FIG. 1</figref> depicts an embodiment of a handheld computing device <b>100</b>. The handheld computing device <b>100</b> may include a first display <b>102</b> and a second display <b>104</b>. Additionally, while two displays (<b>102</b>, <b>104</b>) may be shown and described below with regard to the functionality of various embodiments of handheld computing devices, a handheld computing device may be provided that includes one or more displays. In any regard, the first display <b>102</b> and the second display <b>104</b> may be independently controllable. The displays may be operative to display a rendered image or screen. As used herein, the term “display” is intended to connote device hardware, whereas “screen” is intended to connote the displayed image rendered on the display. In this regard, a display is a physical hardware that is operable to render a screen. A screen may encompass a majority of the display. For instance, a screen may occupy substantially all of the display area except for areas dedicated to other functions (e.g., menu bars, status bars, etc.) Alternatively or additionally, a screen may occupy more than one display. A screen may be associated with an application and/or an operating system executing on the handheld computing device <b>100</b>. For instance, application screens or desktop screens may be displayed. An application may have various kinds of screens that are capable of being manipulated as will be described further below. In an embodiment, each display may have a resolution of 480 pixels by 800 pixels, although higher and lower resolution displays may also be provided.

A screen may be associated with an operating system, an application, or the like. In some instances, a screen may include interactive features (e.g., buttons, text fields, toggle fields, etc.) capable of manipulation by way of a user input. The user input may be received by various input devices (e.g., a physical keyboard, a roller ball, directional keys, a touch sensitive device, etc.). In some instances, a screen may simply include graphics and have no ability to receive an input by a user. In other instances, graphics features and input features may both be provided by a screen. As such, the one or more displays, the screens displayed on the one or more displays, and various user input devices may comprise a GUI that allows a user to exploit functionality of the handheld computing device.

The handheld computing device <b>100</b> may be configurable between a first position and a second position. In the first position, a single display (e.g., the first display <b>102</b> or the second display <b>104</b>) may be visible from the perspective of a user. Both displays <b>102</b> and <b>104</b> may be exposed on an exterior of the handheld device <b>100</b> when in the first position, but the displays <b>102</b> and <b>104</b> may be arranged in a non-adjacent manner such that both displays <b>102</b>, <b>104</b> are not concurrently visible from the perspective of a user (e.g., one display may be visible from the front of the device <b>100</b> and the other display may be visible from the back of the device <b>100</b>).

The handheld computing device <b>100</b> may also be provided in the second position such that the displays <b>102</b>, <b>104</b> may be concurrently viewable from the perspective of a user (e.g., the displays <b>102</b>, <b>104</b> may be positioned adjacent to one another). The displays <b>102</b>, <b>104</b> may be displayed in the second position such that the displays <b>102</b>, <b>104</b> are arranged end-to-end or side-by-side. Additionally, the displays <b>102</b>, <b>104</b> may be arranged in a portrait orientation or a landscape orientation with respect to a user. As will be discussed further below, a portrait orientation is intended to describe an arrangement of the handheld computing device, wherein the longer dimension of the display of the handheld computing device is vertically oriented (e.g., with respect to gravity or the perspective of a user). A landscape orientation is intended to describe an arrangement wherein the shorter dimension of the display of the handheld computing device is vertically oriented (e.g., with respect to gravity or the perspective of a user). Furthermore, the longer dimension and shorter dimension may refer to each display individually or the combined viewing area of the one or more displays of the device. Thus, when the individual displays are arranged in a portrait orientation, the overall display area may be arranged in a landscape orientation, and vice versa. Additionally, the displays and screens may be in different respective orientations. For instance, when the displays are in a landscape orientation, one or more screens may be rendered in a portrait orientation on the displays or vice versa.

The handheld computing device <b>100</b> may be manipulated between the first position (e.g., a single display visible from a user's perspective) and the second position (e.g., at least two displays concurrently visible from the user's perspective) in a variety of manners. For instance, the device <b>100</b> may include a slider mechanism such that the first and second displays <b>102</b>, <b>104</b> are disposable adjacent to one another in a parallel fashion in a second position and slideable to the first position where only a single display is viewable and the other display is obscured by the viewable display.

Alternatively, the device <b>100</b> may be arranged in a clam shell type arrangement wherein a hinge is provided between the first display <b>102</b> and the second display <b>104</b> such that the displays <b>102</b>, <b>104</b> are concurrently visible by a user when in the second position (i.e., an open position). The displays <b>102</b>, <b>104</b> may be provided on an interior clam shell portion or an exterior clam shell portion of the device <b>100</b>. In this regard, both displays <b>102</b>, <b>104</b> may be visible from the front and the back of the device, respectively, when the device is in the first position (i.e., the closed position). When the device <b>100</b> is in the open position, the displays <b>102</b>, <b>104</b> may be provided adjacent and parallel to one another. Alternative arrangements of the handheld computing device <b>100</b> are contemplated wherein different arrangements and/or relative locations of the displays may be provided when in the first and second position.

In addition, the first display <b>102</b> and the second display <b>104</b> may be provided as entirely separate devices. In this regard, a user may manipulate the displays <b>102</b>, <b>104</b> such that they may be positioned adjacent to one another (e.g., side-by-side or end-to-end). The displays <b>102</b>, <b>104</b> may be in operative communication when adjacently positioned such that the displays <b>102</b>, <b>104</b> may operate in the manner provided in greater detail below when adjacently positioned (e.g., via physical contacts, wireless communications, etc.). A retention member (not shown) may be provided to retain the separate displays <b>102</b>, <b>104</b> in an adjacent position. For instance, the retention member may include coordinating magnets, mechanical clips or fasteners, elastic members, etc.

While the foregoing has referenced two displays <b>102</b> and <b>104</b>, alternate embodiments of a handheld device may include more than two displays. In this regard, the two or more displays may behave in a manner in accordance with the foregoing wherein only a single display is viewable by a user in a first position and multiple displays (i.e., more than two displays) are viewable in a second position. Additionally, in one embodiment, the two displays <b>102</b> and <b>104</b> may comprise separate portions of a unitary display (not shown). As such, the first display <b>102</b> may be a first portion of the unitary display and the second display <b>104</b> may be a second portion of the unitary display. For instance, the handheld computing device <b>100</b> (e.g., having a first and second display <b>102</b> and <b>104</b>) may be operatively connected to the unitary display (e.g., via a connector or a dock portion of the unitary display) such that the first display <b>102</b> and the second display <b>104</b> of the handheld computing device <b>100</b> are emulated on the unitary display. As such, the unitary display may have first and second portions corresponding to and acting in a similar manner to the first and second display <b>102</b> and <b>104</b> of the handheld computing device <b>100</b> described below.

The handheld computing device <b>100</b> may further include one or more input devices that may be used to receive user inputs. These input devices may be operative to receive gesture inputs from a user, and, accordingly, may be referred to generally as gesture sensors. A number of different types of gesture sensors may be provided. Some examples include, but are not limited to traditional input devices (keypads, trackballs, etc.), touch sensitive devices, optical sensors (e.g., a camera or the like), etc. The discussion contained herein may reference the use of touch sensitive devices to receive gesture inputs. However, the use of touch sensitive devices is not intended to limit the means for receiving gesture inputs to touch sensitive devices alone and is provided for illustrative purposes only. Accordingly, any of the foregoing means for receiving a gesture input may be used to produce the functionality disclosed below with regard to gesture inputs received at touch sensitive devices.

In this regard, the handheld computing device <b>100</b> may include at least a first touch sensor <b>106</b>. Furthermore, the handheld computing device may include a second touch sensor <b>108</b>. The first touch sensor <b>106</b> and/or the second touch sensor <b>108</b> may be touchpad devices, touch screen devices, or other appropriate touch sensitive devices. Examples include capacitive touch sensitive panels, resistive touch sensitive panels, or devices employing other touch sensitive technologies. The first touch sensor <b>106</b> and/or second touch sensor <b>108</b> may be used in conjunction with a portion of a user's body (e.g., finger, thumb, hand, etc.), a stylus, or other acceptable touch sensitive interface mechanisms known in the art. Furthermore, the first touch sensor <b>106</b> and/or the second touch sensor <b>108</b> may be multi-touch devices capable of sensing multiple touches simultaneously.

The first touch sensor <b>106</b> may correspond to the first display <b>102</b> and the second touch sensor <b>108</b> may correspond to the second display <b>104</b>. In one embodiment of the handheld computing device <b>100</b>, the first display <b>102</b> and the first touch sensor <b>106</b> comprise a first touch screen display <b>110</b>. In this regard, the first touch sensor <b>106</b> may be transparent or translucent and positioned with respect to the first display <b>102</b> such that a corresponding touch received at the first touch sensor <b>106</b> may be correlated to the first display <b>102</b> (e.g., to interact with a screen rendered on the first display <b>102</b>). Similarly, the second display <b>104</b> and the second touch sensor <b>108</b> may comprise a second touch screen display <b>112</b>. In this regard, the second touch sensor <b>108</b> may be positioned with respect to the second display <b>104</b> such that a touch received at the second touch sensor <b>108</b> may be correlated to the second display <b>104</b> (e.g., to interact with a screen rendered on the second display <b>104</b>). Alternatively, the first touch sensor <b>106</b> and/or the second touch sensor <b>108</b> may be provided separately from the displays <b>102</b>, <b>104</b>. Furthermore, in an alternate embodiment, only a single gesture sensor may be provided that allows for inputs to control both the first display <b>102</b> and the second display <b>104</b>. The single gesture sensor may also be provided separately or integrally with the displays.

In this regard, the first and second touch sensors <b>106</b>, <b>108</b> may have the substantially same footprint on the handheld computing device <b>100</b> as the displays <b>102</b>, <b>104</b>. Alternatively, the touch sensors <b>106</b>, <b>108</b> may have a footprint including less of the entirety of the displays <b>102</b>, <b>104</b>. Further still, the touch sensors <b>106</b>, <b>108</b> may include a footprint that extends beyond the displays <b>102</b>, <b>104</b> such that at least a portion of the touch sensors <b>106</b>, <b>108</b> are provided in non-overlapping relation with respect to the displays <b>102</b>, <b>104</b>. As discussed further below, the touch sensors <b>106</b>, <b>108</b> may alternatively be provided in complete non-overlapping relation such that the footprint of the touch sensors <b>106</b>, <b>108</b> is completely different than the footprint of the displays <b>102</b>, <b>104</b>.

With reference to <figref idref="DRAWINGS">FIGS. 10A and 10B</figref>, various potential arrangements are depicted for the first display <b>102</b>, the second display <b>104</b>, and touch sensors <b>106</b>′, <b>106</b>″, and <b>108</b>″. In <figref idref="DRAWINGS">FIG. 10A</figref>, the first <b>102</b> and second display <b>104</b> are arranged side-by-side such that a crease <b>196</b> separates the displays. In this regard, the first display <b>102</b> and second display <b>104</b> may be arranged in a clam-shell type arrangement such that the crease <b>196</b> includes a hinge that allows for pivotal movement between the first display <b>102</b> and second display <b>104</b> as discussed above. A touch sensor <b>106</b>′ may span the width of both the first display <b>102</b> and the second display <b>104</b>. In this regard, the touch sensor <b>106</b>′ may span the crease <b>196</b> without interruption. Alternatively, as shown in <figref idref="DRAWINGS">FIG. 10B</figref>, separate touch sensors <b>106</b>″ and <b>108</b>″ may be provided on either side of the crease <b>196</b>. In this regard, each of the touch sensors <b>106</b>″ and <b>108</b>″ may span the width of each of the first display <b>102</b> and second display <b>104</b>, respectively.

In any of the arrangements shown in <figref idref="DRAWINGS">FIGS. 10A and 10B</figref>, the displays (<b>102</b>, <b>104</b>) may also comprise touch screen displays that may be used in conjunction with touch sensitive portions that are provided separately from the touch screen displays. Thus, displays <b>102</b> and <b>104</b> may both comprise touch screen displays and be provided in addition to touch sensitive devices <b>106</b>′, <b>106</b>″, and <b>108</b>″. Accordingly, a combination of touch screen displays (e.g., <b>110</b>, <b>112</b>) and off display touch sensors (e.g., <b>106</b>′, <b>106</b>″, <b>108</b>″) may be provided for a single device. Touch inputs may be received at both a touch screen display (<b>110</b>, <b>112</b>) and off display touch sensor (<b>106</b>′, <b>106</b>″, <b>108</b>″). In this regard, gestures received at an off screen display sensor may have a different functionality than the same gesture received at a touch screen display. Also, a touch sensitive device may be divided into a plurality of zones. The same gesture received in different zones may have different functionality. For instance, a percentage (e.g., 10%, 25%, etc.) of the touch sensitive device at the top or bottom of the display may be defined as a separate zone than the remainder of the touch sensitive device. Thus, a gesture received in this zone may have a different functionality than a gesture received in the remainder of the touch sensitive device.

The handheld computing device <b>100</b> may further include a processor <b>116</b>. The processor <b>116</b> may be in operative communication with a data bus <b>114</b>. The processor <b>116</b> may generally be operative to control the functionality of the handheld device <b>100</b>. For instance, the processor <b>116</b> may execute an operating system and be operative to execute applications. The processor <b>116</b> may be in communication with one or more additional components <b>120</b>-<b>134</b> of the handheld computing device <b>100</b> as will be described below. For instance, the processor <b>116</b> may be in direct communication with one more of the additional components <b>120</b>-<b>134</b> or may communicate with the one or more additional components <b>120</b>-<b>134</b> via the data bus <b>114</b>. Furthermore, while the discussion below may describe the additional components <b>120</b>-<b>134</b> being in operative communication with the data bus <b>114</b>, in other embodiments any of the additional components <b>120</b>-<b>134</b> may be in direct operative communication with any of the other additional components <b>120</b>-<b>134</b>. Furthermore, the processor <b>116</b> may be operative to independently control the first display <b>102</b> and the second display <b>104</b> and may be operative to receive input from the first touch sensor <b>106</b> and the second touch sensor <b>108</b>. The processor <b>116</b> may comprise one or more different processors. For example, the processor <b>116</b> may comprise one or more application specific integrated circuits (ASICs), one or more field-programmable gate arrays (FPGAs), one or more general purpose processors operative to execute machine readable code, or a combination of the foregoing.

The handheld computing device may include a battery <b>118</b> operative to provide power to the various devices and components of the handheld computing device <b>100</b>. In this regard, the handheld computing device <b>100</b> may be portable.

The handheld computing device <b>100</b> may further include a memory module <b>120</b> in operative communication with the data bus <b>114</b>. The memory module <b>120</b> may be operative to store data (e.g., application data). For instance, the memory <b>120</b> may store machine readable code executable by the processor <b>116</b> to execute various functionalities of the device <b>100</b>.

Additionally, a communications module <b>122</b> may be in operative communication with one or more components via the data bus <b>114</b>. The communications module <b>122</b> may be operative to communicate over a cellular network, a Wi-Fi connection, a hardwired connection or other appropriate means of wired or wireless communication. The handheld computing device <b>100</b> may also include an antenna <b>126</b>. The antenna <b>126</b> may be in operative communication with the communications module <b>122</b> to provide wireless capability to the communications module <b>122</b>. Accordingly, the handheld computing device <b>100</b> may have telephony capability (i.e., the handheld computing device <b>100</b> may be a smartphone device).

An audio module <b>124</b> may also be provided in operative communication with the data bus <b>114</b>. The audio module <b>124</b> may include a microphone and/or speakers. In this regard, the audio module <b>124</b> may be able to capture audio or produce sounds. Furthermore, the device <b>100</b> may include a camera module <b>128</b>. The camera module <b>128</b> may be in operative communication with other components of the handheld computing device <b>100</b> to facilitate the capture and storage of images or video.

Additionally, the handheld computing device <b>100</b> may include an I/O module <b>130</b>. The I/O module <b>130</b> may provide input and output features for the handheld computing device <b>100</b> such that the handheld computing device <b>100</b> may be connected via a connector or other device in order to provide syncing or other communications between the handheld computing device <b>100</b> and another device (e.g., a peripheral device, another computing device etc.).

The handheld computing device <b>100</b> may further include an accelerometer module <b>132</b>. The accelerometer module <b>132</b> may be able to monitor the orientation of the handheld computing device <b>100</b> with respect to gravity. In this regard, the accelerometer module <b>132</b> may be operable to determine whether the handheld computing device <b>100</b> is substantially in a portrait orientation or landscape orientation. The accelerometer module <b>132</b> may further provide other control functionality by monitoring the orientation and/or movement of the handheld computing device <b>100</b>.

The handheld computing device <b>100</b> may also include one or more hardware buttons <b>134</b>. The hardware buttons <b>134</b> may be used to control various features of the handheld computing device <b>100</b>. The hardware buttons <b>134</b> may have fixed functionality or may be contextual such that the specific function of the buttons changes during operation of the handheld computing device <b>100</b>. Examples of such hardware buttons may include, but are not limited to, a volume control, a home screen button, an end button, a send button, a menu button, etc.

With further reference to <figref idref="DRAWINGS">FIGS. 2A-D</figref>, various screens of an embodiment of a device are shown. multiple screens may be shown, only one or a subset of the multiple screens may be shown on the displays of the device at any one moment. In this regard, a screen may be described in a relative location to the displays or other screens (e.g., to the left of a display, to the right of a display, under another screen, above another screen, etc.). These relationships may be logically established such that no physical display reflects the relative position. For instance, a screen may be moved off a display to the left. While the screen is no longer displayed on the display, the screen may have a virtual or logical position to the left of the display from which it was moved. This logical position may be recognized by a user and embodied in values describing the screen (e.g., values stored in memory correspond to the screen). Thus, when referencing screens in relative locations to other screens, the relationships may be embodied in logic and not physically reflected in the display of the device.

<figref idref="DRAWINGS">FIGS. 2A-D</figref> may display a number of different screens that may be displayed at various instances of operation of a handheld device and are not intended to be presented in any particular order or arrangement. Single screen applications and multi screen applications may be provided. A single screen application is intended to describe an application that is capable of producing a screen that may occupy only a single display at a time. A multi screen application is intended to describe an application that is capable of producing one or more screens that may simultaneously occupy multiple displays. Additionally, a multi screen application may occupy a single display. In this regard, a multi screen application may have a single screen mode and a multi screen mode.

A desktop sequence <b>136</b> is displayed in <figref idref="DRAWINGS">FIG. 2A</figref>. The desktop sequence <b>136</b> may include a number of individual desktop screens <b>138</b><i>a</i>-<b>138</b><i>f</i>. Thus, each desktop screen <b>138</b> may occupy substantially the entirety of a single display (e.g., the first display <b>102</b> or second display <b>104</b> of <figref idref="DRAWINGS">FIG. 1</figref>). The desktop screens <b>138</b><i>a</i>-<b>138</b><i>f </i>may be in a predetermined order such that the desktop screens <b>138</b><i>a</i>-<b>138</b><i>f </i>appear consecutively and the order in which the desktop screens appear may not be reordered. However, the desktop screens <b>138</b><i>a</i>-<b>138</b><i>f </i>may be sequentially navigated (e.g., in response to a user input). That is, one or more of the desktop screens <b>138</b><i>a</i>-<b>138</b><i>f </i>may be sequentially displayed on a handheld device as controlled by a user input.

Additionally, <figref idref="DRAWINGS">FIG. 2B</figref> displays a hierarchal application sequence <b>140</b> of a multi screen application. The hierarchal application sequence <b>140</b> may include a root screen <b>142</b>, one or more node screens <b>144</b>, and a leaf screen <b>146</b>. The root screen <b>142</b> may be a top level view of the hierarchical application sequence <b>140</b> such that there is no parent screen corresponding to the root screen <b>142</b>. The root screen <b>142</b> may be a parent to a node screen <b>144</b>. One or more node screens <b>144</b> may be provided that are related as parent/children. A node screen may also serve as a parent to a leaf screen <b>146</b>. By leaf screen <b>146</b>, it is meant that the leaf screen <b>146</b> has no corresponding node screen <b>144</b> for which the leaf screen <b>146</b> is a parent. As such, the leaf screen does not have any children node screens <b>144</b>. <figref idref="DRAWINGS">FIG. 2C</figref> depicts various single screen applications <b>148</b><i>a</i>, <b>148</b><i>b</i>, and <b>148</b><i>c </i>arranged sequentially. Each of these single screen applications may correspond to a different executing application. For instance, in <figref idref="DRAWINGS">FIG. 2C</figref> Application <b>4</b>, Application <b>5</b>, and Application <b>6</b> may be executing on the device and correspond to each single screen <b>148</b><i>a</i>, <b>148</b><i>b</i>, and <b>148</b><i>c</i>, respectively.

<figref idref="DRAWINGS">FIG. 2D</figref> also includes an empty view <b>166</b>. The empty view <b>166</b> may be used during transitions of a screen (e.g., movement of screen between a first display and a second display). It is not necessary that the empty view <b>166</b> be interpretable by the user as an effective GUI screen. The empty view <b>166</b> merely communicates to the user that an action regarding the screen (e.g., the movement of the screen with respect to one or more displays) is occurring. An application displaying an empty view <b>166</b> need not be able to rest, wait, process or interpret input. The empty view <b>166</b> may display a screen, or a representation thereof, as it is being moved in proportion to the amount of the screen that has been moved from a first display to a second display as will be discussed in greater detail below. In this regard, the empty view <b>166</b> may be used to relate information regarding the position of a screen during a transition of the screen (e.g., in response to gesture). An empty view <b>166</b> is only intended to refer to a screen not capable of receiving an input (e.g., a screen in transition). In this regard, the display of an empty view <b>166</b> may include an animation or the like showing the response of a screen as it is being moved or changed (e.g., modified into or out of a landscape mode).

<figref idref="DRAWINGS">FIGS. 3A-K</figref> depict various arrangements and statuses of displays <b>102</b>, <b>104</b> of a device that are possible in various embodiments of a handheld computing device according to the present disclosure. For instance, when in the first (e.g., closed) position, a closed front display <b>168</b> may be visible as shown in <figref idref="DRAWINGS">FIG. 3A</figref>. The closed front display <b>168</b> may correspond with the first display <b>102</b> or the second display <b>104</b>. The closed front <b>168</b> as displayed may be occupied by a desktop screen D<b>1</b><b>138</b> as shown in <figref idref="DRAWINGS">FIG. 3A</figref>. Alternatively, an application with a single screen or a multi screen application in single screen mode may be displayed in the closed front <b>168</b>. A closed back display <b>170</b> may be viewable from an opposite side of the display when the device is in a closed position, as shown in <figref idref="DRAWINGS">FIG. 3B</figref>. The closed back <b>170</b> may display a different desktop screen or application screen than the closed front <b>168</b> (e.g., as shown in <figref idref="DRAWINGS">FIG. 3H</figref>) or may simply display an empty view <b>166</b> (e.g., displaying an icon or other graphic) and lack functionality as an interface.

<figref idref="DRAWINGS">FIG. 3C</figref> depicts a closed device in a landscape orientation <b>172</b><i>a</i>. In one embodiment, a landscape mode (i.e., wherein the display is adjusted to display a screen in a landscape orientation) may not be enabled as shown in <figref idref="DRAWINGS">FIG. 3C</figref>. Alternatively, the landscape mode may be enabled such that the screen (e.g., application screen <b>148</b>) is modified when the device is sensed in a landscape orientation <b>172</b><i>b</i>, such that the screen <b>148</b> is rendered in a landscape orientation as shown at <figref idref="DRAWINGS">FIG. 3D</figref>.

The device may further be provided in a second (e.g., open) position <b>174</b> as shown in <figref idref="DRAWINGS">FIG. 3E</figref>. In the open position <b>174</b>, at least two displays <b>102</b>, <b>104</b> are arranged such that the two displays <b>102</b>, <b>104</b> are both visible from the vantage point of a user. The two displays <b>102</b>, <b>104</b> may be arranged in a side-by-side fashion when in the open position <b>174</b>. Thus, each of the two displays <b>102</b>, <b>104</b> may display separate screens. For instance, the displays <b>102</b>, <b>104</b> may each display a separate desktop screen <b>138</b><i>a</i>, <b>138</b><i>b</i>, respectively. While the individual displays <b>102</b> and <b>104</b> are in a portrait orientation as shown in <figref idref="DRAWINGS">FIG. 3E</figref>, it may be appreciated that the full display area (comprising both the first display <b>102</b> and the second display <b>104</b>) may be arranged in a landscape orientation. Thus, whether the device as depicted in <figref idref="DRAWINGS">FIG. 3E</figref> is in a landscape or portrait orientation may depend on whether the displays are being used individually or collectively. If used collectively as a unitary display, the device may be in a landscape orientation, whereas if the displays are used separately, the orientation shown in <figref idref="DRAWINGS">FIG. 3E</figref> may be referred to as a portrait orientation.

Additionally, when the device is in an open position <b>174</b> as shown in <figref idref="DRAWINGS">FIG. 3F</figref>, a similar dependency with regard to the use of the screens as a unitary display or separate displays may also affect whether the device is in a portrait orientation or landscape orientation. As can be appreciated, each individual screen is in a landscape orientation, such that if the displays are used separately, the device may be in a landscape orientation. If used as a unitary display, the device may be in a portrait orientation. In any regard, as shown in <figref idref="DRAWINGS">FIG. 3F</figref>, a single screen <b>148</b> may occupy a first display <b>102</b> and the second display <b>104</b> may display a desktop screen <b>138</b>. The single screen <b>148</b> may be displayed in a landscape or portrait mode. Alternatively, a device in an open orientation may display a multi screen application <b>156</b> that may occupy both displays <b>102</b>, <b>104</b> in a portrait orientation as shown in <figref idref="DRAWINGS">FIG. 3G</figref> such that the individual displays are in a landscape orientation.

<figref idref="DRAWINGS">FIGS. 3I-K</figref> depict the potential arrangements of the screens of a multi screen application <b>152</b>. The multi screen application <b>152</b> may, in one mode, occupy a single display <b>102</b> when the device is in a closed position <b>168</b> as shown in <figref idref="DRAWINGS">FIG. 3I</figref>. That is, the multi screen application <b>152</b> may be in a single screen mode. Alternatively, when the device is in an open position as shown in <figref idref="DRAWINGS">FIG. 3J</figref>, the multi screen application <b>152</b> may still occupy a single display <b>102</b> in single screen mode. Furthermore, the multi screen application <b>152</b> may be expanded to occupy both displays <b>102</b>, <b>104</b> when the device is in the open position as shown in <figref idref="DRAWINGS">FIG. 3K</figref>. In this regard, the multi screen application <b>152</b> may also execute in a multi screen mode. Various options may be provided for expanding the multi screen application <b>152</b> from a single screen mode to a multi screen mode.

For example, the multi screen application <b>152</b> may be maximized from a single screen mode displayed in a single display to two screens displayed in two displays such that a parent screen is displayed in the first display and a node screen (e.g., a child screen) is expanded into the second display. In this regard, each of the screens displayed in the first and second display may be independent screens that comprise part of a hierarchical application sequence (e.g., as shown in <figref idref="DRAWINGS">FIG. 2B</figref>). Alternatively, the single screen mode of the multi screen application may simply be scaled such that the contents of the single screen are scaled to occupy both displays. Thus, the same content displayed in the single screen is scaled to occupy multiple displays, but no additional viewing area or graphics are presented. Further still, the maximization of the multi screen application from a single screen mode to a multi screen mode may result in the expansion of the viewable area of the application. For example, if a multi screen application is displayed in single screen mode, upon maximization into multi screen mode, the viewable area of the multi-screen application may be expanded while the scale of the graphics displayed remains the same. In this regard, the viewable area of the multi-screen application may be expanded into the second display while the scaling remains constant upon expansion.

In this regard, an application may have configurable functionality regarding the nature and behavior of the screens of the application. For instance, an application may be configurable to be a single screen application or a multi screen application. Furthermore, a multi screen application may be configurable as to the nature of the expansion of the multi screen application between a single screen mode and a multi screen mode. These configuration values may be default values that may be changed or may be permanent values for various applications. These configuration values may be communicated to the device (e.g., the processor <b>116</b>) to dictate the behavior of the application when executing on the device.

<figref idref="DRAWINGS">FIG. 4</figref> depicts various graphical representations of gesture inputs that may be recognized by a handheld computing device. The gestures shown are demonstrative, and as such, other gestures may be provided without limitation. Such gestures may be received at one or more gesture sensors of the device or other gesture sensor as described above. In this regard, various input mechanisms may be used in order to generate the gestures shown in <figref idref="DRAWINGS">FIG. 4</figref>. For example a stylus, a user's finger(s), or other devices may be used to activate a gesture sensor in order to receive the gestures. Alternatively, the gestures may be detected by an optical device (e.g., a camera). The use of a gesture may describe the use of a truncated input that results in functionality without the full range of motion necessary to conventionally carry out the same functionality. For instance, movement of screens between displays may be carried out by selecting and moving the screen between displays such that the full extent of the motion between displays is received as an input. However, such an implementation may be difficult to accomplish in that the first and second displays may comprise separate display portions without continuity therebetween. As such, a gesture may truncate the full motion of movement or provide an alternative input to accomplish the same functionality. Thus, movement spanning the first and second display may be truncated so that the gesture may be received at a single gesture sensor. The use of gesture inputs is particularly suited to handheld computing devices in that the full action of an input may be difficult to execute given the limited input and display space commonly provided on a handheld computing device.

With reference to <figref idref="DRAWINGS">FIG. 4</figref>, a circle <b>190</b> may represent an input received at a gesture sensor. The circle <b>190</b> may include a border <b>192</b>, the thickness of which may indicate the length of time the input is held stationary. In this regard, a tap <b>186</b> has a thinner border <b>192</b> than the border <b>192</b>′ for a long press <b>188</b>. In this regard, the long press <b>188</b> may involve an input that remains stationary for longer than that of a tap <b>186</b>. As such, different gestures may be registered depending upon the length of time that the gesture remains stationary prior to movement.

A drag <b>176</b> involves an input (represented by circle <b>190</b>) with movement <b>194</b> in a direction. The drag <b>176</b> may involve an initiating gesture (e.g., a tap <b>186</b> or long press <b>188</b>) that remains stationary with respect to the gesture sensor for a certain amount of time represented by the border <b>192</b>. In contrast, a flick <b>178</b> may involve an input with a shorter dwell time prior to movement than the drag <b>176</b> as indicated by the thinner border <b>192</b>″ of the initiation of the flick <b>178</b>. The flick <b>178</b> may also include movement <b>194</b>. The direction of movement <b>194</b> of the drag and flick <b>178</b> may be referred to as the direction of the drag <b>176</b> or direction of the flick <b>178</b>.

In an embodiment, a gesture having movement (e.g., a flick <b>178</b> or drag gesture <b>176</b> as described above) may be limited to movement in a single direction along a single axis (e.g., a horizontal, vertical, or other axis). Thus, movement in a direction different than along the first axis may be disregarded during the execution of the gesture. In this regard, once a gesture is initiated, movement in a direction not along an axis along which initial movement is registered may be disregarded or only the vector component of movement along the axis may be registered.

While the gestures shown in <figref idref="DRAWINGS">FIG. 4</figref> include only horizontal motion after the initial input, this may not be actual movement by the user when entering the gesture. For instance, once a drag <b>176</b> is initiated in the horizontal direction, movement in a direction other than in the horizontal direction may not result in movement of the screen to be moved in the direction different than the horizontal direction. For instance, with further reference to <figref idref="DRAWINGS">FIG. 11</figref>, the drag <b>176</b> from left to right may be initiated with initial movement <b>204</b> from left to right along an initiated direction <b>210</b>. Subsequently, the user may input an off direction movement <b>206</b> in a direction different than the initiated direction <b>210</b>. In this regard, the off direction movement <b>206</b> may not result in any movement of a screen between two displays. Furthermore, the user may input partially off direction movement <b>208</b>, where only a vector portion of the movement is in the direction of the initiated direction <b>210</b>. In this regard, only the portion of the partially off direction movement <b>208</b> may result in movement of a screen between displays. In short, the movement of application screens between the first display <b>102</b> and the second display <b>104</b> may be constrained along a single axis along which the displays are arranged.

As briefly discussed above, multiple simultaneous gesture portions may be received at the same time (e.g., by a multi-touch device, or other gesture sensor). A gesture input that combines multiple individual gesture portions may be considered a unique gesture input and have unique functionality associated therewith. For example, a first pin and drag gesture <b>182</b> may comprise a first portion including a tap <b>186</b> as well as a second portion including a drag gesture <b>176</b>. The drag gesture <b>176</b> may be generally away from the tap <b>186</b> such that the direction of the drag gesture <b>176</b> is away from the tap gesture <b>186</b>. Alternatively, a second pin and drag gesture <b>184</b> is also shown where the tap <b>186</b> may be received and a drag gesture <b>176</b> may originate away from the tap <b>186</b> and be in a direction towards the tap <b>186</b>. The first and second portions of a multi portion gesture may have different targets such that the two portions affect different results with respect to an interface as will be discussed in greater detail below.

Screens may be logically associated with a display and be logically arranged with respect to one another even though not all screens are physically rendered on a display. With additional reference to <figref idref="DRAWINGS">FIG. 5</figref>, this concept is further graphically represented. In <figref idref="DRAWINGS">FIG. 5</figref>, a first display <b>102</b> actively displays a first application screen (screen A <b>512</b>). Additionally, a first application stack <b>510</b> is depicted. An application stack may be operative to maintain logical associations of a screen with a respective display. As referenced below, this logical association may be referred to as the position of the application with respect to a display. In this regard, when referring to an application “positioned in a display,” it is meant the application is logically associated with the display as the application may not be actively displayed.

In addition, an application stack may logically maintain the relative positions of screens with respect to one another (i.e., the order of the screens in the application stack). In this regard, a screen may be logically disposed in an application stack associated with a display even though the screen may not be physically rendered on the display. A display controller or other control device (e.g., a processor, memory, or an operative combination thereof) may be operative to maintain the logical associations of screens. This may involve storing the logical association of the screen with a display and/or other screens in memory. As such, the logical associations of the screen with a display and with other screens may be logically maintained and/or changed even though the screen is not actively displayed.

For example, the first application stack <b>510</b> is comprised of screen A <b>512</b>, screen B <b>514</b>, and screen C <b>516</b> which are all logically associated with the first display <b>102</b>. As shown, only screen A <b>512</b> from the application stack <b>510</b> is physically displayed. Screen B <b>514</b> and screen C <b>516</b> may belong to the first application stack <b>510</b> associated with the first display <b>102</b> and be logically positioned behind screen A <b>510</b> in the manner shown in <figref idref="DRAWINGS">FIG. 5</figref>. As such, screen B <b>514</b> and screen C <b>516</b> may be logically positioned behind screen A <b>512</b> such that screen B <b>514</b> and screen C <b>516</b> are not actively rendered on the first display <b>102</b>. While each application belonging to the first application stack <b>510</b> is logically associated with the first display, applications that are not currently rendered in the display may suspend or close when not actively displayed. Alternatively, applications may continue to execute in the background, even though not displayed. Regardless, the non-displayed applications may continue to reside in the application stack <b>510</b> until otherwise closed or ended by a user.

A second application stack <b>520</b> may also be provided to maintain the logical associations of screens with respect to a second display <b>104</b>. The second application stack <b>520</b> is comprised of screen X <b>522</b>, screen Y <b>524</b>, and screen Z <b>526</b> and may behave in a manner similar to the first application stack <b>510</b> described above. Each of screen A <b>512</b>, screen B <b>514</b>, screen C <b>516</b>, screen X <b>522</b>, screen Y <b>524</b>, and screen Z <b>526</b> may correspond to individual applications. As shown, screen X <b>522</b> is currently displayed. While screen Y <b>524</b> and screen Z <b>526</b> are logically associated with the second display <b>104</b> and are logically positioned behind screen X <b>522</b> as shown in <figref idref="DRAWINGS">FIG. 5</figref>. Thus, while each application in the second application stack <b>520</b> is disposed in the second display <b>104</b>, only one application may be actively rendered on the display.

The arrangement (i.e., logical associations) of the screens with respect to the displays and within the application stacks <b>510</b>, <b>520</b> may be arrived at by various methods including manipulation of screens via drag gestures, opening a new application on top of an existing screen rendered on a display, or other means of manipulation whereby screens are moved between the first display <b>102</b> and the second display <b>104</b>.

In light of the foregoing, wherein applications may reside in application stacks associated with a display such that non-displayed applications remain in the application stack, it may be desirable or advantageous to allow for the manipulation of applications between displays such that applications may be moved from a first application stack to a second application stack by a user. The movement of applications between application stacks may, for instance, be accomplished by way of gesture inputs.

One embodiment of a handheld computing device functioning to move applications from one application stack to another application stack in response to a gesture input as shown in <figref idref="DRAWINGS">FIGS. 6A-6C</figref>. In <figref idref="DRAWINGS">FIG. 6A</figref>, application X <b>602</b> may be the actively displayed screen in a first display <b>102</b> and application A<b>1</b><b>604</b> may be the actively displayed screen in a second display <b>104</b>. Application B<b>1</b><b>606</b> may be in a first application stack <b>610</b> associated with the first display <b>102</b> and positioned behind application X <b>602</b> when in the state shown in <figref idref="DRAWINGS">FIG. 6A</figref>. As such, application B<b>1</b> may not be actively rendered on the first display <b>102</b> when positioned as shown in <figref idref="DRAWINGS">FIG. 6A</figref>. In <figref idref="DRAWINGS">FIG. 6A</figref>, a drag gesture <b>176</b> is received that corresponds to the first display <b>102</b> in a direction towards the second display <b>104</b>. In response to the drag gesture <b>176</b>, application X <b>602</b> may be moved from the first application stack <b>610</b> to a second application stack <b>620</b> associated with the second display <b>104</b> as shown in <figref idref="DRAWINGS">FIG. 6B</figref>. In this regard, application B<b>1</b><b>606</b> which was previously disposed behind application X <b>602</b> in the first application stack <b>610</b> may become the actively displayed screen in the first display <b>102</b>. Application X <b>602</b> may be moved to the second display <b>104</b> to become the actively displayed screen in the second display <b>104</b>, and thus the top application in the second application stack <b>620</b>. Application A<b>1</b><b>604</b> which was previously the actively displayed screen in the second display <b>104</b> may be positioned behind application X <b>602</b> in the second application stack <b>620</b>. As such, application X <b>602</b> is moved from the first display <b>102</b> to the second display <b>104</b> such that application X <b>602</b> goes from being logically associated with the first application stack <b>610</b> to the second application stack <b>620</b>. As shown, application X <b>602</b> is given priority in the second application stack <b>620</b> such that application X <b>602</b> becomes the actively displayed screen once moved to the second display <b>104</b>.

However, the movement of an application from a first display <b>102</b> to a second display <b>104</b> may not entail the movement of the application exclusively from a first application stack <b>610</b> to a second application stack. For instance, in <figref idref="DRAWINGS">FIG. 6B</figref> a subsequent drag gesture <b>176</b> may be received. The drag gesture <b>176</b> may be received such that it originates at the first display <b>102</b> and is directed towards the second display <b>104</b>. Application B<b>1</b><b>606</b> may comprise an expandable application capable of being displayed on multiple displays. As such, the drag gesture <b>176</b> may result in application B<b>1</b><b>606</b> being expanded to occupy both the first display <b>102</b> and the second display <b>104</b>. In this sense, application B<b>1</b><b>606</b>, once expanded, belongs to both the first application stack <b>610</b> as well as the second application stack <b>620</b> and becomes the actively displayed screen on both the first display <b>102</b> and the second display <b>104</b>. As shown, application X <b>602</b> which was previously the actively displayed screen in the second display <b>104</b> is positioned in the second application stack <b>620</b> behind screen <b>606</b><i>b. </i>

An alternative outcome of a receipt of a gesture input when a device is in a state shown in <figref idref="DRAWINGS">FIG. 6B</figref> is depicted in <figref idref="DRAWINGS">FIGS. 7A-7B</figref>. <figref idref="DRAWINGS">FIG. 7A</figref> shows the handheld computing device as was shown in <figref idref="DRAWINGS">FIG. 6B</figref>. However, unlike in <figref idref="DRAWINGS">FIG. 6B</figref>, in <figref idref="DRAWINGS">FIG. 7A</figref> a flick gesture <b>178</b> (in contrast to the drag gesture <b>176</b> received in <figref idref="DRAWINGS">FIG. 6B</figref>) is received at the first display <b>102</b> in a direction toward the second display <b>104</b>. A flick gesture <b>178</b> may result in a different outcome than that associated with a drag gesture <b>176</b> such that the expandable application B<b>1</b><b>606</b> is simply moved from the first display <b>102</b> to the second display <b>104</b> while maintaining the application B<b>1</b><b>606</b> in single screen mode. As such, the result of the flick gesture <b>178</b> in <figref idref="DRAWINGS">FIG. 7A</figref> may be shown in <figref idref="DRAWINGS">FIG. 7B</figref> wherein application B<b>1</b><b>606</b> has been moved from the first display <b>102</b> to the second display <b>104</b> such that the application B<b>1</b><b>606</b> remains in single screen mode and becomes a part of the second application stack <b>620</b> exclusive of the first application stack <b>610</b>. In turn, the previous actively displayed screen corresponding with application X <b>602</b> is moved to the second application stack <b>620</b> behind application B<b>1</b><b>606</b>. Application A<b>1</b><b>604</b> is positioned behind application X <b>602</b> in the second application stack <b>620</b>. Additionally, as application B<b>1</b><b>606</b> was the last application in the first application stack <b>610</b>, upon movement of application B<b>1</b><b>606</b> into the second display <b>104</b>, a desktop screen D<b>1</b><b>138</b> may be displayed in the first display <b>102</b>.

As discussed above, a gesture input may comprise multiple portions (e.g., in the case of a multi-touch sensor or other gesture sensor capable of receiving multiple gesture inputs simultaneously). In this regard, a first portion of a gesture input may be used to indicate that a corresponding screen of a display is to be maintained such that it is not moved in response to the receipt of a second portion of the gesture. For instance, a first portion of the gesture input may be received such that a corresponding actively displayed screen is maintained (e.g., pinned) as the actively displayed screen. In this regard, upon receipt of the second portion of the input gesture, an application other than the actively displayed screen may be the target of the second gesture such that the second portion of the gesture effectuates a movement of the application between application stacks behind the screen maintained as the actively displayed screen.

<figref idref="DRAWINGS">FIGS. 8A-8E</figref> depict another embodiment of a handheld computing device wherein applications are repositioned between application stacks based on a receipt of a multi portion gesture input. <figref idref="DRAWINGS">FIGS. 8A-8E</figref> generally show potential functionality related to movement of applications between application stacks. As such, alternative arrangements of the handheld computing device may be provided. For example, more or less applications may be provided that are manipulatable between the application stacks. Furthermore, the applications may be arranged with respect to the first and second displays. Also, the functionality described below may include directional movement (e.g., between the first display <b>102</b> and the second display <b>104</b>). While the direction of the movement of an application may correspond with the direction of a received gesture input as described below, the movement may be in either direction between displays (e.g., from the first display to the second display or vice versa) without limitation.

In <figref idref="DRAWINGS">FIG. 8A</figref>, application B<b>1</b><b>606</b> is an actively displayed screen of the first display <b>102</b>. Additionally, application A<b>1</b><b>604</b> and application X <b>602</b> may also be in a first application stack <b>610</b> associated with the first display <b>102</b>. Display <b>104</b> may not have any applications disposed therein such that a desktop screen D<b>2</b><b>138</b><i>b </i>is displayed in the second display <b>104</b> and no applications are part of a second application stack <b>620</b> associated with the second display <b>104</b>. A pin and drag gesture <b>182</b> may be received such that a first portion <b>190</b> (i.e., a pin) of the pin and drag gesture is associated with the first display <b>102</b> and the second portion <b>192</b> (i.e., a drag) of the pin and drag gesture <b>182</b> comprises a directional gesture initiating at the first display <b>102</b> in a direction of the second display <b>104</b>. The first portion <b>190</b> of the pin and drag gesture <b>182</b> may control the first display <b>102</b> such that the actively displayed screen in the first display <b>102</b> is maintained even when the drag portion <b>192</b> of the pin and drag gesture <b>182</b> is received. In this regard, the result is shown in <figref idref="DRAWINGS">FIG. 8B</figref> wherein application B<b>1</b><b>606</b> is maintained as the actively displayed application in the first display <b>102</b> and application A<b>1</b><b>604</b>, which was the next application in the first application stack <b>610</b> is moved to the second application stack <b>620</b> from behind application B<b>1</b><b>606</b>. In this regard, application A<b>1</b><b>604</b> was moved from behind application B<b>1</b><b>606</b> as application B<b>1</b><b>606</b> was pinned in the first display <b>102</b> by way of receipt of the pin portion <b>190</b> of the pin and drag gesture <b>182</b>.

Additionally, when in the state shown in <figref idref="DRAWINGS">FIG. 8B</figref>, another pin and drag gesture <b>182</b> may be received. Again, the pin and drag gesture <b>182</b> may comprise a pin portion <b>190</b> associated with the first display <b>102</b> to maintain an actively displayed screen of the first display <b>102</b> even after receipt of the drag portion <b>192</b>. In this regard, application B<b>1</b><b>606</b> is again maintained as the actively displayed screen in the first display <b>102</b> and the application behind the actively displayed screen of the first display is the target of the drag portion <b>192</b> of the pin and drag gesture <b>182</b>. The result is shown in <figref idref="DRAWINGS">FIG. 8C</figref>, wherein application X <b>602</b>, which was previously behind application B<b>1</b><b>606</b> in the first application stack, is the target of the drag portion <b>192</b> of the pin and drag gesture <b>182</b> received in <figref idref="DRAWINGS">FIG. 8B</figref>, and is moved to the second application stack <b>620</b>. In <figref idref="DRAWINGS">FIG. 8C</figref>, another pin and drag gesture <b>182</b> may be received such that a pin portion <b>190</b> again pins the actively displayed screen of the first display <b>102</b>. However, in <figref idref="DRAWINGS">FIG. 8C</figref>, there is no application residing behind the actively displayed screen. As such, upon receipt of the drag portion <b>192</b> of the pin and drag gesture <b>182</b>, there is no application residing behind the actively displayed, pinned screen to be the target of the drag portion <b>192</b>. In this case, the pin portion <b>190</b> of the pin and drag gesture <b>182</b> may override the drag portion <b>192</b> such that no movement takes place.

In addition to a gesture input comprising a pin portion and a drag portion wherein the drag portion moves an application from underneath the pinned application, a second pin and drag gesture <b>184</b> may be received such that the drag portion <b>192</b> is in a direction towards the pin portion <b>190</b>. This may result in an application being moved to a position behind the pinned portion rather than from a position behind the pinned application as was shown in <figref idref="DRAWINGS">FIGS. 8A-8C</figref>.

This concept is demonstrated in <figref idref="DRAWINGS">FIG. 8D</figref>. In <figref idref="DRAWINGS">FIG. 8D</figref>, a second pin and drag gesture <b>184</b> is received. A pin portion <b>190</b> is received corresponding to a first display <b>102</b>. As such, the actively displayed screen of the first display <b>102</b> is maintained as the actively displayed screen. The drag portion <b>192</b> initiates at the second display <b>104</b> in a direction towards the first display <b>102</b>. In this regard, the actively displayed screen of the second display <b>104</b> is the target of the drag portion <b>192</b>. As such, the actively displayed screen of the second display <b>104</b> is moved behind the pinned application in the first display <b>102</b>. The result is shown in <figref idref="DRAWINGS">FIG. 8E</figref> wherein application X <b>602</b> which was the actively displayed screen in the second display <b>104</b> is moved behind the pinned screen of application B<b>1</b><b>606</b>. In this regard, application X <b>602</b> becomes a part of the first application stack <b>610</b>. Also, application A<b>1</b><b>604</b> which was residing behind the actively displayed screen of the second display <b>104</b> in <figref idref="DRAWINGS">FIG. 8D</figref> is revealed and becomes the actively displayed screen in the second display <b>104</b> as shown in <figref idref="DRAWINGS">FIG. 8E</figref>.

While the invention has been illustrated and described in detail in the drawings and foregoing description, such illustration and description is to be considered as exemplary and not restrictive in character. For example, certain embodiments described hereinabove may be combinable with other described embodiments and/or arranged in other ways (e.g., process elements may be performed in other sequences). Accordingly, it should be understood that only the preferred embodiment and variants thereof have been shown and described and that all changes and modifications that come within the spirit of the invention are desired to be protected.