JP6073793B2 - Desktop display simultaneously with device release - Google Patents

Description

  The present disclosure relates to desktop display simultaneously with device release.

  A significant number of portable computing devices such as mobile phones, tablets and E-Readers utilize touch screen displays to not only deliver display information to the user, but also from user interface commands. It also receives input. While touch screen displays can increase the configurability of portable devices and provide a wide variety of user interface options, this flexibility is usually expensive. The dual use of touch screens to provide content and receive user commands is flexible for the user, but the display is obfuscated and visual clutter occurs, which causes user frustration and lost productivity. There is a fear.

  The small form factor of portable computing devices requires a careful balance between the displayed graphics and the area provided for input reception. On the other hand, a small display constrains the display space, which can increase the difficulty of operation or interpretation of results. On the other hand, a virtual keypad or other user interface scheme must be superimposed on or placed adjacent to the running application so that the application is packed into a smaller portion of the display.

  This balancing act is particularly difficult with single display touch screen devices. Single display touch screen devices suffer from their limited screen space. When a user enters information into the device through a single display, the ability to interpret the information in the display can be severely hindered, especially when complex interactions between the display and the interface are required. .

  There is a need for a dual multi-display portable computing device that provides increased power and / or increased versatility compared to conventional single-display portable computing devices. These and other needs are addressed by various aspects, embodiments and / or configurations of the present disclosure. Also, while this disclosure presents exemplary embodiments, it should be understood that individual aspects of the disclosure can be claimed separately.

  In one embodiment, the computer-readable medium includes instructions for causing a processor to manage a window stack for a multi-screen device. The computer-executable instruction is an instruction to receive a direction change in a multi-screen device, and the direction change causes the device to transition from a closed state to an open state, in which the first display is active and open. In the state, both the first display and the second display are active, an instruction to determine whether the desktop should be displayed on the second display, and the desktop should be displayed on the second display And determining to display the desktop on the second display and display the first window on the first display.

  In another embodiment, the device includes at least two displays, a memory, and a processor in communication with each of the memory and the at least two displays. The device is operable to provide a composite display, the composite display including one touch-sensitive display in a closed state, receiving a direction change in the multi-screen device, and the direction change causing the multi-screen device to be closed Transitioning from an open state to an open state, wherein the composite display comprises a first portion associated with the first touch-sensitive display and a second portion associated with the second touch-sensitive display. Deciding to enlarge the desktop to cover the composite display, to display the first window on the first part of the composite display, and to display the desktop on the second part of the composite display; A desktop is displayed on the display, and a first window is displayed on the first touch-sensitive display. It is operable to display.

  In yet another embodiment, a method for presenting a display for a multi-screen device provides a composite display that spans at least a portion of the first touch-sensitive display when the multi-screen device is in a closed state. When the device is in the closed state, displaying the first window at the top of the window stack, receiving the direction change in the multi-screen device, the direction change from the closed state to the open state A transition to a receiving, changing the composite display to span at least a portion of the first touch-sensitive display and the second touch-sensitive display of the multi-screen device, The first part is associated with the first touch-sensitive display and the composite display The second part is to change the composite display associated with the second touch-sensitive display, determine that the desktop is associated with the composite display, modify the desktop to expand to the entire composite display Determining that, in the first part of the composite display, the first window is at the top of the window stack, and in the second part of the composite display, that the desktop is at the top of the window stack. Determining, displaying a first window on a first touch-sensitive display, and displaying the desktop on a second touch-sensitive display.

  The descriptions “at least one”, “one or more”, and “and / or” are open-ended expressions that are in use and connected and disjunctive. For example, “at least one of A, B and C”, “at least one of A, B or C”, “one or more of A, B and C”, “of A, B or C” Each of the expressions “one or more” and “A, B and / or C” is A only, B only, C only, A and B, A and C, B and C, or A and B. And C mean both.

  References to “one”, “one or more” and “at least one” can be used interchangeably herein. Note that the terms “comprising”, “including” and “having” can also be used interchangeably.

  The term “automatic” and variations thereof, as used herein, refer to any process or operation that takes place without substantial human input when performing the process or operation. However, if input is received prior to execution of the process or operation, the process or operation may be automatic, even if substantial or non-substantial human input is used in performing the process or operation. A human input is considered substantial if such input affects how the process or operation is performed. A human input that accepts execution of a process or operation is not considered “substantial”.

  The term “computer-readable medium” as used herein refers to any tangible storage and / or transmission medium that participates in providing instructions to a processor for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, NVRAM or magnetic or optical disks. Volatile media includes dynamic memory, such as main memory. Common forms of computer readable media include, for example, floppy disks, flexible disks, hard disks, magnetic tapes or any other magnetic media, magneto-optical recording media, CD-ROM, any other optical media, Punch cards, paper tape, any other hole pattern physical media, RAM, PROM and EPROM, FLASH-EPROM, solid state media such as memory cards, any other memory chip or cartridge, carrier wave described below Or any other medium that can be read by a computer. A digital file or other self-contained information archive or archive set attached to an email is considered a distribution medium equivalent to a tangible storage medium. It should be understood that if the computer readable medium is configured as a database, the database can be any type of database, such as relational, hierarchical, object oriented and / or the like. Accordingly, this disclosure is considered to include tangible storage or distribution media on which the software implementations of the present disclosure are stored and equivalents and successor media approved in the prior art.

  The term “desktop” refers to a metaphor used to represent a system. A desktop is generally thought of as a “face” that contains a picture called an icon, widget, folder, etc., and usually launches or displays applications, windows, cabinets, files, folders, documents, and other graphical items on it be able to. The icons are generally selectable to initiate a task through user interface interactions, and the user can run the application or perform other operations.

  The terms “screen”, “touchscreen” or “touchscreen” refer to a physical structure that includes one or more hardware components that provide a device with the ability to render a user interface and / or receive user input. Point to. The screen may include any combination of gesture capture area, touch-sensitive display and / or configurable area. A device may have one or more physical screens embedded in the hardware. However, the screen may also include external peripheral devices that are removable from the device. In embodiments, multiple external devices can be attached to the device. Thus, in embodiments, the screen allows the user to interact with the device by touching an area on the screen and provides information to the user through the display. Touch screens can sense a user's touch in many different ways, such as changes in electrical parameters (eg, resistance or capacitance), sound wave fluctuations, infrared proximity detection, variable light detection and the like. In a resistive touch screen, for example, separate conductive and resistive metal layers within the screen typically pass current. When the user touches the screen, the two layers come into contact with each other at the touched position, thereby changing the electric field and calculating the coordinates of the touched position. In a capacitive touch screen, the capacitive layer accumulates charge, and the charge is discharged as soon as the user touches the touch screen, thereby reducing the charge on the capacitive layer. The reduction is measured and the coordinates of the touched position are determined. In a surface acoustic wave touch screen, sound waves are propagated through the screen and are blocked by user contact. The receiving transducer detects the user contact instance and determines the coordinates of the touched location.

  The term “display” refers to a portion of one or more screens used to display the output of a computer to a user. The display may be a multi-screen display called a single screen display or a composite display. The composite display may include one or more screen touch-sensitive displays. A single physical screen may include multiple displays that are managed as separate logical displays. Thus, different content can be displayed on different displays that are part of the same physical screen.

  The term “display image” refers to an image generated on a display. A typical display image is a window or desktop. The display image can occupy all or part of the display.

  The term “display orientation” refers to the way a user orients a rectangular display for viewing. The two most common types of display directions are portrait and landscape. In landscape mode, the display is oriented so that the width of the display is greater than the height of the display (a ratio of 4: 3 for width 4 units and height 3 units or 16 units for width 16 units and height 9 units: 16: 9). In other words, in landscape mode, the longer dimension of the display is oriented in a substantially horizontal direction and the shorter dimension of the display is oriented in a substantially vertical direction. In contrast, in portrait mode, the display width is oriented to be less than the display height. In other words, in portrait mode, the shorter dimension of the display is oriented in a substantially horizontal direction and the longer dimension of the display is oriented in a substantially vertical direction.

  The term “composite display” refers to a logical structure that defines a display that can include one or more screens. A multi-screen display can be associated with a composite display that encompasses all screens. A composite display may have different display characteristics based on different orientations of the device.

  The term “gesture” refers to a user action that represents an intended idea, action, meaning, result and / or outcome. User actions may include operation of the device (eg, opening and closing the device, changing the orientation of the device, moving a trackball or wheel, etc.), movement of a body part relative to the device, movement of a tool or tool relative to the device, voice input, etc. . Gestures can be made on the device (such as on the screen) or with the device and interact with the device.

  The term “module” as used herein may perform any known or later developed hardware, software, firmware, artificial intelligence, fuzzy theory, or function associated with that element. A combination of hardware and software that can be used.

  The term “gesture capture” refers to sensing or otherwise detecting an instance and / or type of user gesture. Gesture capture can occur in one or more areas of the screen. The gesture area can be on the display, sometimes referred to as a touch-sensitive display, or outside the display, sometimes referred to as a gesture capture area.

  A “multi-screen application” refers to an application capable of a plurality of modes. Multiple screen application modes may include, but are not limited to, a single screen mode (applications are displayed on a single screen) or a composite display mode (applications are displayed on more than one screen). Multiple screen applications may have different layouts optimized for the mode. Thus, a multi-screen application may have a different layout for a single screen or for a composite display that may include two or more screens. Different layouts may have different screen / display dimensions and / or configurations that can render the user interface of a multi-screen application. Different layouts allow the application to optimize the user interface of the application for the type of display, eg, single screen or multiple screens. In single screen mode, a multi-screen application can present one window frame of information. In the composite display mode, the multi-screen application has more space for display content, so it can present multiple window frames of information or provide a larger and richer presentation. Multi-screen applications can be designed to dynamically adapt to device and mode changes depending on which display (single or composite) the system assigns to the multi-screen application. In an alternative embodiment, the user can use a gesture to request a transition of the application to a different mode, and if a display is available for the requested mode, the device You can move to display and transition modes.

  “Single screen application” refers to an application capable of a single screen mode. Thus, a single screen application can only create one window, and different modes and different display dimensions may not be possible. Single screen applications are not capable of running in some of the modes discussed in multiple screen applications.

  The term “window” refers to a typically rectangular image displayed on at least a portion of the display and includes or provides content that is different from the rest of the screen. Windows may obscure the desktop.

  The terms “determine, judge”, “calculate” and “operate” and variations thereof, as used herein, are used interchangeably and may be any type of methodology, process, mathematical operation or technique. including.

  It should be understood that the term “means” as used herein is to be given its broadest possible interpretation in accordance with 35 USC 112, sixth paragraph. Accordingly, the claims incorporating the term “means” are intended to cover all structures, materials or acts described herein, and all equivalents thereof. Furthermore, structures, materials or acts and equivalents thereof are intended to include all that is described in the summary of the invention, a brief description of the drawings, a mode for carrying out the invention, an abstract and the claims themselves.

  The foregoing description is a simplified summary of the disclosure and provides an understanding of some aspects of the disclosure. This summary is not an extensive or comprehensive overview of the disclosure and its various aspects, embodiments and / or configurations. This summary is not intended to identify key or critical elements of the disclosure or to delineate the scope of the disclosure, but as an introduction to the more detailed description presented below. It is intended to present selected concepts in a simplified form. As will be appreciated, other aspects, embodiments and / or configurations of the present disclosure, alone or in combination, utilize one or more of the features described above or described in detail below. be able to.

1 includes a first diagram of an embodiment of a multi-screen user device. 2 includes a second diagram of an embodiment of a multi-screen user device. FIG. 4 includes a third diagram of an embodiment of a multi-screen user device. FIG. 4 includes a fourth illustration of an embodiment of a multi-screen user device. FIG. 10 includes a fifth view of an embodiment of a multi-screen user device. FIG. 6 includes a sixth view of an embodiment of a multi-screen user device. FIG. 10 includes a seventh view of an embodiment of a multi-screen user device. FIG. 10 includes an eighth view of an embodiment of a multi-screen user device. FIG. 10 includes a ninth view of an embodiment of a multi-screen user device. FIG. 10 includes a tenth view of an embodiment of a multi-screen user device. FIG. 6 is a block diagram of an embodiment of a device hardware. FIG. 6 is a block diagram of an embodiment of a device state model based on device orientation and / or configuration. FIG. 6 is a table of embodiments of device state models based on device orientation and / or configuration. FIG. FIG. 3 is a first representation of an embodiment of a user gesture received at a device. FIG. 4 is a second representation of an embodiment of a user gesture received at a device. FIG. 6 is a third representation of an embodiment of a user gesture received at a device. 6 is a fourth representation of an embodiment of a user gesture received at a device. FIG. 10 is a fifth representation of an embodiment of a user gesture received at a device. 7 is a sixth representation of an embodiment of a user gesture received at a device. 8 is a seventh representation of an embodiment of a user gesture received at a device. 9 is an eighth representation of an embodiment of a user gesture received at a device. FIG. 6 is a block diagram of an embodiment of device software and / or firmware. FIG. 3 is a second block diagram of an embodiment of device software and / or firmware. FIG. 6 is a first representation of an embodiment of a device configuration generated in response to a device state. FIG. 4 is a second representation of an embodiment of a device configuration generated in response to a device state. FIG. 6 is a third representation of an embodiment of a device configuration generated in response to a device state. FIG. 10 is a fourth representation of an embodiment of a device configuration generated in response to a device state. FIG. 10 is a fifth representation of an embodiment of a device configuration generated in response to a device state. FIG. 10 is a sixth representation of an embodiment of a device configuration generated in response to a device state. FIG. 10 is a seventh representation of an embodiment of a device configuration generated in response to a device state. FIG. 10 is an eighth representation of an embodiment of a device configuration generated in response to a device state. 10 is a ninth representation of an embodiment of a device configuration generated in response to a device state. 14 is a tenth representation of an embodiment of a device configuration generated in response to a device state. A representation of a logical window stack. Another logical window stack. Figure 4 is another representation of an embodiment of a logical window stack. Figure 4 is another representation of an embodiment of a logical window stack. Figure 4 is another representation of an embodiment of a logical window stack. Figure 4 is another representation of an embodiment of a logical window stack. Figure 4 is another representation of an embodiment of a logical window stack. Figure 4 is another representation of an embodiment of a logical window stack. Figure 4 is another representation of an embodiment of a logical window stack. Figure 4 is another representation of an embodiment of a logical window stack. FIG. 4 is a block diagram of an embodiment of a logical data structure for a window stack. 6 is a flowchart of an embodiment of a method for creating a window stack.

  In the appended drawings, similar components and / or features may have the same reference label. Furthermore, various components of the same type can be distinguished by following the reference label with characters that distinguish among similar components. Where only the first reference label is used herein, the description is applicable to any one of the similar components having the same first reference label regardless of the second reference label.

Presented herein are device embodiments. The device may be a communication device such as a mobile phone or other smart device. The device may include two screens that are oriented to provide several unique display configurations. Furthermore, the device can receive user input in a unique way. The overall design and functionality of the device can enhance the user experience that makes the device more useful and effective.
Mechanical features:
1A-1J illustrate a device 100 according to an embodiment of the present disclosure. As described in further detail below, the device 100 can be arranged in many different ways, each of which provides different functionality to the user. Device 100 is a multi-screen device that both includes a touch-sensitive primary screen 104 and a secondary screen 108. In an embodiment, the entire front surface of screens 104 and 108 may be touch-sensitive, and a user can receive input by touching the front surfaces of screens 104 and 108. The primary screen 104 includes a touch-sensitive display 110. The touch-sensitive display 110 is not only touch-sensitive but also displays information to the user. The secondary screen 108 includes a touch-sensitive display 114 that also displays information to the user. In other embodiments, screens 104 and 108 may include more than one display area.

  The primary screen 104 also includes a configurable area 112 that is configured for specific input when the user touches a portion of the configurable area 112. The secondary screen 108 also includes a configurable area 116 that is configured for specific inputs. Areas 112a and 116a are configured to receive a “back” input indicating that the user wishes to view previously displayed information. Areas 112b and 116b are configured to receive a “menu” input indicating that the user wishes to view options from the menu. Areas 112c and 116c are configured to receive a “home” input indicating that the user wishes to view information associated with the “home” view. In other embodiments, areas 112a-c and 116a-c can be configured for other types of specific inputs, including control of features of device 100, in addition to the configurations described above, Non-limiting examples include overall system power adjustment, volume adjustment, brightness adjustment, vibration adjustment, display item selection (either screen 104 or 108), camera operation, microphone Examples include operation and start / end of a call. Also, in some embodiments, areas 112a-c and 116a-c are specific inputs depending on the application running on device 100 and / or information displayed on touch-sensitive displays 110 and / or 114. Can be configured for.

  In addition to touch-sensitive, primary screen 104 and secondary screen 108 also include areas where the user does not need to touch the display area of the screen and receives input from the user. For example, the primary screen 104 includes a gesture capture area 120 and the secondary screen 108 includes a gesture capture area 124. These areas can receive input, for example, by recognizing gestures made by the user without having to actually touch the surface of the display area. Compared to touch-sensitive displays 110 and 114, gesture capture areas 120 and 124 are generally unable to render a display image.

  The two screens 104 and 108 are connected by a hinge 128, which is clearly shown in FIG. 1C (showing a rear view of the device 100). In the embodiment shown in FIGS. 1A-1J, the hinge 128 is the central hinge that connects the screens 104 and 108, so that when the hinge is closed, the screens 104 and 108 are in FIG. Are juxtaposed (ie, side by side) as shown. The hinge 128 can be opened to place the two screens 104 and 108 in a relatively different arrangement. As described in more detail below, device 100 may have different functionality depending on the relative positions of screens 104 and 108.

  FIG. 1D shows the right side of the device 100. As shown in FIG. 1D, the secondary screen 108 also includes a card slot 132 and a port 136 on its side. In an embodiment, the card slot 132 houses different types of cards that include a subscriber identity module (SIM). In an embodiment, port 136 is an input / output port (I / O port) that allows device 100 to be connected to other peripheral devices such as a display, keyboard, or printing device. As can be appreciated, these are just some examples, and in other embodiments, the device 100 may include slots and ports for accommodating additional memory devices and / or for connecting other peripheral devices, etc. Other slots and ports may be included. Also shown in FIG. 1D is an audio jack 140 that houses, for example, a tip, ring, and sleeve (TRS) connector that allows the user to use headphones or headsets.

  The device 100 also includes a number of buttons 158. For example, FIG. 1E shows the left side of the device 100. As shown in FIG. 1E, the side of primary screen 104 includes three buttons 144, 148, and 152, which can be configured for specific inputs. For example, the buttons 144, 148 and 152 can be configured to control many aspects of the device 100 in combination or alone. Some non-limiting examples include overall system power, volume, brightness, vibration, selection of display items (either screen 104 or 108), camera, microphone, and call start / end. In some embodiments, two buttons can be combined into a rocker button instead of separate buttons. This configuration is useful in situations where buttons are configured to control features such as volume or brightness. In addition to buttons 144, 148, and 152, device 100 also includes a button 156 as shown in FIG. In one embodiment, button 156 is configured as an on / off button that is used to control overall system power to device 100. In other embodiments, button 156 is configured to control other aspects of device 100 in addition to or in place of system power control. In some embodiments, one or more of the buttons 144, 148, 152, and 156 can support different user commands. As an example, a normal press generally has a duration of less than about 1 second and resembles a quick tap. Medium presses generally have a duration of more than 1 second but less than about 12 seconds. Long presses (long presses) generally have a duration of about 12 seconds or more. The button functionality is typically specific to the application currently focused on the respective displays 110 and 114. For example, in a call application, depending on a particular button, a normal, medium or long press can mean call termination, call volume increase, call volume decrease, microphone mute switching. For example, in a camera or video application, depending on the particular button, a normal, medium or long press can mean zooming in, zooming out, taking a picture or recording a video.

  In addition, the device 100 has many hardware components. As shown in FIG. 1C, the device 100 includes a speaker 160 and a microphone 164. Device 100 also includes a camera 168 (FIG. 1B). In addition, the device 100 includes two position sensors 172a and 172b, which are used to determine the relative positions of the screens 104 and 108. In one embodiment, position sensors 172a and 172b are Hall effect sensors. However, in other embodiments, other sensors can be used in addition to or instead of the Hall effect sensor. Also, accelerometer 176 can be included as part of device 100 to determine the orientation of device 100 and / or the orientation of screens 104 and 108. Additional internal hardware components that can be included in device 100 are described below in connection with FIG.

  The overall design of device 100 allows for the provision of additional functionality that is not available on other communication devices. Some of the functionality is based on the various positions and orientations that the device 100 may have. As shown in FIGS. 1B-1G, device 100 can be operated in an “open” position where screens 104 and 108 are juxtaposed. This location allows a large display area for displaying information to the user. Once the position sensors 172a and 172b determine that the device 100 is in the open position, the position sensors 172a and 172b provide signals that can be used to trigger different events such as displaying information on both screens 104 and 108. Can be generated. An additional event can be triggered when the accelerometer 176 determines that the device 100 is in a portrait position (FIG. 1B) opposite a landscape position (not shown).

  In addition to the open position, device 100 may also have a “closed” position as shown in FIG. 1H. Again, the position sensors 172a and 172b can generate a signal indicating that the device 100 is in the “closed” position. This can trigger an event that results in a change in the information displayed on the screens 104 and / or 108. For example, if the device 100 is in the “closed” position, the user can only view one screen, so the device 100 is programmed to stop displaying information on one of the screens, eg, the screen 108. can do. In other embodiments, the signal generated by the position sensors 172a and 172b, indicating that the device 100 is in the “closed” position, can trigger the device 100 to respond to a telephone call. The “closed” position may also be a preferred position when using device 100 as a mobile phone.

  Device 100 may also be used in an “Easel” position as shown in FIG. In the “Easel” position, the screens 104 and 108 are angled toward each other and the edges of the screens 104 and 108 are substantially horizontal. In this position, the device 100 can be configured to display information on both screens 104 and 108, allowing two users to exchange information with the device 100 simultaneously. When the device 100 is in the “Easel” position, the sensors 172a and 172b can generate a signal indicating that the screens 104 and 108 are angled with respect to each other, and the accelerometer 176 A signal can be generated indicating that the device 100 is positioned such that the edges of 108 are substantially horizontal. The signals can then be used in combination to generate an event that triggers a change in the display of information on the screens 104 and 108.

  FIG. 1J shows the device 100 in the “deformed easel” position. In the “deformed easel” position, one of the screens 104 or 108 is used as a stand and is placed face down on the surface of an object such as a table. This position provides a convenient way to display information to the user in landscape orientation. Similar to the easel position, when the device 100 is in the “deformed easel” position, the position sensors 172a and 172b generate signals indicating that the screens 104 and 108 are positioned at an angle to each other. The accelerometer 176 will generate a signal indicating that the device 100 is positioned so that it is substantially horizontal with one of the screens 104 and 108 facing down. The signal can then be used to generate an event that triggers a change in the display of information on screens 104 and 108. For example, since the user cannot see the screen, information may not be displayed on the downward screen.

  A transition state is also possible. If the position sensors 172a and b and / or the accelerometer indicate that the screen is closed or folded (from the open position), the transition state to closed is recognized. Conversely, if the position sensors 172a and b indicate that the screen is open or folded (from the closed position), the transition state to open is recognized. The transition state to closed and open is usually time based or has a maximum duration from the sensed starting point. Normally, user input is not possible when one of the closed and open states is in progress. Thus, accidental contact with the screen by the user during the closing or opening operation is not misinterpreted as user input. In an embodiment, another transition state is possible when the device 100 is closed. If the device 100 is closed due to this additional transition state, the display is switched from one screen 104 to the second screen 108 based on some user input such as a double tap on the screen 110, 114, for example. Is possible.

As can be appreciated, the description of device 100 is for illustrative purposes only, and the embodiments are not limited to the specific mechanical features shown in FIGS. 1A-1J and described above. In other embodiments, the device 100 may include additional features including one or more additional buttons, slots, display areas, hinges, and / or locking mechanisms. In addition, in embodiments, the features described above can be located in different parts of the device 100 and still provide similar functionality. Accordingly, FIGS. 1A-1J and the description provided above are non-limiting.
Hardware features:
FIG. 2 illustrates components of the device 100 according to an embodiment of the present disclosure. In general, the device 100 includes a primary screen 104 and a secondary screen 108. The primary screen 104 and its components are normally enabled in either the open or closed position or the closed position or state, while the secondary screen 108 and its components are normally enabled in the open state, but in the closed state. It is invalidated. However, even in the closed state, an interrupt triggered by the user or application (such as in response to a call application or camera application operation) can change the active screen or disable the primary screen 104 with the appropriate command. The secondary screen 108 can also be activated. Each screen 104, 108 may be touch sensitive and may include a different operating area. For example, the first operating area within each touch sensitive screen 104 and 108 may include touch sensitive displays 110, 114. In general, touch sensitive displays 110, 114 may include full color touch sensitive displays. A second area within each touch-sensitive screen 104 and 108 may include gesture capture areas 120, 124. The gesture capture area 120, 124 may include an area or area outside the area of the touch-sensitive display 110, 114 that may receive input in the form of a gesture provided by the user, for example. is there. However, the gesture capture areas 120, 124 do not include pixels that can perform display functions or capabilities.

  The third area of touch sensitive screens 104 and 108 may include configurable areas 112, 116. Configurable areas 112, 116 can receive input and have display or limited display capabilities. In an embodiment, the configurable areas 112, 116 may present different input options to the user. For example, configurable areas 112, 116 may display buttons or other associated items. In addition, the identity of the displayed button or whether there is a button displayed in the configurable area 112, 116 of the touch-sensitive screen 104 or 108 is used and / or manipulated by the device 100. Can be determined from the context to be. In the exemplary embodiment, touch-sensitive screens 104 and 108 receive input from the user and a liquid crystal display device that spans at least those areas of touch-sensitive screens 104 and 108 that can provide visual output to the user. And a capacitive input matrix over those areas of touch sensitive screens 104 and 108 that can be made.

  One or more display controllers 216a, 216b may be provided to control the operation of touch sensitive screens 104 and 108 including input (touch sensitive) and output (display) functions. In the exemplary embodiment shown in FIG. 2, a separate touch screen controller 216a or 216b is provided for each touch screen 104 and. According to an alternative embodiment, a common or shared touch screen controller 216 can be used to control each of the included touch sensitive screens 104 and 108. According to yet other embodiments, the functionality of the touch screen controller 216 can be incorporated into other components such as the processor 204.

  The processor 204 may include a general purpose programmable processor or controller for executing application programming or instructions. According to at least some embodiments, the processor 204 can include multiple processor cores and / or implement multiple virtual processors. According to yet other embodiments, the processor 204 may include multiple physical processors. As a specific example, processor 204 may be a specially configured application specific integrated circuit (ASIC) or other integrated circuit, digital signal processor, controller, wired electronics or logic circuit, programmable logic device or gate array, dedicated A computer or the like may be included. The processor 204 generally functions to execute programming code or instructions that implement various functions of the device 100.

  The communication device 100 may also include a memory 208 for use in connection with application programming or execution of instructions by the processor 204 and for storing program instructions and / or data temporarily or over time. By way of example, memory 208 may include RAM, DRAM, SDRAM, or other solid state memory. As an alternative or in addition, a data storage 212 may be provided. Similar to memory 208, data storage 212 may include one or more solid state memory devices. Alternatively or additionally, data storage 212 may include a hard disk drive or other random access memory.

  In supporting a communication function or capability, the device 100 may include a mobile phone module 228. By way of example, cell phone module 228 may include GSM, CDMA, FDMA, and / or analog cell phone transceivers that can support voice, multimedia, and / or data transfer over a cellular network. As an alternative or in addition thereto, the device 100 may include additional or other wireless communication modules 232. By way of example, other wireless communication modules 232 may include Wi-Fi, Bluetooth, WiMax, infrared, or other wireless communication links. The cell phone module 228 and the other wireless communication module 232 can each be associated with a shared or dedicated antenna 224.

  A port interface 252 can be included. The port interface 252 may include a unique or universal port that supports the interconnection of the device 100 with other devices or components, such as a dock, where other devices or components are in addition to or indispensable for the device 100. It may or may not include different abilities. In addition to supporting the exchange of communication signals between device 100 and another device or component, docking port 136 and / or port interface 252 support the supply of power to or from device 100. Can do. The port interface 252 also includes intelligent elements including a docking module for controlling communication or other interactions between the device 100 and connected devices or components.

  The input / output module 248 and associated ports can be included, for example, to support communication over a wired network or link with other communication devices, server devices, and / or peripheral devices. Examples of the input / output module 248 include an Ethernet port, universal serial bus (USB) port, Institute of Electrical and Electronics Engineers (IEEE) 1394, or other interface.

  An audio input / output interface / device 244 may be included to provide analog audio to interconnected speakers or other devices, or receive analog audio input from connected microphones or other devices. As an example, the audio input / output interface / device 244 may include an associated amplifier and an analog to digital converter. Alternatively or additionally, device 100 may include an integrated audio input / output device 256 and / or audio jack for interconnecting external speakers or microphones. For example, an integrated speaker and integrated microphone can be provided to support close-in calling or speakerphone operation.

  The hardware button 158 can be used, for example, in connection with certain control operations. Examples include a master power switch, volume control, etc., as described in conjunction with FIGS. One or more image capture interfaces / devices 240 such as cameras can be included to capture still and / or video images. Alternatively or additionally, the image capture interface / device 240 may include a scanner or code reader. The image capture interface / device 240 may include or be associated with additional elements such as a flash or other light source.

  Device 100 may also include a global positioning system (GPS) receiver 236. According to embodiments of the present invention, the GPS receiver 236 may further include a GPS module that can provide absolute position information to other components of the device 100. An accelerometer 176 can also be included. For example, in connection with displaying information to the user and / or other functions, signals from the accelerometer 176 can be used to determine the direction and / or format for displaying that information to the user. .

  Embodiments of the invention may also include one or more position sensors 172. The position sensor 172 can provide a signal indicating the position of the touch-sensitive screens 104 and 108 relative to each other. For example, this information can be provided as input to a user interface application to determine the operating mode, i.e. characteristics of touch-sensitive displays 110, 114 and / or other device 100 operations. By way of example, the screen position sensor 172 may provide a series of Hall effect sensors, a plurality of position switches, a light switch, a Wheatstone bridge, a potentiometer, or a signal indicating a plurality of relative positions where the touch screen is located. Other configurations that can be included.

Communication between the various components of the device 100 can occur over one or more buses 222. In addition, power can be supplied to the components of the device 100 from the power supply and / or power control module 260. The power control module 260 may include a port for interconnecting the device 100 to, for example, a battery, an AC / DC converter, power control logic, and / or an external power source.
Device status:
3A and 3B represent an exemplary state of the device 100. FIG. Many example states are shown and transition from the first state to the second state, but the diagram illustrating the example states is from all possible states and / or from all possible first states. It should be understood that it does not encompass a transition to the second state. As shown in FIG. 3, various arrows between the states (indicated by states represented by circles) represent physical changes that occur in the device 100. The physical change is detected by one or more of hardware and software, and the detection triggers one or more of the hardware and / or software interrupts to control one or more functions of device 100 and Used for management.

  As shown in FIG. 3A, there are twelve exemplary “physical” states: closed 304, transition 308 (or transition state to open), easel 312, modified easel 316, open 320, incoming / outgoing Outgoing call or communication 324, image / video capture 328, transition 332 (or closed transition state), landscape 340, docking 336, docking 344 and landscape 348. Next to each exemplary state is a representation of the physical state of the device 100, with the exception of states 324 and 328, where the state is generally an international It is symbolized by an icon and a camera icon.

  In state 304, the device is in a closed state and device 100 is generally oriented in a vertical orientation with primary screen 104 and secondary screen 108 back to back on different surfaces (see FIG. 1H). From the closed state, the device 100 can enter, for example, a docking state 336 or a sideways state 340 where the device 100 is coupled with a docking station or docking cable, or generally one or more. In the landscape state 340, the primary screen 104 faces the user and the primary screen 104 and the secondary screen 108 are back to back and the device 100 is generally oriented in a docked or associated state with other devices or peripheral devices. .

  Also, in the closed state, the device can move to the transition state, and in the transition state, the device remains closed, but the display is based on user input, such as a double tap on the screen 110, 114, for example. Thus, the screen moves from one screen 104 to another screen 108. Yet another embodiment includes a bilateral state. In the duplex state, the device remains closed, but a single application displays at least one window on both the first display 110 and the second display 114. The windows shown on the first and second displays 110, 114 may be the same or different based on the application and the state of the application. For example, while acquiring an image with the camera, the device can display a finder on the first display 110 and display a preview of the subject (full screen and mirrored from left to right) on the second display 114. To do.

  In state 308, which is a transition from a closed state 304 to a half-open state or an easel state 312, the device 100 is opened with the primary screen 104 and the secondary screen 108 rotated about a point on the axis that coincides with the hinge. Indicated. Upon entering the easel state 312, the primary screen 104 and the secondary screen 108 are separated from each other such that the device 100 can be located on the surface in an easel-like configuration, for example.

  In state 316, known as the deformed easel position, device 100 has a primary screen 104 and a secondary screen 108 that are in a relative relationship to each other similar to easel state 312, with the difference being primary screen 104 or One of the secondary screens 108 is placed on the surface.

  State 320 is an open state, where primary screen 104 and secondary screen 108 are generally on the same plane. From the open state, the device 100 can transition to a docked state 344 or an open sideways state 348. In the open state 320, the primary screen 104 and the secondary screen 108 are generally in a state that is vertically oriented, whereas in the landscape state 348, the primary screen 104 and the secondary screen 108 are generally in a state that is horizontally oriented. is there.

  The state 324 is an example of a communication state when the device 100 receives an incoming call or makes an outgoing call. Although not explicitly shown, it should be understood that the device 100 can transition to the incoming / outgoing call state 324 from any state shown in FIG. Similarly, the image / video capture state 328 can also be entered from any of the other states shown in FIG. 3, in which the device 100 includes a camera with a video capture device 240 and / or Alternatively, one or more images can be taken via video.

The transition state 332 exemplarily shows a state in which the primary screen 104 and the secondary screen 108 are closed toward each other to enter the closed state 304, for example.
FIG. 3B shows the input received to detect the transition from the first state to the second state with reference to the key. In FIG. 3B, various combinations of states are shown, and in general, some of the columns are in the portrait state 352 and landscape state 356, and some of the rows are in the portrait state 360 and landscape state 364. set to target.

  In FIG. 3B, the keys indicate that “H” represents input from one or more Hall effect sensors, “A” represents input from one or more accelerometers, and “T” represents input from a timer. “P” represents a communication trigger input, and “I” represents an image and / or video capture request input. Accordingly, the central portion 376 of the table shows an input or combination of inputs that represents how the device 100 detects a transition from a first physical state to a second physical state.

  As discussed, in the center portion 376 of the table, the received input enables detection of, for example, a transition from a vertically open state to a landscape easel state (shown in bold “HAT”). In the transition from this exemplary portrait open state to landscape easel state, Hall effect sensor (“H”), accelerometer (“A”) and timer (“T”) inputs may be required. The timer input can be obtained, for example, from a clock associated with the processor.

In addition to the portrait and landscape states, a docking state 368 that is triggered based on receipt of the docking signal 372 is also shown. As discussed above, in connection with FIG. 3, the docking signal triggers by connecting the device 100 with one or more other devices 100, accessories, peripherals, smart docks or the like. be able to.
User interaction:
4A-4H depict various graphical representations of gesture input that can be recognized by screens 104,108. Gestures can be made not only by the user's body part, such as a finger, but also by other devices, such as a stylus that can be sensed by the touch sensitive part of the screen 104,108. In general, gestures are interpreted differently based on where the gesture is made (either directly on the display 110, 114 or the gesture capture area 120, 124). For example, gestures in the displays 110, 114 may be targeted to a desktop or application, and gestures in the gesture capture area 120, 124 may be interpreted for the system.

  4A-4H, the first type of gesture (touch gesture 420) is substantially stationary on the screen 104, 108 for a selected length of time. Circle 428 represents a touch or other contact type received at a particular location in the touch sensitive portion of the screen. The circle 428 may include a boundary 432 whose thickness indicates the length of time that contact has been held in a substantially stationary state at the contact location. For example, tap 420 (or short press) has a boundary 432a that is thinner than boundary 432b for long press 424 (or for a normal press). The long press 424 may involve contact that remains substantially stationary on the screen for a longer time than the tap 420. As will be appreciated, differently defined gestures can be registered according to the length of time that the touch remains stationary before touching or moving on the screen.

  Referring to FIG. 4C, the drag gesture 400 on the screen 104, 108 is accompanied by a contact movement 436 in the selected direction with the initial contact (represented by a circle 428). Initial contact 428 may remain stationary on screens 104, 108 for a specific amount of time represented by boundary 432. Drag gestures typically move the contact in a drag direction where the user touches an icon, window or other display image at a first location, and then toward the desired new second location for the selected display image. It is necessary to let The contact movement need not be a straight line, but can be any path movement as long as the contact is substantially continuous from the first to the second position.

  Referring to FIG. 4D, the flick gesture 404 on the screens 104, 108 is shown in the first contact (represented by a circle 428) with a shortened contact movement 436 (compared to the drag gesture) in the selected direction. ). In an embodiment, the flick has a higher exit speed for the last movement of the gesture compared to the drag gesture. The flick gesture can be, for example, a finger snap following the initial contact. Compared to drag gestures, flick gestures generally do not require continuous contact with the screens 104, 108 from a first position of the display image to a predetermined second position. The touched display image is moved in the flick gesture direction toward the predetermined second position by the flick gesture. Both gestures can generally move the displayed image from the first position to the second position, but the duration and distance of the touch on the screen is generally greater for flick gestures than for drag gestures. Is short.

  Referring to FIG. 4E, a pinch gesture 408 on the screens 104, 108 is depicted. The pinch gesture 408 can be undertaken, for example, by making a first contact 428a on the screens 104, 108 with a first finger and making a second contact 428b on the screens 104, 108 with a second finger, for example. it can. The first and second contacts 428a, b may be by a common touch-sensitive portion of the common screen 104,108, by a different touch-sensitive portion of the common screen 104 or 108, or by a different touch-sensitive portion of a different screen. Can be detected. The first contact 428a is held for a first amount of time, as represented by boundary 432a, and the second contact 428b is held for a second amount of time, as represented by boundary 432b. Is done. The first and second amount of time is generally substantially the same, and the first and second contacts 428a, b generally occur substantially simultaneously. Also, the first and second contacts 428a, b generally include corresponding first and second contact movements 436a, b, respectively. The first and second contact movements 436a, b are generally in opposite directions. In other words, the first contact movement 436a is in the direction toward the second contact 428b, and the second contact movement 436b is in the direction toward the first contact 428a. In other words, the pinch gesture 408 can be realized by the user's finger touching the screens 104 and 108 by a pinch operation.

  Referring to FIG. 4F, a spread gesture 410 on the screen 104, 108 is depicted. Spread gesture 410 can be undertaken, for example, by making first contact 428a on screens 104, 108 with a first finger and making second contact 428b on screens 104, 108 with a second finger, for example. it can. The first and second contacts 428a, b may be by a common touch-sensitive portion of the common screen 104,108, by a different touch-sensitive portion of the common screen 104 or 108, or by a different touch-sensitive portion of a different screen. Can be detected. The first contact 428a is held for a first amount of time, as represented by boundary 432a, and the second contact 428b is held for a second amount of time, as represented by boundary 432b. Is done. The first and second amount of time is generally substantially the same, and the first and second contacts 428a, b generally occur substantially simultaneously. Also, the first and second contacts 428a, b generally include corresponding first and second contact movements 436a, b, respectively. The first and second contact movements 436a, b are generally in a common direction. In other words, the first and second contact movements 436a, b are in a direction away from the first and second contacts 428a, b. In other words, the spread gesture 410 can be realized by the user's finger touching the screens 104 and 108 by a spread operation.

  The above gestures can be combined in any way, such as that shown by FIGS. 4G and 4H, to produce a determined functional result. For example, in FIG. 4G, a tap gesture 420 and a drag or flick gesture 412 in a direction away from the tap gesture 420 are combined. In FIG. 4H, tap gesture 420 is combined with a drag or flick gesture 412 in a direction toward tap gesture 420.

  The functional outcome of receiving a gesture may depend on a number of factors including the state of the device 100, the display 110, 114 or the screen 104, 108, the context associated with the gesture, or the sensed position of the gesture. The state of the device generally refers to one or more of the configuration of the device 100, the display orientation, and the user and other inputs received at the device 100. The context is generally whether the application is a single screen application or a multi-screen application, and the application will be a multi-screen application that displays one or more windows on one or more screens. Is a multi-screen application that displays one or more windows in one or more stacks, but one or more of the specific application selected by the gesture and the part of the application that is currently running Refers to multiple. The sensed position of a gesture is typically determined by whether the sensed gesture position coordinate set is on the touch-sensitive display 110, 114 or in the gesture capture area 120, 124, and the sensed gesture position coordinate set is common. Refers to whether it is associated with a display or screen 104, 108, or is associated with a different display or screen 104, 108, and / or which part of the gesture capture area contains a sensed gesture position coordinate set.

  When a tap is received on the touch-sensitive display 110, 114, for example, the start or end of execution of the corresponding application, maximization or minimization of the window, reordering of the windows in the stack, and keyboard display or other It can be used when selecting an icon to provide user input by a display image or the like. When a drag is received on the touch-sensitive displays 110, 114, for example, moving the icon or window to the desired position in the display, reordering the stack on the display, or spanning both displays (as a result The selected window can be used when simultaneously occupying a portion of each display). When the flick is received on the touch sensitive display 110, 114 or the gesture capture area 120, 124, for example, it moves the window from the first display to the second display or spans both displays (as a result The selected window can be used when simultaneously occupying a portion of each display). However, unlike drag gestures, flick gestures are generally not used when moving a display image to a specific user-selected position, but when moving a display image to a default position that cannot be configured by the user. used.

  A pinch gesture minimizes or increases the display area or size of the window when receiving on the touch-sensitive display 110, 114 or the gesture capture area 120, 124 (usually when receiving the whole on a common display) Switch the window that appears at the top of the stack on the display to the top of the stack on another display (usually when receiving on a different display or screen), or display the application manager (display the window on the stack) "Pop-up window") can be used. Spread gestures, when received on touch-sensitive displays 110, 114 or gesture capture areas 120, 124, maximize the window display area or size and reduce the window displayed at the top of the stack on each display. Used when switching to the top of another display stack (usually when receiving on a different display or screen) or when displaying the application manager (when receiving in an off-screen gesture capture area on the same or different screen) can do.

The combined gesture of FIG. 4G retains the first window stack position in a constant first stack on the display that receives the gesture when received on a common display or common display capture area within the screen 104,108. On the other hand, the second window stack position can be rearranged into the second window stack and used to include the window in the display that receives the gesture. When the combined gesture of FIG. 4H is received on a common display or screen 104, 108 or a different display or different display capture area within the screen, the display receiving the tap portion of the gesture is in a constant first window stack. While maintaining the first window stack position, the second window stack position can be rearranged into the second window stack for use in including a window on a display that receives a flick or drag gesture. Although specific gestures and gesture capture regions in the previous examples have been associated with a corresponding set of functional results, these associations can be redefined in any way, and gestures and / or gesture capture regions and / or It should be understood that different associations can be generated between functional results.
Firmware and software:
Memory 508 can store one or more software components, and processor 504 can execute it. These components may include at least one operating system (OS) 516, application manager 562, desktop 566 and / or one or more applications 564a and / or 564b from application store 560. The OS 516 may include a framework 520, one or more frame buffers 548, one or more drivers 512, and / or a kernel 518 as previously described in conjunction with FIG. The OS 516 can be any software comprised of programs and data, which manage computer hardware resources and provide common services for the execution of various applications 564. The OS 516 may be any operating system, and in at least some embodiments, but not limited to, Linux (R), Android (R), iPhone OS (iPhone OS). (IOS (registered trademark)), Windows Phone 7 (Windows Phone 7) (registered trademark), and the like. OS 516 is operable to provide functionality to the phone by performing one or more operations as described herein.

  Application 564 may be any high level software that performs specific functionality for the user. Applications 564 may include programs such as email clients, web browsers, text message applications, games, media players, office suites, and the like. Application 564 can be stored in application store 560, which can represent any memory or data storage for storing application 564 and management software associated therewith. Once executed, the application 564 can execute in different areas of the memory 508.

  The framework 520 may be any software or data that allows multiple tasks that are running on the device to interact. In an embodiment, at least a portion of framework 520 and the individual components described below may be considered part of OS 516 or application 564. However, these parts are described as part of the framework 520, except that their components are not so limited. Framework 520 includes, but is not limited to, multiple display management (MDM) module 524, surface cache module 528, window management module 532, input management module 536, task management module 540, application model manager 542, display controller, one Alternatively, it may include a plurality of frame buffers 548, a task stack 552, one or more window stacks 550 (which are a logical arrangement of windows and / or desktops in the display area) and / or an event buffer 556.

  The MDM module 524 includes one or more modules operable to manage the display of applications or other data on the screen of the device. An embodiment of the MDM module 524 is described in conjunction with FIG. 5B. In an embodiment, the MDM module 524 receives input from other OS 516 components such as the driver 512 and from the application 564 and always determines the state of the device 100. The inputs assist the MDM module 524 in determining how to configure and assign the display according to application priority and requirements and user behavior. Once a decision on the display configuration is made, the MDM module 524 can combine the application 564 and the display. The configuration can then be provided to one or more other components to generate a window on the display.

  Surface cache module 528 includes any memory or storage and associated software for storing or caching one or more images of the window. A series of active and / or inactive windows (or other display objects such as a desktop display) may be associated with each display. The active window (or other display object) is currently displayed. An inactive window (or other display object) was opened and displayed at some point, but is not currently displayed. To enhance the user experience, a “screen shot” of the last generated image of the window (or other display object) can be stored before transitioning the window from the active state to the inactive state. The surface cache module 528 may be operable to store a bitmap of the last active image of a window (or other display object) that is not currently displayed. Accordingly, the surface cache module 528 stores an image of the inactive window (or other display object) in the data store.

  In an embodiment, window management module 532 is operable to manage windows (or other display objects) that are active or inactive on their respective displays. Window management module 532 determines when a window (or other display object) is visible or inactive based on information from MDM module 524, OS 516, or other components. The window management module 532 then places the invisible window (or other display object) in an “inactive state” and suspends the operation of the application in conjunction with the task management module task management 540. In addition, the window management module 532 can assign a display identifier to a window (or other display object) through a cooperative interaction with the MDM module 524, and can also include one of the data associated with the window (or other display object). One or more other items can also be managed. Window management module 532 may also provide information stored in application 564, task management module 540, or other components that interact with or are associated with windows (or other display objects). The window management module 532 can also associate an input task with a window based on window focus and display coordinates in the motion space.

  The input management module 536 is operable to manage events that occur on the device. An event is any input to a window environment, such as a user interface interaction with a user. The input management module 536 receives the event and logically stores the event in the event buffer 556. An event is such a user interface interaction, a “down event” that occurs when the screen 104, 108 receives a touch signal from the user, indicating that the user's finger is moving across the screen 104, 108. May be included as a “movement event” that occurs when the screen 104, 108 is determined, an “up event” that occurs when the screen 104, 108 determines that the user has stopped touching the screen 104, 108, or the like. These events are received, stored and forwarded to other modules by the input management module 536. The input management module 536 can also map screen input to an operational space that is a culmination of all physical and virtual displays available on the device.

  The operational space is a virtualized space that includes all touch sensitive displays 110, 114 that are “tiled” together to mimic the physical dimensions of the device 100. For example, if the device 100 is deployed, the motion space size may be 960 × 800, which may be the number of pixels in the combined display area of both touch-sensitive displays 110, 114. If the user touches the first touch-sensitive display 110 at position (40, 40), the full screen window can receive a touch event at position (40, 40). If the user touches the second touch-sensitive display 114 at position (40, 40), the full screen window can receive a touch event at position (520, 40) because the second The touch-sensitive display 114 is to the right of the first touch-sensitive display 110, so that the device 100 offsets its touch by the width of the first touch-sensitive display 110, ie, 480 pixels. This is because it can be provided. If a hardware event occurs with location information from the driver 512, the framework 520 can upscale the physical location to the operational space because the location of the event can vary based on the orientation and state of the device. The operational space receives “gesture input spanning multiple input devices” filed on July 20, 2011, which is incorporated herein by reference in its entirety for all and all purposes it teaches. US Pat. Application No. 13 / 187,026, entitled “Systems and Methods for Receiving Gesture Inputs Spanning Multiple Input Devices”.

  A task can be an application, and a subtask is a window where users can exchange information to do something, for example, call, take a picture, send an email, or view a map. It can be an application component to provide. Each task can be given a window for drawing a user interface. The window typically occupies the entire display (eg, touch sensitive displays 110, 114), but is smaller than the displays 110, 114 and may float on other windows. An application typically consists of multiple subtasks that are loosely coupled together. Typically, one task in an application is designated as the “main” task and is presented to the user when first starting the application. Each task can then initiate another task or subtask to perform a different operation.

  Task management module 540 is operable to manage the operation of one or more applications 564 that can be executed by the device. Therefore, the task management module 540 can receive the signal and start, pause, end, and the like of the application or application subtask stored in the application store 560. Task management module 540 may then create an instance of one or more tasks or subtasks of application 564 and begin operation of application 564. Further, the task management module 540 can initiate, pause or terminate a task or subtask as a result of user input or as a result of a signal from a collaborative framework 520 component. The task management module 540 is responsible for managing the lifecycle of applications (tasks and subtasks) from application start to application termination.

  The processing of the task management module 540 is facilitated by a task stack 552, which is a logical structure associated with the task management module 540. Task stack 552 maintains the state of all tasks and subtasks on device 100. The OS 516 component can notify the task management module 540 when some component of the operating system 516 needs to cause a task or subtask to make a transition in its life cycle. The task management module 540 then uses the identification information to locate the task or subtask in the task stack 552 and sends a signal to the task or subtask indicating what lifecycle transition the task needs to perform. By notifying the task or subtask about the transition, the task or subtask can prepare for the lifecycle state transition. The task management module 540 can then perform a state transition for the task or subtask. In an embodiment, the state transition may involve triggering the OS kernel 518 to terminate the task when termination is required.

  Further, the task management module 540 can suspend the application 564 based on information from the window management module 532. Suspending application 564 can maintain application data in memory, but may limit or stop application 564 from rendering the window or user interface. When the application becomes active again, the task management module 540 can again trigger the application to render its user interface. In an embodiment, if a task is paused, the task can save the task state if the task is terminated. In the paused state, the application window cannot be seen by the user, so the application task cannot receive input.

  The frame buffer 548 is a logical structure used for user interface rendering. Frame buffer 548 may be created and destroyed by OS kernel 518. However, the display controller 544 can write image data into the frame buffer 548 for the visible window. Frame buffer 548 may be associated with one screen or multiple screens. The association of the frame buffer 548 with the screen can be dynamically controlled by interaction with the OS kernel 518. A composite display can be created by associating multiple screens with a single frame buffer 548. The graphical data used to render the user interface of the application window can then be written to a single frame buffer 548 for the composite display, which is output to multiple screens 104, 108. The display controller 544 can move the application's user interface to a portion of the frame buffer 548 that is mapped to a particular display 110, 114, thus displaying the user interface only on one screen 104 or 108. be able to. Display controller 544 can extend user interface control to multiple applications and control the user interface for as many displays as are associated with frame buffer 548 or a portion thereof. This approach compensates for multiple physical screens 104, 108 that are in use by software components on the display controller 544.

  The application manager 562 is an application that provides a presentation layer for the window environment. Accordingly, application manager 562 provides a graphical model for rendering by task management module 540. Similarly, desktop 566 provides a presentation layer for application store 560. Thus, the desktop provides a graphical model of the surface with selectable application icons for applications 564 in application store 560 that can be provided to window management module 556 for rendering.

  Further, the framework may include an application model manager (AMM) 542. Application manager 562 can interface with AMM 542. In an embodiment, the AMM 542 receives state change information from the device 100 regarding the state of the application (running or paused). AMM 542 may associate the bitmap image from surface cache module 528 with an active (running or paused) task. In addition, the AMM 542 uses a linear ("film strip" or "films") that captures the logical window stack maintained within the task management module 540 as the windows are separated using the gesture capture area 120 outside the display. A set of playing cards ") can be converted into an organization. Further, AMM 542 may provide a list of running applications to application manager 562.

  An embodiment of the MDM module 524 is shown in FIG. 5B. The MDM module 524 includes, but is not limited to, device orientation, whether the device 100 is open or closed, which application 564 is running, how the application 564 is displayed, and what action the user performs. It is operable to determine the state of the environment for the device that is performing, including the task being displayed, etc. To configure the display, the MDM module 524 interprets these environmental factors and determines the display configuration, as described in conjunction with FIGS. The MDM module 524 can then combine the application 564 or other device component with the display. The configuration can then be sent to display controller 544 and / or other components within OS 516 to generate a display. The MDM module 524 includes, but is not limited to, one or more of a display configuration module 568, a priority module 572, a device status module 574, a gesture module 576, a requirements module 580, an event module 584, and / or a binding module 588. Can be included.

  Display configuration module 568 determines the layout for the display. In embodiments, the display configuration module 568 can determine environmental factors. Environmental factors may be received from one or more other MDM modules 524 or from other sources. The display configuration module 568 can then determine the optimal configuration for the display from the list of factors. Some embodiments of possible configurations and associated factors are described in conjunction with FIGS.

  The priority module 572 is operable to determine the display priority of the application 564 or other component. For example, an application may have a priority for single or dual displays. The priority module 572 can determine the display priority of the application (eg, by examining the priority setting of the application) and if the device 100 is in a state that can support the preferred mode, the application 564 may allow changing modes (eg, single screen, dual screen, maximum, etc.). However, some user interface policies may not allow a mode even if that mode is available. As the device configuration changes, the priority can be reviewed to determine whether a better display configuration can be achieved for the application 564.

  Device status module 574 is operable to determine or receive the status of the device. The state of the device may be as described in conjunction with FIGS. 3A and 3B. The device status can be used in the display configuration module 568 to determine the configuration of the display. In this way, the device status module 574 can receive input and interpret the status of the device. The status information is then provided to the display configuration module 568.

  Although the gesture module 576 is shown as part of the MDM module 524, in an embodiment, the gesture module 576 may be a separate framework 520 component that is separate from the MDM module 524. In an embodiment, the gesture module 576 is operable to determine whether the user is performing any action at any part of the user interface. In an alternative embodiment, gesture module 576 receives user interface operations only from configurable areas 112, 116. The gesture module 576 can receive touch events that occur on the configurable areas 112, 116 (or possibly other user interface areas) using the input management module 536 and interpret the touch events. It is possible to determine what gesture the user is performing (using direction, speed, distance, duration and various other parameters). Once the gesture is interpreted, the gesture module 576 can begin processing the gesture and can work with other framework 520 components to manage the necessary window animation. Gesture module 576 collaborates with application model manager 542 to collect state information regarding which applications are running (active or paused) and the order in which the applications must appear when a user gesture is performed. To do. Also, the gesture module 576 can receive a bitmap (from the surface cache module 528) and a reference to the live window so that when a gesture occurs, the gesture module 576 crosses the display 110, 114 to the window. The display controller 544 can be instructed how to move. Thus, suspended applications appear to be running as their windows move across the displays 110,114.

  Further, the gesture module 576 can receive task information from either the task management module 540 or the input management module 536. The gesture may be as defined in conjunction with FIGS. For example, window movement causes the display to render a series of display frames that indicate window movement. Gestures associated with such user interface interactions can be received and interpreted by gesture module 576. Information about the user gesture is then sent to the task management module 540 to modify the task display binding.

  Similar to priority module 572, requirements module 580 is operable to determine display requirements for application 564 or other components. An application may have a set of display requirements that must be observed. Some applications require a specific display orientation. For example, the application “Angry Birds” can only be displayed in landscape orientation. This type of display requirement can be determined or received by the requirements module 580. When the device orientation is changed, the requirements module 580 can claim the display requirements for the application 564 again. Display configuration module 568 can generate a display configuration in accordance with application display requirements provided by requirements module 580.

  An event module 584 similar to the gesture module 576 is operable to determine one or more events that occur in an application or other component that can affect the user interface. Thus, event module 584 can receive event information from either event buffer 556 or task management module 540. These events can change how tasks are combined with the display. The event module 584 collects state change information from other framework 520 components and can be acted upon in response to the state change information. In one example, a new message is rendered on the secondary screen when the phone is opened or closed, or when a change of direction occurs. State changes based on this event can be received and interpreted by the event module 584. Information about the event can then be sent to the display configuration module 568 to modify the configuration of the display.

The combination module 588 is operable to combine the application 564 or other component with the configuration determined by the display configuration module 568. Binding associates the display configuration for each application with the display and mode of the application in memory. Thus, the combining module 588 can associate an application with a display configuration for the application (eg, landscape, portrait, multiple screens, etc.). The binding module 588 can then assign a display identifier to the display. The display identifier associates the application with a specific display on device 100. This combination is then stored and provided to display controller 544, other components of OS 516 or other components, and the display rendered properly. The binding is dynamic and can be changed or updated based on configuration changes associated with events, gestures, state changes, application priorities or requirements, and the like.
User interface configuration:
With reference now to FIGS. 6A-J, various types of output configurations enabled by the device 100 are described below.

  6A and 6B depict two different output configurations of device 100 in a first state. Specifically, FIG. 6A depicts the device 100 in a closed portrait state 304 and the data is displayed on the primary screen 104. In this example, the device 100 displays data via the touch-sensitive display 110 in the first portrait configuration 604. As can be appreciated, the first portrait configuration 604 can only display a desktop or operating system home screen. Alternatively, one or more windows can be presented in portrait orientation while the device 100 is displaying data in the first portrait configuration 604.

  FIG. 6B depicts the device 100 still in the closed portrait state 304, but instead the data is displayed on the secondary screen 108. In this example, the device 100 displays data via the touch-sensitive display 114 in the second portrait configuration 608.

  It may be possible to display similar or different data in either the first or second portrait configuration 604,608. Also, transitioning between the first portrait orientation 604 and the second portrait orientation 608 can be provided by providing the device 100 with a user gesture (eg, a double tap gesture), menu selection, or other means. It may be possible. Other suitable gestures can also be used to move between configurations. Moreover, depending on which state the device 100 is moved to, the device 100 may be transitioned from the first or second portrait configuration 604, 608 to any other configuration described herein. It may be possible.

  Alternative output configurations can be accommodated by the device 100 in the second state. Specifically, FIG. 6C depicts a third portrait configuration, where data is displayed on both primary screen 104 and secondary screen 108 simultaneously. The third portrait orientation may be referred to as a dual portrait (PD) output configuration. In the PD output configuration, the touch-sensitive display 110 on the primary screen 104 depicts data in the first portrait orientation 604, while the touch-sensitive display 114 on the secondary screen 108 has the second portrait orientation 608. Describe the data with. Simultaneous presentation of the first portrait configuration 604 and the second portrait configuration 608 may occur when the device 100 is in the open portrait state 320. In this configuration, the device 100 has one application window on one display 110 or 114, two application windows (one on each display 110 and 114), one application window and one desktop, or One desktop can be displayed. Other configurations may also be possible. Depending on which state the device 100 is moved to, it may be possible to transition the device 100 from the simultaneous display of configurations 604, 608 to any other configuration described herein. I want you to understand. Moreover, while in this state, depending on the display priority of the application, both displays may be active and the device may be placed in a duplex mode that displays different windows in the same application. For example, the camera application can display the viewfinder and controls on one side, while the other side displays a mirrored preview that can be viewed on the subject. A game involving simultaneous play by two players can also use the duplex mode.

  6D and 6E depict two additional output configurations for device 100 in a third state. Specifically, FIG. 6D depicts the device 100 in a closed landscape state 340 and the data is displayed on the primary screen 104. In this example, device 100 displays data via touch-sensitive display 110 in a first landscape configuration 612. Similar to the other configurations described herein, the first landscape configuration 612 may display a desktop, home screen, one or more windows that display application data, or the like.

  FIG. 6E depicts the device 100 still in the closed sideways state 340, but instead the data is displayed on the secondary screen 108. In this example, the device 100 displays data via the touch-sensitive display 114 in the second landscape configuration 616. It may be possible to display similar or different data in either the first or second landscape configuration 612,616. It may be possible to transition between the first sideways configuration 612 and the second sideways configuration 616 by providing the device 100 with one or both of twist and tap gestures or flip and slide gestures. Other suitable gestures can also be used to move between configurations. Moreover, depending on which state the device 100 is moved to, the device 100 can be transitioned from the first or second landscape configuration 612, 616 to any other configuration described herein. Can be.

  FIG. 6F depicts a third landscape configuration, where data is displayed on both the primary screen 104 and the secondary screen 108 simultaneously. The third landscape configuration may be referred to as a dual landscape (LD) output configuration. In the LD output configuration, the touch-sensitive display 110 on the primary screen 104 depicts data in the first landscape configuration 612 while the touch-sensitive display 114 on the secondary screen 108 displays data in the second landscape configuration 616. Describe. Simultaneous presentation of the first landscape configuration 612 and the second landscape configuration 616 may occur when the device 100 is in the open landscape state 340. Depending on which state the device 100 is moved to, it may be possible to move the device 100 from the simultaneous display of configurations 612, 616 to any other configuration described herein. I want you to understand.

  6G and 6H depict two views of device 100 in yet another state. Specifically, device 100 is depicted as being in easel state 312. FIG. 6G illustrates that the first easel output configuration 618 can be displayed on the touch-sensitive display 110. FIG. 6H illustrates that the second easel output configuration 620 can be displayed on the touch-sensitive display 114. Device 100 can be configured to individually depict either first easel output configuration 618 or second easel output configuration 620. Alternatively, both easel output configurations 618, 620 can be presented simultaneously. In some embodiments, the easel output configurations 618, 620 may be similar or identical to the landscape output configurations 612, 616. The device 100 may also be configured to display one or both of the easel output configurations 618, 620 while in the modified easel state 316. Simultaneous use of easel output configurations 618, 620 allows games for two players (eg, Battleship®, chess, checkers, etc.), two or more users sharing the same device 100 and other applications It should be understood that multiple user meetings can be facilitated. As can be appreciated, depending on which state the device 100 is moved to, the device 100 may be transitioned from one or both displays of configurations 618, 620 to any other configuration described herein. It may be possible.

  FIG. 6I depicts yet another output configuration that can be accommodated while the device 100 is in the open portrait state 320. Specifically, device 100 is configured to present a single continuous image across both touch-sensitive displays 110, 114 in a portrait orientation, referred to herein as a portrait orientation (PMax) configuration 624. Can do. In this configuration, data (eg, single image, application, window, icon, video, etc.) is split and displayed partially on one of the touch-sensitive displays while other parts of the data are otherwise displayed. Can be displayed on a touch-sensitive display. The Pmax configuration 624 can facilitate a larger display and / or better resolution for displaying a particular image on the device 100. As with other output configurations, device 100 can be transitioned from Pmax configuration 624 to any other output configuration described herein, depending on which state device 100 is moved to. There is a case.

  FIG. 6J depicts yet another output configuration that can be accommodated while the device 100 is in the open sideways state 348. Specifically, device 100 can be configured to present a single continuous image across both touch-sensitive displays 110, 114 in a landscape orientation, referred to herein as a landscape max (LMax) configuration 628. . In this configuration, data (eg, single image, application, window, icon, video, etc.) is split and displayed partially on one of the touch-sensitive displays while other parts of the data are otherwise displayed. Can be displayed on a touch-sensitive display. The Lmax configuration 628 can facilitate a larger display and / or better resolution for displaying a particular image on the device 100. As with other output configurations, device 100 can be transitioned from Lmax configuration 628 to any other output configuration described herein, depending on which state device 100 is moved to. There is a case.

  As shown in FIGS. 7A and 7B, the device 100 manages at least one of the desktop and windows in at least one window stack 700. The window stack 700 is a logical configuration of at least one of active and inactive windows or display objects for a multi-screen device. For example, the window stack 700 may be logically similar to a set of playing cards or a brick stack, and as shown in FIGS. 7A and 7B, one or more windows or display objects (eg, a desktop) may be , Arranged in order. The active window is a window currently displayed on at least one of the touch-sensitive displays 110 and 114. For example, window 1 708 is an active window and is displayed on only one of touch-sensitive displays 114. In the embodiment shown in FIG. 7A, device 100 is displaying window 1 708 with configuration 608 in the closed state 304. An inactive window is a window that has been opened and displayed, but is currently “behind” the active window and is not displayed. In an embodiment, the inactive window may be for an application that is paused, so the window is not displaying active content. For example, window 2 712 and window 3 716 are inactive windows.

  Window stack 700 may have a variety of configurations or organizational structures. In the embodiment shown in FIG. 7A, the device 100 is in the second portrait orientation 608 in the closed state 304, and the device 100 displays the first stack 704 associated with the first touch-sensitive display 114. Including. Thus, each touch-sensitive display 114 can have an associated window stack 704. In other embodiments, there is a single window stack that encompasses the entire composite display. A composite display is a logical structure that defines the entire display space including two touch sensitive displays 110,114. Device 100 may have a single stack for the composite display when the window or display object is resized to occupy part or all of the composite display. Thus, stack 704 can represent a portion of a larger composite window stack, and since device 100 is in a closed state 304, a portion of it is not shown.

  In FIG. 7B, the two window stacks (or two portions of the window stack) 704, 724 may have a different number of windows or display objects arranged in each stack 704, 724. Further, the two window stacks 704, 724 can be identified in different ways and managed separately. As shown in FIG. 7A, the first window stack 704 is from the first window 708 to the next window 712, to the last window 716, and finally to the desktop 720 (in the embodiment, “ It is possible to arrange them in order to “the bottom”. In an embodiment, an application window can be placed in a window stack below the desktop 720, and the desktop 720 is taken to the “top” of the stack on other windows during a desktop or other orientation change. The desktop 720 is not always “bottom” because it can come. For example, as shown in FIG. 7B, the device 100 is transitioned to the open state 320. Device 100 transitions to a display configuration as shown in FIG. 6C. Thus, the touch sensitive display 110 does not have a window associated with the touch sensitive display 110. Accordingly, the desktop 720 is displayed on the touch-sensitive display 110. Thus, the second stack 724 can include a desktop 720, which in the embodiment is a single desktop area, and the desktop 720 is below all windows in both the window stack 704 and the window stack 724. The logical data structure for managing a single window stack having two window stacks or two portions 704, 724 may be as described in conjunction with FIG.

  The configuration of the window stack 704 after opening the device is shown in FIGS. Window stack 704 is shown in three “solid” views. In FIG. 7C, the top surface of the window stack 704/724 is shown. Two adjacent sides of the window stack 704/724 are shown in FIGS. 7D and 7E. In this embodiment, the window stack 704/724 is similar to a brick stack. The windows are stacked on top of each other. FIG. 7C is viewing the window stack 704/724 from above, so that only the topmost window of the window stack 704/724 is visible in different parts of the composite display 728. FIG. The desktop 720 or window can occupy part or all of the composite display 728. FIG. 7C shows a composite display 728. Composite display 728 includes or includes the entire display area of touch-sensitive displays 110, 114. The size of the composite display 728 can be changed based on the orientation of the device 100. For example, the size of the composite display 728 of the device 100 in the closed state may include only one area of the touch-sensitive display 110 or 114, as shown in FIG. 7A. Composite display 728 is expanded to include both touch-sensitive displays 110, 114 when device 100 is opened, as shown in FIGS. 7B and 7C. Some windows or display objects are associated with the composite display 728, and when the dimensions of the composite display 728 change, the dimensions of the window or display object also change. In an embodiment, one such display object may be the desktop 720, and its dimensions may change as the device 100 is opened to occupy the entire composite display 728.

  In the embodiment shown, desktop 720 is the bottom display object, window or “brick” of window stack 704/724. From there, window 1 708, window 2 712, and window 3 716 are stacked. Window 1 708, window 2 712, and window 3 716 occupy only a portion of the composite display 728. Thus, another part of stack 724 includes only desktop 718. Only the top window or display object of any part of the composite display 728 is actually rendered and displayed. Thus, as shown in the top view of FIG. 7C, window 1 708 and desktop 718 are displayed by being on top of different portions of window stack 704/724. The window can be resized to occupy a small portion of the composite display 728 and “make visible” the windows below the window stack 704. For example, desktop 718 is below the window 1 708, window 2 712, and window 3 716 in the stack, but is still displayed. This configuration of windows and desktops occurs when the device is opened while displaying the top window of the window stack 704.

  Where and how the desktop 718 is placed in the stack depends on the orientation of the device 100, the context about which programs, functions, software, etc. are running on the device 100, and when the device 100 is opened It can depend on how the stack is arranged. Although the logical data structure associated with the desktop 718 or other window may not change when the device 100 is opened, the logical data structure can determine how to display the window and desktop. As the user interface or other event or task changes the arrangement of the stack, the logical structure of the window or desktop may be changed to reflect the change in arrangement.

  7F-7J illustrate another embodiment of a window stack configuration 724 that has been modified because the device has been opened from a different configuration than that of FIGS. In the embodiment shown in FIG. 7F, device 100 is in the closed state 304 and is displaying window 1 708 in configuration 608. Window 2 712 and window 3 716 are inactive windows. In the embodiment shown in FIG. 7F, the device 100 is in the first portrait configuration 604 in the closed state 304, and the device 100 opens the second stack 724 associated with the first touch-sensitive display 110. Including. Accordingly, touch-sensitive display 110 may have an associated window stack 724. In other embodiments, there is a single window stack that encompasses the entire composite display. Device 100 may have a single stack for the composite display when the window or display object is resized to occupy part or all of the composite display. Accordingly, stack 724 may represent a portion of a larger composite display stack, and device 100 is not shown because it is in a closed state 304.

  In FIG. 7G, the two window stacks (or two portions of the window stack) 704, 724 may have a different number of windows or display objects arranged in each stack 704, 724. Further, the two window stacks 704, 724 can be identified in different ways and managed separately. As shown in FIG. 7F, the second window stack 724 moves from the first window 708 to the next window 712, to the last window 716, and finally to the desktop 720 (in the embodiment, “ It is possible to arrange them in order to “the bottom”. In embodiments, application windows can be placed in a window stack below desktop 720, and desktop 720 can be brought to the “top” of the stack on other windows, such as during a change of direction. The desktop 720 is not always “bottom”. For example, as shown in FIG. 7G, the device 100 is moved to the open state 320. Device 100 transitions to a display configuration as shown in FIG. 6C. As such, the touch-sensitive display 114 does not have a window associated with the touch-sensitive display 114. Accordingly, the desktop 720 is displayed on the touch-sensitive display 114. Accordingly, the second stack 704 can include a desktop 720, which in the embodiment is a single desktop area, and the desktop 720 is below all windows in both the window stack 704 and the window stack 724. The logical data structure for managing a single window stack having two window stacks or two portions 704, 724 may be as described in conjunction with FIG.

  The configuration of the window stack 724 after opening the device is shown in FIGS. Window stack 704 is shown in three “solid” views. In FIG. 7H, the top surface of the window stack 704/724 is shown. Two adjacent “sides” of the window stack 704/724 are shown in FIGS. 7I and 7J. In this embodiment, the window stack 704/724 is similar to a brick stack. The windows are stacked on top of each other. FIG. 7H is viewing the window stack 704/724 from above, so that only the top window / display object of the window stack 704/724 is visible in different parts of the composite display 728. FIG. The desktop 720 or window can occupy part or all of the composite display 728.

  In the embodiment shown, desktop 720 is the bottom display object, window or “brick” of window stack 704/724. From there, window 1 708, window 2 712, and window 3 716 are stacked. Window 1 708, window 2 712, and window 3 716 occupy only a portion of the composite display 728. Thus, another part of stack 724 includes only desktop 718. Only the top window or display object of any part of the composite display 728 is actually rendered and displayed. Accordingly, window 1 708 and desktop 720 are displayed by being on top of different portions of window stack 704/724, as shown in the top view of FIG. 7H. The window can be resized to occupy a small portion of the composite display 728 and “make visible” the windows below the window stack 704. For example, desktop 718 is below the window 1 708, window 2 712, and window 3 716 in the stack, but is still displayed. This configuration of windows and desktops occurs when the device is opened while displaying the top window of the window stack 704.

  Where and how the desktop 718 is placed in the stack depends on the orientation of the device 100, the context about which programs, functions, software, etc. are running on the device 100, and when the device 100 is opened It can depend on how the stack is arranged. Although the logical data structure associated with the desktop 718 or other window may not change when the device 100 is opened, the logical data structure can determine how to display the window and desktop. As the user interface or other event or task changes the arrangement of the stack, the logical structure of the window or desktop may be changed to reflect the change in arrangement.

  A logical data structure 800 for managing the placement of windows or desktops in a window stack is shown in FIG. The logical data structure 800 can be any data structure used to store data, whether it is an object, a record, a file, or the like. The logical data structure 800 can be stored in any type of database or data storage system, regardless of protocol or standard. In an embodiment, the logical data structure 800 includes one or more portions, fields, attributes, etc. that store data in a logical configuration that allows easy storage and retrieval of information. In the following, one or more of these parts, fields, attributes, etc. will be described as simple fields. The field may store data for window identifier 804, dimension 808, stack position identifier 812, display identifier 816 and / or active indicator 820. Each window in the window stack may have an associated logical data structure 800. In FIG. 8, a single logical data structure 800 is shown, but there may be more or fewer logical data structures 800 used in the window stack, as represented by ellipse 824 (within the stack). Based on the number of windows or desktops). Further, as represented by ellipse 828, there may be more or fewer fields than those shown in FIG.

  Window identifier 804 may include any identifier (ID) that uniquely identifies the associated window or display object in relation to other windows or display objects in the window stack. Window identifier 804 may be a globally unique identifier (GUID), numeric ID, alphanumeric ID, or other type of identifier. In embodiments, the window identifier 804 may be 1 digit, 2 digits, or any number of digits based on the number of windows that can be opened. In an alternative embodiment, the size of the window identifier 804 may vary based on the number of open windows. While the window is open, the window identifier 804 may remain static and unchanged.

  The dimensions 808 may include the dimensions of the composite display 704 window or display object. For example, the dimension 808 may include coordinates of two or more corners of the window or display object, or may include dimensions for one coordinate and the width and height of the window or display object. These dimensions 808 can depict which portion of the composite display 704 a window or display object can occupy, which can be the entire composite display 704 or just a portion of the composite display 704. For example, window 1 708 may have a dimension 808 that indicates that window 1 708 occupies only a portion of the display area of composite display 728, as shown in FIGS. As the window is moved or inserted in the window stack, the dimension 808 can change.

  The stack position identifier 812 is any identifier that can identify the position of the window or display object in the stack, or can be deduced from the control record of the window in a data structure such as a list or stack. obtain. The stack location identifier 812 can be a GUID, numeric ID, alphanumeric ID, or other type of identifier. Each window or desktop may include a stack location identifier 812. For example, as shown in the embodiment of FIG. 7A, window 1 708 of stack 1 704 has a stack location identifier 812 that identifies window 708 as the first window of stack 704 and the active window. Can have. Similarly, window 2 712 may have two stack position identifiers 812 representing that window 2 712 is the second window of stack 704. Thus, depending on the type of stack, the stack position identifier 812 can represent the position of the window or display object within the stack.

  Display identifier 816 may identify that a window or display object is associated with a particular display, such as first display 110 or second display 114, or composite display 728 comprised of both displays. it can. As shown in FIG. 7A, this display identifier 816 may not be required in a multi-stack system, but display identifier 816 indicates whether a window or display object in the continuous stack of FIG. 7B is displayed on a particular display. Can indicate whether Accordingly, the desktop 720 may have two parts in FIG. 7C. The first portion may have a display identifier 816 for the first display 110, while the second portion may have a display identifier 816 for the second display 114. However, in an alternative embodiment, the desktop 720 may have a single display identifier 816 that indicates that the display identifier 816 has identified the composite display 728.

  Similar to the display identifier 816, the active indicator 820 may not be required in the dual stack system of FIG. 7A because the window or display object at stack position 1 is active and displayed. In an alternative embodiment, the active indicator 820 can indicate which window in the stack is being displayed. Thus, window 1 708 is shown and may have a single active indicator 820. The active indicator 820 may be a simple flag or bit that indicates that the window or display object is active or being displayed.

  An embodiment of a method 900 for creating a window stack is shown in FIG. In FIG. 9, the general order of the steps of the method 900 is shown. In general, the method 900 begins with a start operation 904 and ends with an end operation 924. The method 900 may include more or fewer steps than those shown in FIG. 9, or may order the steps in different ways. Method 900 is performed by a computer system and may be performed as a series of computer-executable instructions that are encoded or stored on a computer-readable medium. The method 900 is described below with reference to systems, components, modules, software, data structures, user interfaces, etc. described in conjunction with FIGS.

  As described in FIGS. 3A-3B, in step 908, the multi-screen device 100 can receive a change of direction, thereby changing the device 100 from the closed state 304 to the open state 320. Direction changes can be detected and signaled by hardware inputs from Hall effect sensors, timers, and the like. The direction change can be received by the task management module 540 and transmitted to the multiple display management module 524. The multiple display management module 524 interprets the change and either from the closed portrait display 604,608 to the open portrait display (as shown in FIG. 6C) or from the closed landscape display 612,616 to the open landscape configuration (FIG. 6F). As shown, the configuration of the display can be varied (as described in conjunction with FIGS. 6A-6F). In an embodiment, task management module 540 places user interface interactions in task stack 552 that is acted upon by multiple display management module 524. Further, the task management module 540 waits for information from the multiple display management module 524, sends an instruction to the window management module 532, and creates a window in the window stack 704.

  In step 912, upon receiving the instruction from the task management module 540, the multiple display management module 524 determines whether to specify the desktop 786. In an embodiment, desktop 786 may be at the bottom of window stack 704/724 before device 100 is opened. However, device 100 may display the last window of stack 704/724. In other words, the top window of stack 704/724 is displayed and no window can occupy the newly exposed display in the open state. For example, in FIG. 7A, there is no window on the “left side” of window 1 708. Therefore, the multiple display management module 524 needs to present the desktop 720 on the display 110 as shown in FIG. 7B. Since the desktop 720 generally extends across the composite display 728, the desktop 720 is always displayed on the opened device 100 unless another window covers the desktop 720. As shown in FIGS. 7B and 7F, since there is no window covering the desktop 720, the multiple display management module 524 decides to display the desktop 720 on the opened display.

  In an embodiment, the device status module 574 of the multiple display management module 524 may indicate how the device is oriented or in what state the device is in (eg, open state, closed state, portrait orientation, etc.). Can be determined. Further, at least one of the priority module 572 and the requirement module 580 can determine how to display the desktop 786 based on the priority of the desktop 786. The display configuration module 568 can then evaluate the current window stack 704/724 using input from at least one of the device status module 574, the priority module 572, and other framework components 520. . Since the other windows do not move, the desktop 720 shown in the new display typically does not affect the other windows in the window stack 704/724. However, the dimensions 808 of the desktop 720 may change as the desktop 720 is modified to occupy the entire composite display 728 and expands upon opening the device 100.

  The visibility algorithm, in an embodiment, determines which window / display object is at the top of the stack 704/724 for all parts of the composite display 728. For example, the visibility algorithm determines that the desktop 786 has been manifested in one part of the stack 704 since the device 100 has been opened, as seen in FIG. 7B or 7F. In addition, window 1 708 is displayed in the other part of stack 704 as seen in FIG. 7B or 7F. Having determined where to place desktop 720, display configuration module 568 can change at least one of display dimensions 808, display identifier 816, and stack location identifier 812 for desktop 720. Multiple display management module 524 may then return at least one of dimension 808, display identifier 816, and stack position identifier 812 to task management module 540.

  In an embodiment, task management module 540 sends at least one of dimensions 808, display identifier 816, stack position identifier 812, and other information and instructions to render desktop 786 to window management module 532. In step 920, the window management module 532 and the task management module 540 can change the logical data structure 800. Both task management module 540 and window management module 532 can manage a copy of window stack 704/724. These copies of the window stack 704/724 may be synchronized or similarly maintained through communication between the window management module 532 and the task management module 540. Accordingly, the window management module 532 and the task management module 540 are based on the information determined by the multiple display management module 524 and include the dimension 808, display identifier 816, and stack position identifier 812 for the desktop 720 and one or more windows. At least one of them can be changed. The logical data structure 800 can then be stored in both the window management module 532 and the task management module 540. Further, window management module 532 and task management module 540 can then manage window stack 704/724 and logical data structure 800.

  The exemplary systems and methods of this disclosure have been described in the context of window stacks associated with multiple screen devices. However, in order to avoid unnecessarily obscuring the present disclosure, many known structures and devices are omitted in the previous description. This omission should not be construed as limiting the scope of the claims. Specific details are set forth in order to provide an understanding of the present disclosure. However, it should be understood that the present disclosure can be implemented in a variety of ways beyond the specific details set forth herein.

  Moreover, although the exemplary aspects, embodiments, and / or configurations shown herein illustrate various components of a juxtaposed system, certain components of the system can be distributed networks such as a LAN and / or the Internet. Can be remotely located in a remote location or in a dedicated system. Thus, combining the components of the system into one or more devices such as the software modules of FIGS. 5A and 5 can also be distributed such as analog and / or digital telecommunications networks, packet switched networks, or circuit switched networks. It should be understood that they can be juxtaposed on a particular node of the network. From the previous description, it will be appreciated that for computational efficiency, the components of the system can be located anywhere in the distributed network of components without affecting the operation of the system. For example, the various components may be located in switches such as PBXs and media servers, gateways, in one or more communication devices, in one or more users' premises, or some combination thereof. it can. Similarly, one or more functional parts of the system can be distributed between a telecommunications device and an associated computing device.

  In addition, the various links connecting the elements can be wired links, wireless links, any combination thereof, and any other capable of supplying and / or communicating data to and from the connected elements. It should be understood that it can be any known or later developed element. These wired or wireless links can also be protected links and may be able to communicate encrypted information. The transmission medium used as the link can be any suitable electrical signal carrier including, for example, coaxial cables, copper wire and optical fiber, and can be a sound wave or light wave such as those generated during radio wave and infrared data communications. Can take shape.

  Also, although flowcharts have been discussed in the context of a particular sequence of events, changes, additions and omissions to this sequence may occur without substantially affecting the operation of the disclosed embodiments, configurations and aspects. Please understand that you get.

  Many variations and modifications of the disclosure can be used. It would also be possible to provide some features of the present disclosure without providing others. For example, in one variation, the window stack 700 is similar to a carousel or Rolodex rather than a set of playing cards. Thus, the window cycles from one touch-sensitive display 110 to another touch-sensitive display 114. For example, a window will be pushed to the right and will be at the end of the stack behind another window. If the stack continues to move to the right, the window that was opened on the first touch-sensitive display 110 will eventually appear on the second touch-sensitive display. These movements and changes in the stack are managed using the methods and logical data structures described above. In other embodiments, other arrangements for the window stack are possible.

  In yet another embodiment, the system and method of the present disclosure includes wired electronics such as a dedicated computer, programmed microprocessor or microcontroller and peripheral integrated circuit elements, ASICs or other integrated circuits, digital signal processors, discrete element circuits, etc. Alternatively, it can be implemented in conjunction with logic circuits, programmable logic devices or gate arrays such as PLD, PLA, FPGA, PAL, dedicated computers, any equivalent means, or the like. In general, any device or means capable of performing the methodologies described herein may be used to implement various aspects of the present disclosure. Exemplary hardware that can be used in the disclosed embodiments, configurations, and aspects include computers, portable devices, phones (eg, mobile phones, Internet capable, digital, analog, hybrid, and others), and Includes other hardware known in the art. Some of these devices include processors (eg, single or multiple microprocessors), memory, non-volatile storage, input devices, and output devices. Moreover, alternative software implementations including, but not limited to, distributed processing or component / object distributed processing, parallel processing, or virtual machine processing are constructed to implement the methods described herein. You can also.

  In yet another embodiment, the disclosed method is easily implemented in conjunction with software using an object or object-oriented software development environment that provides portable source code that can be used on a variety of computer or workstation platforms. be able to. Alternatively, the disclosed system can be partially or fully implemented in hardware using standard logic circuits or VLSI designs. Whether software or hardware is used to implement the system in accordance with this disclosure depends on the speed and / or efficiency requirements of the system, the particular functionality, and the particular software or hardware system or microprocessor or microcomputer system utilized. Dependent.

  In yet another embodiment, the disclosed method can be stored on a storage medium and executed on a general purpose computer, special purpose computer, microprocessor and the like programmed in cooperation with a controller and memory. Can be partially implemented in software. In these examples, the system and method of the present disclosure is dedicated as a resource that resides on a server or computer workstation as a program embedded in a personal computer such as an applet, JAVA, or CGI script. It can be implemented as a routine embedded in a measurement system, system component or the like. The system can also be implemented by physically incorporating the system and / or method into a software and / or hardware system.

  Although this disclosure describes components and functions implemented in aspects, embodiments and / or configurations with reference to specific standards and protocols, aspects, embodiments and / or configurations are not limited to such standards and protocols. Not limited to. Other similar standards and protocols not mentioned herein exist and are considered to be included in this disclosure. Moreover, the standards and protocols referred to herein and other similar standards and protocols not mentioned herein regularly take on faster or more effective equivalents having essentially the same functionality. Replaced. Such replacement standards and protocols having the same functions are considered equivalents included in this disclosure.

  The present disclosure in various aspects, embodiments and / or configurations includes substantially components, methods, processes, systems and / or apparatus as depicted and described herein, and various aspects, embodiments. , Configuration embodiments, sub-combinations and / or subsets thereof. Those skilled in the art will understand how to make and use the disclosed aspects, embodiments and / or configurations after understanding the present disclosure. The present disclosure in various aspects, embodiments, and / or configurations is without any items that are depicted and / or described herein, or with various aspects, embodiments, and / or configurations herein. Including providing devices and processes, such as may have been used in previous devices or processes, for example, to improve performance, facilitate implementation, and / or reduce implementation costs This includes cases where there are no major items.

  The foregoing discussion has been presented for purposes of illustration and description. The foregoing is not intended to limit the present disclosure to the form or forms disclosed herein. In the foregoing detailed description, various features of the present disclosure are grouped together in one or more aspects, embodiments and / or configurations, for example, for the purpose of streamlining the present disclosure. Features of aspects, embodiments and / or configurations of the present disclosure may be combined in alternative aspects, embodiments and / or configurations other than those discussed above. This method of disclosure is not to be interpreted as reflecting an intention that the claims require more features than are expressly recited in each claim. Rather, as the following claims reflect, aspects of the invention reside in less than all features of a single aforementioned disclosed aspect, embodiment and / or configuration. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate preferred embodiment of the disclosure.

  Moreover, the description includes descriptions of one or more aspects, embodiments and / or configurations, and certain variations and modifications, for example, after understanding the present disclosure, Other variations, combinations, and modifications are within the scope of this disclosure, as may be within the knowledge. Such alternative, interchangeable and / or equivalent structures, functions, ranges or steps are intended to obtain rights to include alternative aspects, embodiments and / or configurations of the permitted scope. Alternative, interchangeable and / or equivalent structures, functions to those claimed without the intention of publicly devoting any patentable subject matter, whether or not disclosed in Range or process.

Claims (9)

A device,
A composite display having a first portion and a second portion;
Memory,
A processor in communication with the memory and the composite display, the processor comprising:
Creating a first window stack logically associated with the first portion of the composite display, wherein the first window stack comprises one or more active windows, inactive windows, and the A data structure that represents the logical configuration of a desktop running on a device,
Displaying a first window at a logical top of the first window stack on the first portion of the composite display;
Receiving a change from a first state to a second state in the device;
In response to the change to the second state, a second window stack is created that is logically associated with the second portion of the composite display, where the second window stack is one Or a second data structure representing a second logical configuration of a plurality of active windows, inactive windows, and a desktop executing on the device;
Determining that a second window or desktop associated with the second window stack is displayed on the second portion of the composite display;
Determining that the second window is logically at the top of the second window stack;
The processor being operable to display the first window on the first portion of the composite display and to display the second window on the second portion of the composite display. device. The device of claim 1, wherein a first display includes the first portion of the composite display and a second display includes the second portion of the composite display. Each of the first and second window stacks includes:
A window identifier adapted to identify each window and desktop in relation to other windows and desktops in one of the first and second window stacks; and of the first and second window stacks The device of claim 1, comprising one or more of a window stack location identifier adapted to identify a logical location of each window or desktop in one of the. The device of claim 2, wherein the first and second displays are on a common first screen. The device of claim 4, wherein the first display is on a first screen and the second display is on another second screen. A method for presenting a window or desktop display for a device, comprising:
Creating a composite display having a first portion and a second portion;
Creating a first window stack logically associated with the first portion of the composite display, wherein the first window stack comprises one or more active windows, inactive windows, and the A data structure that represents the logical configuration of a desktop running on a device,
Displaying a first window at a logical top of the first window stack on the first portion of the composite display;
Receiving a transition from a first state to a second state in the device;
Creating a second window stack logically associated with the second portion of the composite display in response to the transition to the second state, wherein the second window stack is 1 A second data structure representing a second logical configuration of one or more active windows, inactive windows, and a desktop executing on the device;
Determining that a second window or desktop associated with the second window stack is displayed on the second portion of the composite display;
Determining that the second window is logically at the top of the second window stack;
Displaying the first window on the first portion of the composite display and displaying the first window on the second portion of the composite display. The desktop is logically at the bottom of the second window stack and is inactive, and the second window stack includes two or more other windows that are inactive, the desktop The method of claim 6, wherein the two or more windows are not displayed on the second portion of the composite display. The method of claim 7, wherein a first display includes the first portion of the composite display and a second display includes the second portion of the composite display. 9. The method of claim 8, wherein the first display is on a first screen and the second display is on another second screen.