U.S. patent application number 13/223039 was filed with the patent office on 2012-04-05 for handling gestures for changing focus.
Invention is credited to Ron Cassar, Martin Gimpl, Miroslaw (Mirek) Zaremski.
Application Number | 20120081303 13/223039 |
Document ID | / |
Family ID | 45889332 |
Filed Date | 2012-04-05 |
United States Patent
Application |
20120081303 |
Kind Code |
A1 |
Cassar; Ron ; et
al. |
April 5, 2012 |
HANDLING GESTURES FOR CHANGING FOCUS
Abstract
Embodiments are described for handling focus when a gesture is
input in a multi-screen device. In embodiments, if the gesture is
incomplete a focus is maintained on a screen, display area, or
displayed image that has the focus. If the gesture is determined to
be complete, then the focus is changed to a different screen,
display area, or displayed image.
Inventors: |
Cassar; Ron; (Burlington,
CA) ; Gimpl; Martin; (Helsinki, FI) ;
Zaremski; Miroslaw (Mirek); (Richmond Hill, CA) |
Family ID: |
45889332 |
Appl. No.: |
13/223039 |
Filed: |
August 31, 2011 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
61389000 |
Oct 1, 2010 |
|
|
|
61389117 |
Oct 1, 2010 |
|
|
|
61389087 |
Oct 1, 2010 |
|
|
|
Current U.S.
Class: |
345/173 |
Current CPC
Class: |
G06F 3/1423 20130101;
G06F 1/1616 20130101; G06F 3/0483 20130101; G06F 3/04847 20130101;
G06F 1/1641 20130101; G06F 3/0416 20130101; G06F 3/0481 20130101;
G06F 3/04886 20130101; G06F 1/1647 20130101; G06F 3/0482 20130101;
G06F 3/04845 20130101; G06F 3/04842 20130101; G06F 3/0488 20130101;
G06F 3/0486 20130101; G06F 3/04817 20130101; G06F 3/0412 20130101;
G06F 3/04883 20130101; G06F 3/017 20130101 |
Class at
Publication: |
345/173 |
International
Class: |
G06F 3/041 20060101
G06F003/041 |
Claims
1. A method, comprising: receiving, by at least one of a gesture
capture region and a touch sensitive display, a gesture indicating
a request to change focus; determining by at least one processor
whether the gesture is completed; and in response to the at least
one processor determining that the gesture is not completed,
maintaining a focus on a first screen that has the focus.
2. The method of claim 1, further comprising: in response to the at
least one processor determining that the gesture is completed,
changing the focus from the first screen to a second screen.
3. The method of claim 1, further comprising: in response to the
determining that the gesture is completed, further changing the
focus from a first image displayed on the first screen to a second
image displayed on a second screen.
4. The method of claim 3, further comprising: wherein the first
displayed image is a displayed window and the second displayed
image is a second window.
5. The method of claim 1, further comprising: receiving input
indicating that in response to an incomplete gesture, the focus
should be maintained on the screen with the focus.
6. The method of claim 1, further comprising: highlighting a
configurable area on the first screen when the focus is on the
screen; and highlighting a second configurable area on the second
screen when the focus is on the second screen.
7. The method of claim 1, further comprising: in response to
receiving the gesture, displaying at least one image displayed on
the first screen as moved from an original position.
8. The method of claim 7, in response to receiving the gesture,
displaying the at least one image as moved in a direction of the
gesture.
9. The method of claim 8, further comprising: in response to the
determining that the gesture is incomplete, displaying the at least
one image in the original position.
10. A non-transitory computer readable medium storing computer
executable instructions that when executed by at least one
processor perform a method comprising: receiving, by a gesture
capture region, a drag gesture indicating a request to change
focus; determining by at least one processor whether the drag
gesture is completed; in response to the at least one processor
determining that the drag gesture is not completed, maintaining a
focus on an image displayed on a first screen; and in response to
the at least one processor determining that the gesture is
completed, changing the focus from the first image to a second
image displayed on a second screen.
11. The non-transitory computer readable medium of claim 10,
wherein the method further comprises: in response to the at least
one processor determining that the drag gesture is not completed,
maintaining the lighting of a portion of a first configurable area
of the first screen and allowing input from the first configurable
area.
12. The non-transitory computer readable medium of claim 11,
wherein the method further comprises: allowing input from the first
configurable area.
13. The non-transitory computer readable medium of claim 10,
wherein the method further comprises: in response to the at least
one processor determining that the gesture is completed, darkening
the portion of the first configurable area of the first screen and
lighting up a portion of a second configurable area of the second
screen.
14. The non-transitory computer readable medium of claim 13,
wherein the method further comprises: allowing input from the
second configurable area; and not allowing input from the first
configurable area.
15. The non-transitory computer readable medium of claim 10,
wherein the method further comprises: receiving input indicating
that in response to an incomplete gesture, the focus should be
maintained on a displayed image with the focus.
16. The non-transitory computer readable medium of claim 10,
wherein the first displayed image is a first window and the second
displayed image is a second window.
17. A dual screen communication device, comprising: a gesture
capture region to receive a gesture; and a first touch sensitive
display; a second touch sensitive display; a computer readable
medium that stores computer executable instructions that when
executed by at least one processor perform a method comprising:
receiving, by one or more of the gesture capture region, the first
touch sensitive display, and the second touch display, a gesture
indicating a request to change focus; determining by at least one
processor whether the gesture is completed; and in response to the
at least one processor determining that the gesture is not
completed, maintaining a focus on the first touch sensitive
display.
18. The device of claim 17, wherein the method further comprises:
in response to the at least one processor determining that the
gesture is completed, changing the focus from the first touch
sensitive display to a second touch sensitive display.
19. The device of claim 17, wherein the method further comprises:
in response to the at least one processor determining that the drag
gesture is not completed, allowing input from the first touch
sensitive display and not allowing input from a portion of the
second touch sensitive display.
20. The device of claim 17, wherein the method further comprises:
in response to the at least one processor determining that the drag
gesture is completed, allowing input from the second touch
sensitive display and not allowing input from a portion of the
first touch sensitive display.
Description
CROSS REFERENCE TO RELATED APPLICATION
[0001] The present application claims the benefits of and priority,
under 35 U.S.C. .sctn.119(e), to U.S. Provisional Application Ser.
No. 61/389,000, filed Oct. 1, 2010, entitled "DUAL DISPLAY
WINDOWING SYSTEM;" 61/389,117, filed Oct. 1, 2010, entitled
"MULTI-OPERATING SYSTEM PORTABLE DOCKETING DEVICE;" 61/389,087,
filed Oct. 1, 2010, entitled "TABLET COMPUTING USER INTERFACE."
Each of the aforementioned documents is incorporated herein by this
reference in their entirety for all that they teach and for all
purposes.
BACKGROUND
[0002] A substantial number of handheld computing devices, such as
cellular phones, tablets, and E-Readers, make use of a touch screen
display not only to deliver display information to the user but
also to receive inputs from user interface commands. While touch
screen displays may increase the configurability of the handheld
device and provide a wide variety of user interface options, this
flexibility typically comes at a price. The dual use of the touch
screen to provide content and receive user commands, while flexible
for the user, may obfuscate the display and cause visual clutter,
thereby leading to user frustration and loss of productivity.
[0003] The small form factor of handheld computing devices requires
a careful balancing between the displayed graphics and the area
provided for receiving inputs. On the one hand, the small display
constrains the display space, which may increase the difficulty of
interpreting actions or results. On the other, a virtual keypad or
other user interface scheme is superimposed on or positioned
adjacent to an executing application, requiring the application to
be squeezed into an even smaller portion of the display.
[0004] This balancing act is particularly difficult for single
display touch screen devices. Single display touch screen devices
are crippled by their limited screen space. When users are entering
information into the device, through the single display, the
ability to interpret information in the display can be severely
hampered, particularly when a complex interaction between display
and interface is required.
SUMMARY
[0005] There is a need for a dual multi-display handheld computing
device that provides for enhanced power and/or versatility compared
to conventional single display handheld computing devices. These
and other needs are addressed by the various aspects, embodiments,
and/or configurations of the present disclosure. Also, while the
disclosure is presented in terms of exemplary embodiments, it
should be appreciated that individual aspects of the disclosure can
be separately claimed.
[0006] In one embodiment, a method includes receiving, by at least
one of a gesture capture region and a touch sensitive display, a
gesture indicating a request to change focus. A determination is
made by at least one processor whether the gesture is completed. In
response to the at least one processor determining that the gesture
is not completed, a focus is maintained on a first screen that has
the focus.
[0007] Another embodiment is directed to a non-transitory computer
readable medium storing computer executable instructions that when
executed by at least one processor perform a method that includes
receiving, by a gesture capture region, a drag gesture indicating a
request to change focus. A determination is made whether the drag
gesture is completed. If a determination is made that the drag
gesture is not completed a focus is maintained on an image
displayed on a first screen. If a determination is made that the
gesture is completed, the focus is changed from the first image to
a second image displayed on a second screen.
[0008] Yet another embodiment is directed to a dual screen
communication device. The communication device includes a gesture
capture region to receive a gesture, a first touch sensitive
display; a second touch sensitive display; and a computer readable
medium that stores computer executable instructions that when
executed by at least one processor perform a method that includes
receiving, by at least one of the gesture capture region, the first
touch sensitive display, or the second touch sensitive display, a
gesture indicating a request to change focus. A determination is
then made whether the gesture is completed. If a determination is
made that the gesture is not completed, a focus is maintained on a
first touch sensitive display.
[0009] The present disclosure can provide a number of advantages
depending on the particular aspect, embodiment, and/or
configuration. In a device that includes more than one screen, a
decision must be made by the device as to what screen, display
area, or displayed image has the focus. This decision must be made
so that any input received by a user can be associated with a
screen, display area, or displayed image. In embodiments, only when
gestures are completed is the focus changed to another screen,
display area, or displayed image. This solves the problem of the
device needing to decide whether to change focus when it receives a
gesture that is not complete. These and other advantages will be
apparent from the disclosure.
[0010] The phrases "at least one", "one or more", and "and/or" are
open-ended expressions that are both conjunctive and disjunctive in
operation. For example, each of the expressions "at least one of A,
B and C", "at least one of A, B, or C", "one or more of A, B, and
C", "one or more of A, B, or C" and "A, B, and/or C" means A alone,
B alone, C alone, A and B together, A and C together, B and C
together, or A, B and C together.
[0011] The term "a" or "an" entity refers to one or more of that
entity. As such, the terms "a" (or "an"), "one or more" and "at
least one" can be used interchangeably herein. It is also to be
noted that the terms "comprising", "including", and "having" can be
used interchangeably.
[0012] The term "automatic" and variations thereof, as used herein,
refers to any process or operation done without material human
input when the process or operation is performed. However, a
process or operation can be automatic, even though performance of
the process or operation uses material or immaterial human input,
if the input is received before performance of the process or
operation. Human input is deemed to be material if such input
influences how the process or operation will be performed. Human
input that consents to the performance of the process or operation
is not deemed to be "material".
[0013] The term "computer-readable medium" as used herein refers to
any tangible storage and/or transmission medium that participate 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, a floppy
disk, a flexible disk, hard disk, magnetic tape, or any other
magnetic medium, magneto-optical medium, a CD-ROM, any other
optical medium, punch cards, paper tape, any other physical medium
with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, a
solid state medium like a memory card, any other memory chip or
cartridge, a carrier wave as described hereinafter, or any other
medium from which a computer can read. A digital file attachment to
e-mail or other self-contained information archive or set of
archives is considered a distribution medium equivalent to a
tangible storage medium. When the computer-readable media is
configured as a database, it is to be understood that the database
may be any type of database, such as relational, hierarchical,
object-oriented, and/or the like. Accordingly, the disclosure is
considered to include a tangible storage medium or distribution
medium and prior art-recognized equivalents and successor media, in
which the software implementations of the present disclosure are
stored.
[0014] The term "desktop" refers to a metaphor used to portray
systems. A desktop is generally considered a "surface" that
typically includes pictures, called icons, widgets, folders, etc.
that can activate show applications, windows, cabinets, files,
folders, documents, and other graphical items. The icons are
generally selectable to initiate a task through user interface
interaction to allow a user to execute applications or conduct
other operations.
[0015] The term "display" refers to a portion of a screen used to
display the output of a computer to a user.
[0016] The term "displayed image" refers to an image produced on
the display. A typical displayed image is a window or desktop. The
displayed image may occupy all or a portion of the display.
[0017] The term "display orientation" refers to the way in which a
rectangular display is oriented by a user for viewing. The two most
common types of display orientation are portrait and landscape. In
landscape mode, the display is oriented such that the width of the
display is greater than the height of the display (such as a 4:3
ratio, which is 4 units wide and 3 units tall, or a 16:9 ratio,
which is 16 units wide and 9 units tall). Stated differently, the
longer dimension of the display is oriented substantially
horizontal in landscape mode while the shorter dimension of the
display is oriented substantially vertical. In the portrait mode,
by contrast, the display is oriented such that the width of the
display is less than the height of the display. Stated differently,
the shorter dimension of the display is oriented substantially
horizontal in the portrait mode while the longer dimension of the
display is oriented substantially vertical. The multi-screen
display can have one composite display that encompasses all the
screens. The composite display can have different display
characteristics based on the various orientations of the
device.
[0018] The term "gesture" refers to a user action that expresses an
intended idea, action, meaning, result, and/or outcome. The user
action can include manipulating a device (e.g., opening or closing
a device, changing a device orientation, moving a trackball or
wheel, etc.), movement of a body part in relation to the device,
movement of an implement or tool in relation to the device, audio
inputs, etc. A gesture may be made on a device (such as on the
screen) or with the device to interact with the device.
[0019] The term "module" as used herein refers to any known or
later developed hardware, software, firmware, artificial
intelligence, fuzzy logic, or combination of hardware and software
that is capable of performing the functionality associated with
that element.
[0020] The term "gesture capture" refers to a sense or otherwise a
detection of an instance and/or type of user gesture. The gesture
capture can occur in one or more areas of the screen, A gesture
region can be on the display, where it may be referred to as a
touch sensitive display or off the display where it may be referred
to as a gesture capture area.
[0021] A "multi-screen application" refers to an application that
is capable of producing one or more windows that may simultaneously
occupy multiple screens. A multi-screen application commonly can
operate in single-screen mode in which one or more windows of the
application are displayed only on one screen or in multi-screen
mode in which one or more windows are displayed simultaneously on
multiple screens.
[0022] A "single-screen application" refers to an application that
is capable of producing one or more windows that may occupy only a
single screen at a time.
[0023] The term "screen," "touch screen," or "touchscreen" refers
to a physical structure that enables the user to interact with the
computer by touching areas on the screen and provides information
to a user through a display. The touch screen may sense user
contact in a number of different ways, such as by a change in an
electrical parameter (e.g., resistance or capacitance), acoustic
wave variations, infrared radiation proximity detection, light
variation detection, and the like. In a resistive touch screen, for
example, normally separated conductive and resistive metallic
layers in the screen pass an electrical current. When a user
touches the screen, the two layers make contact in the contacted
location, whereby a change in electrical field is noted and the
coordinates of the contacted location calculated. In a capacitive
touch screen, a capacitive layer stores electrical charge, which is
discharged to the user upon contact with the touch screen, causing
a decrease in the charge of the capacitive layer. The decrease is
measured, and the contacted location coordinates determined. In a
surface acoustic wave touch screen, an acoustic wave is transmitted
through the screen, and the acoustic wave is disturbed by user
contact. A receiving transducer detects the user contact instance
and determines the contacted location coordinates.
[0024] The term "window" refers to a, typically rectangular,
displayed image on at least part of a display that contains or
provides content different from the rest of the screen. The window
may obscure the desktop.
[0025] The terms "determine", "calculate" and "compute," and
variations thereof, as used herein, are used interchangeably and
include any type of methodology, process, mathematical operation or
technique.
[0026] The term "focus" refers to being active and/or selected to
receive input. A screen, a display, or a component (e.g., displayed
image) of a displayed graphical user interface may have the
"focus."
[0027] It shall be understood that the term "means" as used herein
shall be given its broadest possible interpretation in accordance
with 35 U.S.C., Section 112, Paragraph 6. Accordingly, a claim
incorporating the term "means" shall cover all structures,
materials, or acts set forth herein, and all of the equivalents
thereof. Further, the structures, materials or acts and the
equivalents thereof shall include all those described in the
summary of the invention, brief description of the drawings,
detailed description, abstract, and claims themselves.
[0028] The preceding is a simplified summary of the disclosure to
provide an understanding of some aspects of the disclosure. This
summary is neither an extensive nor exhaustive overview of the
disclosure and its various aspects, embodiments, and/or
configurations. It is intended neither to identify key or critical
elements of the disclosure nor to delineate the scope of the
disclosure but to present selected concepts of the disclosure in a
simplified form as an introduction to the more detailed description
presented below. As will be appreciated, other aspects,
embodiments, and/or configurations of the disclosure are possible
utilizing, alone or in combination, one or more of the features set
forth above or described in detail below.
BRIEF DESCRIPTION OF THE DRAWINGS
[0029] FIG. 1A includes a first view of an embodiment of a
multi-screen user device;
[0030] FIG. 1B includes a second view of an embodiment of a
multi-screen user device;
[0031] FIG. 1C includes a third view of an embodiment of a
multi-screen user device;
[0032] FIG. 1D includes a fourth view of an embodiment of a
multi-screen user device;
[0033] FIG. 1E includes a fifth view of an embodiment of a
multi-screen user device;
[0034] FIG. 1F includes a sixth view of an embodiment of a
multi-screen user device;
[0035] FIG. 1G includes a seventh view of an embodiment of a
multi-screen user device;
[0036] FIG. 1H includes a eighth view of an embodiment of a
multi-screen user device;
[0037] FIG. 1I includes a ninth view of an embodiment of a
multi-screen user device;
[0038] FIG. 1J includes a tenth view of an embodiment of a
multi-screen user device;
[0039] FIG. 2 is a block diagram of an embodiment of the hardware
of the device;
[0040] FIG. 3A is a block diagram of an embodiment of the state
model for the device based on the device's orientation and/or
configuration;
[0041] FIG. 3B is a table of an embodiment of the state model for
the device based on the device's orientation and/or
configuration;
[0042] FIG. 4A is a first representation of an embodiment of user
gesture received at a device;
[0043] FIG. 4B is a second representation of an embodiment of user
gesture received at a device;
[0044] FIG. 4C is a third representation of an embodiment of user
gesture received at a device;
[0045] FIG. 4D is a fourth representation of an embodiment of user
gesture received at a device;
[0046] FIG. 4E is a fifth representation of an embodiment of user
gesture received at a device;
[0047] FIG. 4F is a sixth representation of an embodiment of user
gesture received at a device;
[0048] FIG. 4G is a seventh representation of an embodiment of user
gesture received at a device;
[0049] FIG. 4H is a eighth representation of an embodiment of user
gesture received at a device;
[0050] FIG. 5A is a block diagram of an embodiment of the device
software and/or firmware;
[0051] FIG. 5B is a second block diagram of an embodiment of the
device software and/or firmware;
[0052] FIG. 6A is a first representation of an embodiment of a
device configuration generated in response to the device state;
[0053] FIG. 6B is a second representation of an embodiment of a
device configuration generated in response to the device state;
[0054] FIG. 6C is a third representation of an embodiment of a
device configuration generated in response to the device state;
[0055] FIG. 6D is a fourth representation of an embodiment of a
device configuration generated in response to the device state;
[0056] FIG. 6E is a fifth representation of an embodiment of a
device configuration generated in response to the device state;
[0057] FIG. 6F is a sixth representation of an embodiment of a
device configuration generated in response to the device state;
[0058] FIG. 6G is a seventh representation of an embodiment of a
device configuration generated in response to the device state;
[0059] FIG. 6H is a eighth representation of an embodiment of a
device configuration generated in response to the device state;
[0060] FIG. 6I is a ninth representation of an embodiment of a
device configuration generated in response to the device state;
[0061] FIG. 6J is a tenth representation of an embodiment of a
device configuration generated in response to the device state;
[0062] FIGS. 7A-7C are a representation of an embodiment showing a
first screen that has a focus and the response when an incomplete
gesture is made;
[0063] FIGS. 8A-8C are a representation of a second embodiment
showing a first screen and an image displayed on the first screen
that have a focus and the response when an incomplete gesture is
made;
[0064] FIGS. 9A-9C are a representation of an embodiment showing a
first screen and an image displayed on the first screen that have a
focus and the response when a complete gesture is made; and
[0065] FIG. 10 illustrates a flow chart of an embodiment for
handling a gesture.
[0066] In the appended figures, similar components and/or features
may have the same reference label. Further, various components of
the same type may be distinguished by following the reference label
by a letter that distinguishes among the similar components. If
only the first reference label is used in the specification, the
description is applicable to any one of the similar components
having the same first reference label irrespective of the second
reference label.
DETAILED DESCRIPTION
[0067] Presented herein are embodiments of a device. The device can
be a communications device, such as a cellular telephone, or other
smart device. The device can include two screens that are oriented
to provide several unique display configurations. Further, the
device can receive user input in unique ways. The overall design
and functionality of the device provides for an enhanced user
experience making the device more useful and more efficient.
[0068] Mechanical Features:
[0069] FIGS. 1A-1J illustrate a device 100 in accordance with
embodiments of the present disclosure. As described in greater
detail below, device 100 can be positioned in a number of different
ways each of which provides different functionality to a user. The
device 100 is a multi-screen device that includes a primary screen
104 and a secondary screen 108, both of which are touch sensitive.
In embodiments, the entire front surface of screens 104 and 108 may
be touch sensitive and capable of receiving input by a user
touching the front surface of the screens 104 and 108. Primary
screen 104 includes touch sensitive display 110, which, in addition
to being touch sensitive, also displays information to a user.
Secondary screen 108 includes touch sensitive display 114, which
also displays information to a user. In other embodiments, screens
104 and 108 may include more than one display area.
[0070] Primary screen 104 also includes a configurable area 112
that has been configured for specific inputs when the user touches
portions of the configurable area 112. Secondary screen 108 also
includes a configurable area 116 that has been configured for
specific inputs. Areas 112a and 116a have been configured to
receive a "back" input indicating that a user would like to view
information previously displayed. Areas 112b and 116b have been
configured to receive a "menu" input indicating that the user would
like to view options from a menu. Areas 112c and 116c have been
configured to receive a "home" input indicating that the user would
like to view information associated with a "home" view. In other
embodiments, areas 112a-c and 116a-c may be configured, in addition
to the configurations described above, for other types of specific
inputs including controlling features of device 100, some
non-limiting examples including adjusting overall system power,
adjusting the volume, adjusting the brightness, adjusting the
vibration, selecting of displayed items (on either of screen 104 or
108), operating a camera, operating a microphone, and
initiating/terminating of telephone calls. Also, in some
embodiments, areas 112a-C and 116a-C may be configured for specific
inputs depending upon the application running on device 100 and/or
information displayed on touch sensitive displays 110 and/or
114.
[0071] In addition to touch sensing, primary screen 104 and
secondary screen 108 may also include areas that receive input from
a user without requiring the user to touch the display area of the
screen. For example, primary screen 104 includes gesture capture
area 120, and secondary screen 108 includes gesture capture area
124. These areas are able to receive input by recognizing gestures
made by a user without the need for the user to actually touch the
surface of the display area. In comparison to touch sensitive
displays 110 and 114, the gesture capture areas 120 and 124 are
commonly not capable of rendering a displayed image.
[0072] The two screens 104 and 108 are connected together with a
hinge 128, shown clearly in FIG. 1C (illustrating a back view of
device 100). Hinge 128, in the embodiment shown in FIGS. 1A-1J, is
a center hinge that connects screens 104 and 108 so that when the
hinge is closed, screens 104 and 108 are juxtaposed (i.e.,
side-by-side) as shown in FIG. 1B (illustrating a front view of
device 100). Hinge 128 can be opened to position the two screens
104 and 108 in different relative positions to each other. As
described in greater detail below, the device 100 may have
different functionalities depending on the relative positions of
screens 104 and 108.
[0073] FIG. 1D illustrates the right side of device 100. As shown
in FIG. 1D, secondary screen 108 also includes a card slot 132 and
a port 136 on its side. Card slot 132 in embodiments, accommodates
different types of cards including a subscriber identity module
(SIM). Port 136 in embodiments 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 merely some examples and in other
embodiments device 100 may include other slots and ports such as
slots and ports for accommodating additional memory devices and/or
for connecting other peripheral devices. Also shown in FIG. 1D is
an audio jack 140 that accommodates a tip, ring, sleeve (TRS)
connector for example to allow a user to utilize headphones or a
headset.
[0074] Device 100 also includes a number of buttons 158. For
example, FIG. 1E illustrates the left side of 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, buttons 144, 148, and 152 may be configured to, in
combination or alone, control a number of aspects of device 100.
Some non-limiting examples include overall system power, volume,
brightness, vibration, selection of displayed items (on either of
screen 104 or 108), a camera, a microphone, and
initiation/termination of telephone calls. In some embodiments,
instead of separate buttons two buttons may be combined into a
rocker button. This arrangement is useful in situations where the
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, shown in FIG. 1F, which illustrates the
top of device 100. In one embodiment, button 156 is configured as
an on/off button used to control overall system power to device
100. In other embodiments, button 156 is configured to, in addition
to or in lieu of controlling system power, control other aspects of
device 100. In some embodiments, one or more of the buttons 144,
148, 152, and 156 are capable of supporting different user
commands. By way of example, a normal press has a duration commonly
of less than about 1 second and resembles a quick tap. A medium
press has a duration commonly of 1 second or more but less than
about 12 seconds. A long press has a duration commonly of about 12
seconds or more. The function of the buttons is normally specific
to the application that is currently in focus on the respective
display 110 and 114. In a telephone application for instance and
depending on the particular button, a normal, medium, or long press
can mean end call, increase in call volume, decrease in call
volume, and toggle microphone mute. In a camera or video
application for instance and depending on the particular button, a
normal, medium, or long press can mean increase zoom, decrease
zoom, and take photograph or record video.
[0075] There are also a number of hardware components within device
100. As illustrated in FIG. 1C, device 100 includes a speaker 160
and a microphone 164. Device 100 also includes a camera 168 (FIG.
1B). Additionally, device 100 includes two position sensors 172A
and 172B, which are used to determine the relative positions of
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 in lieu of the Hall effect
sensors. An accelerometer 176 may also be included as part of
device 100 to determine the orientation of the device 100 and/or
the orientation of screens 104 and 108. Additional internal
hardware components that may be included in device 100 are
described below with respect to FIG. 2.
[0076] The overall design of device 100 allows it to provide
additional functionality not available in other communication
devices. Some of the functionality is based on the various
positions and orientations that device 100 can have. As shown in
FIGS. 1B-1G, device 100 can be operated in an "open" position where
screens 104 and 108 are juxtaposed. This position allows a large
display area for displaying information to a user. When position
sensors 172A and 172B determine that device 100 is in the open
position, they can generate a signal that can be used to trigger
different events such as displaying information on both screens 104
and 108. Additional events may be triggered if accelerometer 176
determines that device 100 is in a portrait position (FIG. 1B) as
opposed to a landscape position (not shown).
[0077] In addition to the open position, device 100 may also have a
"closed" position illustrated in FIG. 1H. Again, position sensors
172A and 172B can generate a signal indicating that device 100 is
in the "closed" position. This can trigger an event that results in
a change of displayed information on screen 104 and/or 108. For
example, device 100 may be programmed to stop displaying
information on one of the screens, e.g., screen 108, since a user
can only view one screen at a time when device 100 is in the
"closed" position. In other embodiments, the signal generated by
position sensors 172A and 172B, indicating that the device 100 is
in the "closed" position, can trigger device 100 to answer an
incoming telephone call. The "closed" position can also be a
preferred position for utilizing the device 100 as a mobile
phone.
[0078] Device 100 can also be used in an "easel" position which is
illustrated in FIG. 1I. In the "easel" position, screens 104 and
108 are angled with respect to each other and facing outward with
the edges of screens 104 and 108 substantially horizontal. In this
position, device 100 can be configured to display information on
both screens 104 and 108 to allow two users to simultaneously
interact with device 100. When device 100 is in the "easel"
position, sensors 172A and 172B generate a signal indicating that
the screens 104 and 108 are positioned at an angle to each other,
and the accelerometer 176 can generate a signal indicating that
device 100 has been placed so that the edge of screens 104 and 108
are substantially horizontal. The signals can then be used in
combination to generate events that trigger changes in the display
of information on screens 104 and 108.
[0079] FIG. 1J illustrates device 100 in a "modified easel"
position. In the "modified easel" position, one of screens 104 or
108 is used as a stand and is faced down on the surface of an
object such as a table. This position provides a convenient way for
information to be displayed to a user in landscape orientation.
Similar to the easel position, when device 100 is in the "modified
easel" position, position sensors 172A and 172B generate a signal
indicating that the screens 104 and 108 are positioned at an angle
to each other. The accelerometer 176 would generate a signal
indicating that device 100 has been positioned so that one of
screens 104 and 108 is faced downwardly and is substantially
horizontal. The signals can then be used to generate events that
trigger changes in the display of information of screens 104 and
108. For example, information may not be displayed on the screen
that is face down since a user cannot see the screen.
[0080] Transitional states are also possible. When the position
sensors 172A and B and/or accelerometer indicate that the screens
are being closed or folded (from open), a closing transitional
state is recognized. Conversely when the position sensors 172A and
B indicate that the screens are being opened or folded (from
closed), an opening transitional state is recognized. The closing
and opening transitional states are typically time-based, or have a
maximum time duration from a sensed starting point. Normally, no
user input is possible when one of the closing and opening states
is in effect. In this manner, incidental user contact with a screen
during the closing or opening function is not misinterpreted as
user input. In embodiments, another transitional state is possible
when the device 100 is closed. This additional transitional state
allows the display to switch from one screen 104 to the second
screen 108 when the device 100 is closed based on some user input,
e.g., a double tap on the screen 110,114.
[0081] As can be appreciated, the description of device 100 is made
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, device 100 may include
additional features, including one or more additional buttons,
slots, display areas, hinges, and/or locking mechanisms.
Additionally, in embodiments, the features described above may be
located in different parts of device 100 and still provide similar
functionality. Therefore, FIGS. 1A-1J and the description provided
above are nonlimiting.
[0082] Hardware Features:
[0083] FIG. 2 illustrates components of a device 100 in accordance
with embodiments of the present disclosure. In general, the device
100 includes a primary screen 104 and a secondary screen 108. While
the primary screen 104 and its components are normally enabled in
both the opened and closed positions or states, the secondary
screen 108 and its components are normally enabled in the opened
state but disabled in the closed state. However, even when in the
closed state a user or application triggered interrupt (such as in
response to a phone application or camera application operation)
can flip the active screen, or disable the primary screen 104 and
enable the secondary screen 108, by a suitable command. Each screen
104, 108 can be touch sensitive and can include different operative
areas. For example, a first operative area may comprise a touch
sensitive display 110. In general, the touch sensitive display 110
may comprise a full color, touch sensitive display. A second area
within each touch sensitive screen 104 and 108 may comprise a
gesture capture region 120, 124. The gesture capture region 120,
124 may comprise an area or region that is outside of the touch
sensitive display 110 area, and that is capable of receiving input,
for example in the form of gestures provided by a user. However,
the gesture capture region 120, 124 does not include pixels that
can perform a display function or capability.
[0084] A third region of the touch sensitive screens 104 and 108
may comprise a configurable area 112, 116. The configurable area
112, 116 is capable of receiving input and has display or limited
display capabilities. In embodiments, the configurable area 112,
116 may present different input options to the user. For example,
the configurable area 112, 116 may display buttons or other
relatable items. Moreover, the identity of displayed buttons, or
whether any buttons are displayed at all within the configurable
area 112, 116 of a touch sensitive screen 104 or 108, may be
determined from the context in which the device 100 is used and/or
operated. In an exemplary embodiment, the touch sensitive screens
104 and 108 comprise liquid crystal display devices extending
across at least those regions of the touch sensitive screens 104
and 108 that are capable of providing visual output to a user, and
a capacitive input matrix over those regions of the touch sensitive
screens 104 and 108 that are capable of receiving input from the
user.
[0085] One or more display controllers 216a, 216b may be provided
for controlling the operation of the touch sensitive screens 104
and 108, including input (touch sensing) and output (display)
functions. In the exemplary embodiment illustrated in FIG. 2, a
separate touch screen controller 216a or 216b is provided for each
touch screens 104 and 108. In accordance with alternate
embodiments, a common or shared touch screen controller 216 may be
used to control each of the included touch sensitive screens 104
and 108. In accordance with still other embodiments, the functions
of a touch screen controller 216 may be incorporated into other
components, such as a processor 204.
[0086] The processor 204 may comprise a general purpose
programmable processor or controller for executing application
programming or instructions. In accordance with at least some
embodiments, the processor 204 may include multiple processor
cores, and/or implement multiple virtual processors. In accordance
with still other embodiments, the processor 204 may include
multiple physical processors. As a particular example, the
processor 110 may comprise a specially configured application
specific integrated circuit (ASIC) or other integrated circuit, a
digital signal processor, a controller, a hardwired electronic or
logic circuit, a programmable logic device or gate array, a special
purpose computer, or the like. The processor 110 generally
functions to run programming code or instructions implementing
various functions of the device 100.
[0087] A communication device 100 may also include memory 208 for
use in connection with the execution of application programming or
instructions by the processor 204, and for the temporary or long
term storage of program instructions and/or data. As examples, the
memory 208 may comprise RAM, DRAM, SDRAM, or other solid state
memory. Alternatively or in addition, data storage 212 may be
provided. Like the memory 208, the data storage 212 may comprise a
solid state memory device or devices. Alternatively or in addition,
the data storage 212 may comprise a hard disk drive or other random
access memory.
[0088] In support of communications functions or capabilities, the
device 100 can include a cellular telephony module 228. As
examples, the cellular telephony module 228 can comprise a GSM,
CDMA, FDMA and/or analog cellular telephony transceiver capable of
supporting voice, multimedia and/or data transfers over a cellular
network. Alternatively or in addition, the device 100 can include
an additional or other wireless communications module 232. As
examples, the other wireless communications module 236 can comprise
a Wi-Fi, Bluetooth, WiMax, infrared, or other wireless
communications link. The cellular telephony module 228 and the
other wireless communications module 236 can each be associated
with a shared or a dedicated antenna 224.
[0089] A port interface 244 may be included. The port interface 244
may include proprietary or universal ports to support the
interconnection of the device 100 to other devices or components,
such as a dock, which may or may not include additional or
different capabilities from those integral to the device 100. In
addition to supporting an exchange of communication signals between
the device 100 and another device or component, the docking port
244 can support the supply of power to or from the device 100. The
port interface 244 also comprises an intelligent element that
comprises a docking module for controlling communications or other
interactions between the device 100 and a connected device or
component.
[0090] An input/output module 248 and associated ports may be
included to support communications over wired networks or links,
for example with other communication devices, server devices,
and/or peripheral devices. Examples of an input/output module 248
include an Ethernet port, a USB port, IEEE 1394, or other
interface.
[0091] An audio input/output interface/device(s) 240 can be
included to provide analog audio to an interconnected speaker or
other device, and to receive analog audio input from a connected
microphone or other device. As an example, the audio input/output
interface/device(s) 240 may comprise an associated amplifier and
analog to digital converter. Alternatively or in addition, the
device 100 can include an integrated audio input/output device 256
and/or an audio jack for interconnecting an external speaker or
microphone. For example, an integrated speaker and an integrated
microphone can be provided, to support near talk or speaker phone
operations.
[0092] Hardware buttons 260 can be included for example for use in
connection with certain control operations. Examples include a
master power switch, volume control, etc., as described in
conjunction with FIGS. 1A through 1J. One or more image capture
interfaces/devices 240, such as a camera, can be included for
capturing still and/or video images. Alternatively or in addition,
an image capture interface/device 240 can include a scanner or code
reader. An image capture interface/device 240 can include or be
associated with additional elements, such as a flash or other light
source.
[0093] The device 100 can also include a global positioning system
(GPS) receiver 236. In accordance with embodiments of the present
invention, the GPS receiver 236 may further comprise a GPS module
that is capable of providing absolute location information to other
components of the device 100. An accelerometer(s) 176 may also be
included. For example, in connection with the display of
information to a user and/or other functions, a signal from the
accelerometer 176 can be used to determine an orientation and/or
format in which to display that information to the user.
[0094] Embodiments of the present invention can also include one or
more position sensor(s) 172. The position sensor 172 can provide a
signal indicating the position of the touch sensitive screens 104
and 108 relative to one another. This information can be provided
as an input, for example to a user interface application, to
determine an operating mode, characteristics of the touch sensitive
displays 110, 114, and/or other device 100 operations. As examples,
a screen position sensor 172 can comprise a series of Hall effect
sensors, a multiple position switch, an optical switch, a
Wheatstone bridge, a potentiometer, or other arrangement capable of
providing a signal indicating of multiple relative positions the
touch screens are in.
[0095] Communications between various components of the device 100
can be carried by one or more buses 222. In addition, power can be
supplied to the components of the device 100 from a power source
and/or power control module 260. The power control module 260 can,
for example, include a battery, an AC to DC converter, power
control logic, and/or ports for interconnecting the device 100 to
an external source of power.
[0096] Device State:
[0097] FIGS. 3A and 3B represent illustrative states of device 100.
While a number of illustrative states are shown, and transitions
from a first state to a second state, it is to be appreciated that
the illustrative state diagram may not encompass all possible
states and/or all possible transitions from a first state to a
second state. As illustrated in FIG. 3, the various arrows between
the states (illustrated by the state represented in the circle)
represent a physical change that occurs to the device 100, that is
detected by one or more of hardware and software, the detection
triggering one or more of a hardware and/or software interrupt that
is used to control and/or manage one or more functions of device
100.
[0098] As illustrated in FIG. 3A, there are twelve exemplary
"physical" states: closed 304, transition 308 (or opening
transitional state), easel 312, modified easel 316, open 320,
inbound/outbound call or communication 324, image/video capture
328, transition 332 (or closing transitional state), landscape 340,
docked 336, docked 344 and landscape 348. Next to each illustrative
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 symbolized by the international icon for a telephone and
the icon for a camera, respectfully.
[0099] In state 304, the device is in a closed state with the
device 100 generally oriented in the portrait direction with the
primary screen 104 and the secondary screen 108 back-to-back in
different planes (see FIG. 1H). From the closed state, the device
100 can enter, for example, docked state 336, where the device 100
is coupled with a docking station, docking cable, or in general
docked or associated with one or more other devices or peripherals,
or the landscape state 340, where the device 100 is generally
oriented with the primary screen 104 facing the user, and the
primary screen 104 and the secondary screen 108 being
back-to-back.
[0100] In the closed state, the device can also move to a
transitional state where the device remains closed by the display
is moved from one screen 104 to another screen 108 based on a user
input, e.g., a double tap on the screen 110, 114. Still another
embodiment includes a bilateral state. In the bilateral 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 display 110, 114 may
be the same or different based on the application and the state of
that application. For example, while acquiring an image with a
camera, the device may display the view finder on the first display
110 and displays a preview for the photo subjects (full screen and
mirrored left-to-right) on the second display 114.
[0101] In state 308, a transition state from the closed state 304
to the semi-open state or easel state 312, the device 100 is shown
opening with the primary screen 104 and the secondary screen 108
being rotated around a point of axis coincidence with the hinge.
Upon entering the easel state 312, the primary screen 104 and the
secondary screen 108 are separated from one another such that, for
example, the device 100 can sit in an easel-like configuration on a
surface.
[0102] In state 316, known as the modified easel position, the
device 100 has the primary screen 104 and the secondary screen 108
in a similar relative relationship to one another as in the easel
state 312, with the difference being one of the primary screen 104
or the secondary screen 108 are placed on a surface as shown.
[0103] State 320 is the open state where the primary screen 104 and
the secondary screen 108 are generally on the same plane. From the
open state, the device 100 can transition to the docked state 344
or the open landscape state 348. In the open state 320, the primary
screen 104 and the secondary screen 108 are generally in the
portrait-like orientation while in landscaped state 348 the primary
screen 104 and the secondary screen 108 are generally in a
landscape-like orientation.
[0104] State 324 is illustrative of a communication state, such as
when an inbound or outbound call is being received or placed,
respectively, by the device 100. While not illustrated for clarity,
it should be appreciated the device 100 can transition to the
inbound/outbound call state 324 from any state illustrated in FIG.
3. In a similar manner, the image/video capture state 328 can be
entered into from any other state in FIG. 3, with the image/video
capture state 328 allowing the device 100 to take one or more
images via a camera and/or videos with a video capture device
240.
[0105] Transition state 322 illustratively shows primary screen 104
and the secondary screen 108 being closed upon one another for
entry into, for example, the closed state 304.
[0106] FIG. 3B illustrates, with reference to the key, the inputs
that are received to detect a transition from a first state to a
second state. In FIG. 3B, various combinations of states are shown
with in general, a portion of the columns being directed toward a
portrait state 352, a landscape state 356, and a portion of the
rows being directed to portrait state 360 and landscape state
364.
[0107] In FIG. 3B, the Key indicates that "H" represents an input
from one or more Hall Effect sensors, "A" represents an input from
one or more accelerometers, "T" represents an input from a timer,
"P" represents a communications trigger input and "I" represents an
image and/or video capture request input. Thus, in the center
portion 376 of the chart, an input, or combination of inputs, are
shown that represent how the device 100 detects a transition from a
first physical state to a second physical state.
[0108] As discussed, in the center portion of the chart 376, the
inputs that are received enable the detection of a transition from,
for example, a portrait open state to a landscape easel
state--shown in bold--"HAT." For this exemplary transition from the
portrait open to the landscape easel state, a Hall Effect
sensor("H"), an accelerometer ("A") and a timer ("T") input may be
needed. The timer input can be derived from, for example, a clock
associated with the processor.
[0109] In addition to the portrait and landscape states, a docked
state 368 is also shown that is triggered based on the receipt of a
docking signal 372. As discussed above and in relation to FIG. 3,
the docking signal can be triggered by the association of the
device 100 with one or more other device 100s, accessories,
peripherals, smart docks, or the like.
[0110] User Interaction:
[0111] FIGS. 4A through 4H depict various graphical representations
of gesture inputs that may be recognized by the screens 104, 108.
The gestures may be performed not only by a user's body part, such
as a digit, but also by other devices, such as a stylus, that may
be sensed by the contact sensing portion(s) of a screen 104, 108.
In general, gestures are interpreted differently, based on where
the gestures are performed (either directly on the display 110, 114
or in the gesture capture region 120, 124). For example, gestures
in the display 110,114 may be directed to a desktop or application,
and gestures in the gesture capture region 120, 124 may be
interrupted as for the system.
[0112] With reference to FIGS. 4A-4H, a first type of gesture, a
touch gesture 420, is substantially stationary on the screen
104,108 for a selected length of time. A circle 428 represents a
touch or other contact type received at particular location of a
contact sensing portion of the screen. The circle 428 may include a
border 432, the thickness of which indicates a length of time that
the contact is held substantially stationary at the contact
location. For instance, a tap 420 (or short press) has a thinner
border 432a than the border 432b for a long press 424 (or for a
normal press). The long press 424 may involve a contact that
remains substantially stationary on the screen for longer time
period than that of a tap 420. As will be appreciated, differently
defined gestures may be registered depending upon the length of
time that the touch remains stationary prior to contact cessation
or movement on the screen.
[0113] With reference to FIG. 4C, a drag gesture 400 on the screen
104,108 is an initial contact (represented by circle 428) with
contact movement 436 in a selected direction. The initial contact
428 may remain stationary on the screen 104,108 for a certain
amount of time represented by the border 432. The drag gesture
typically requires the user to contact an icon, window, or other
displayed image at a first location followed by movement of the
contact in a drag direction to a new second location desired for
the selected displayed image. The contact movement need not be in a
straight line but have any path of movement so long as the contact
is substantially continuous from the first to the second
locations.
[0114] With reference to FIG. 4D, a flick gesture 404 on the screen
104,108 is an initial contact (represented by circle 428) with
truncated contact movement 436 (relative to a drag gesture) in a
selected direction. In embodiments, a flick has a higher exit
velocity for the last movement in the gesture compared to the drag
gesture. The flick gesture can, for instance, be a finger snap
following initial contact. Compared to a drag gesture, a flick
gesture generally does not require continual contact with the
screen 104,108 from the first location of a displayed image to a
predetermined second location. The contacted displayed image is
moved by the flick gesture in the direction of the flick gesture to
the predetermined second location. Although both gestures commonly
can move a displayed image from a first location to a second
location, the temporal duration and distance of travel of the
contact on the screen is generally less for a flick than for a drag
gesture.
[0115] With reference to FIG. 4E, a pinch gesture 408 on the screen
104,108 is depicted. The pinch gesture 408 may be initiated by a
first contact 428 a to the screen 104,108 by, for example, a first
digit and a second contact 428b to the screen 104,108 by, for
example, a second digit. The first and second contacts 428a,b may
be detected by a common contact sensing portion of a common screen
104,108, by different contact sensing portions of a common screen
104 or 108, or by different contact sensing portions of different
screens. The first contact 428a is held for a first amount of time,
as represented by the border 432a, and the second contact 428b is
held for a second amount of time, as represented by the border
432b. The first and second amounts of time are generally
substantially the same, and the first and second contacts 428a, b
generally occur substantially simultaneously. The first and second
contacts 428a, b generally also include corresponding first and
second contact movements 436a, b, respectively. The first and
second contact movements 436a, b are generally in opposing
directions. Stated another way, the first contact movement 436a is
towards the second contact 436b, and the second contact movement
436b is towards the first contact 436a. More simply stated, the
pinch gesture 408 may be accomplished by a user's digits touching
the screen 104,108 in a pinching motion.
[0116] With reference to FIG. 4F, a spread gesture 410 on the
screen 104,108 is depicted. The spread gesture 410 may be initiated
by a first contact 428a to the screen 104,108 by, for example, a
first digit and a second contact 428b to the screen 104,108 by, for
example, a second digit. The first and second contacts 428a,b may
be detected by a common contact sensing portion of a common screen
104,108, by different contact sensing portions of a common screen
104,108, or by different contact sensing portions of different
screens. The first contact 428a is held for a first amount of time,
as represented by the border 432a, and the second contact 428b is
held for a second amount of time, as represented by the border
432b. The first and second amounts of time are generally
substantially the same, and the first and second contacts 428a, b
generally occur substantially simultaneously. The first and second
contacts 428a, b generally also include corresponding first and
second contact movements 436a,b, respectively. The first and second
contact movements 436a, b are generally in a common direction.
Stated another way, the first and second contact movements 436a, b
are away from the first and second contacts 428a, b. More simply
stated, the spread gesture 410 may be accomplished by a user's
digits touching the screen 104,108 in a spreading motion.
[0117] The above gestures may be combined in any manner, such as
those shown by FIGS. 4G and H, to produce a determined functional
result. For example, in FIG. G a tap gesture 420 is combined with a
drag or flick gesture 412 in a direction away from the tap gesture
420. In FIG. H, a tap gesture 420 is combined with a drag or flick
gesture 412 in a direction towards the tap gesture 420.
[0118] The functional result of receiving a gesture can vary
depending on a number of factors, including a state of the device
100, display 110, 114, or screen 104, 108, a context associated
with the gesture, or sensed location of the gesture. The state of
the device commonly refers to one or more of a configuration of the
device 100, a display orientation, and user and other inputs
received by the device 100. Context commonly refers to one or more
of the particular application(s) selected by the gesture and the
portion(s) of the application currently executing, whether the
application is a single- or multi-screen application, and whether
the application is a multi-screen application displaying one or
more windows in one or more screens or in one or more stacks.
Sensed location of the gesture commonly refers to whether the
sensed set(s) of gesture location coordinates are on a touch
sensitive display 110, 114 or a gesture capture region 120, 124,
whether the sensed set(s) of gesture location coordinates are
associated with a common or different display or screen 104,108,
and/or what portion of the gesture capture region contains the
sensed set(s) of gesture location coordinates.
[0119] A tap, when received by an a touch sensitive display 110,
114, can be used, for instance, to select an icon to initiate or
terminate execution of a corresponding application, to maximize or
minimize a window, to reorder windows in a stack, and to provide
user input such as by keyboard display or other displayed image. A
drag, when received by a touch sensitive display 110, 114, can be
used, for instance, to relocate an icon or window to a desired
location within a display, to reorder a stack on a display, or to
span both displays (such that the selected window occupies a
portion of each display simultaneously). A flick, when received by
a touch sensitive display 110, 114 or a gesture capture region 120,
124, can be used to relocate a window from a first display to a
second display or to span both displays (such that the selected
window occupies a portion of each display simultaneously). Unlike
the drag gesture, however, the flick gesture is generally not used
to move the displayed image to a specific user-selected location
but to a default location that is not configurable by the user.
[0120] The pinch gesture, when received by a touch sensitive
display 110, 114 or a gesture capture region 120, 124, can be used
to maximize or otherwise increase the displayed area or size of a
window (typically when received entirely by a common display), to
switch windows displayed at the top of the stack on each display to
the top of the stack of the other display (typically when received
by different displays or screens), or to display an application
manager (a "pop-up window" that displays the windows in the stack).
The spread gesture, when received by a touch sensitive display 110,
114 or a gesture capture region 120, 124, can be used to minimize
or otherwise decrease the displayed area or size of a window, to
switch windows displayed at the top of the stack on each display to
the top of the stack of the other display (typically when received
by different displays or screens), or to display an application
manager (typically when received by an off-screen gesture capture
region on the same or different screens).
[0121] The combined gestures of FIG. 4G, when received by a common
display capture region in a common display or screen 104,108, can
be used to hold a first window stack location in a first stack
constant for a display receiving the gesture while reordering a
second window stack location in a second window stack to include a
window in the display receiving the gesture. The combined gestures
of FIG. 4H, when received by different display capture regions in a
common display or screen 104,108 or in different displays or
screens, can be used to hold a first window stack location in a
first window stack constant for a display receiving the tap part of
the gesture while reordering a second window stack location in a
second window stack to include a window in the display receiving
the flick or drag gesture. Although specific gestures and gesture
capture regions in the preceding examples have been associated with
corresponding sets of functional results, it is to be appreciated
that these associations can be redefined in any manner to produce
differing associations between gestures and/or gesture capture
regions and/or functional results.
[0122] Firmware and Software:
[0123] The memory 508 may store and the processor 504 may execute
one or more software components. These components can include at
least one operating system (OS) 516a and/or 516b, a framework 520,
and/or one or more application(s) 564a and/or 564b from an
application store 560. The processor 504 may receive inputs from
drivers 512, previously described in conjunction with FIG. 2. The
OS 516 can be any software, consisting of programs and data, that
manages computer hardware resources and provides common services
for the execution of various applications 564. The OS 516 can be
any operating system and, at least in some embodiments, dedicated
to mobile devices, including, but not limited to, Linux, Android,
iPhone OS (iOS), Windows Phone 7, etc. The OS 516 is operable to
provide functionality to the phone by executing one or more
operations, as described herein.
[0124] The applications 564 can be any higher level software that
executes particular functionality for the user. Applications 564
can include programs such as email clients, web browsers, texting
applications, games, media players, office suites, etc. The
applications 564 can be stored in an application store 560, which
may represent any memory or data storage, and the management
software associated therewith, for storing the applications 564.
Once executed, the applications 564 may be run in a different area
of memory 508.
[0125] The framework 520 may be any software or data that allows
the multiple tasks running on the device to interact. In
embodiments, at least portions of the framework 520 and the
discrete components described hereinafter may be considered part of
the OS 516 or an application 564. However, these portions will be
described as part of the middleware 520, but those components are
not so limited. The framework 520 can include, but is not limited
to, a Multi-Display Management (MDM) module 524, a Surface Cache
module 528, a Window Management module 532, an Input Management
module 536, a Task Management module 540, a Display Controller, one
or more frame buffers 548, a task stack 552, one or more window
stacks 550 (which is a logical arrangement of windows and/or
desktops in a display area), and/or an event buffer 556.
[0126] The MDM module 524 includes one or more modules that are
operable to manage the display of applications or other data on the
two screens of the device. An embodiment of the MDM module 524 is
described in conjunction with FIG. 5B. In embodiments, the MDM
module 524 receives inputs from the OS 516, the drivers 512 and the
applications 564. The inputs assist the MDM module 524 in
determining how to configure and allocate the displays according to
the application's preferences and requirements, and the user's
actions. Once a determination for display configurations is
determined, the MDM module 524 can bind the applications 564 to a
display configuration. The configuration may then be provided to
one or more other components to generate the display.
[0127] The Surface Cache module 528 includes any memory or storage
and the software associated therewith to store or cache one or more
images from the display screens. Each display screen may have
associated with the screen a series of active and non-active
windows (or other display objects (such as a desktop display)). The
active window (or other display object) is currently being
displayed. The non-active windows (or other display objects) were
opened and/or at some time displayed but are now "behind" the
active window (or other display object). To enhance the user
experience, before being covered by another active window (or other
display object), a "screen shot" of a last generated image of the
window (or other display object) can be stored. The Surface Cache
module 528 may be operable to store the last active image of a
window (or other display object) not currently displayed. Thus, the
Surface Cache module 528 stores the images of non-active windows
(or other display objects) in a data store (not shown).
[0128] In embodiments, the Window Management module 532 is operable
to manage the windows (or other display objects) that are active or
not active on each of the screens. The Window Management module
532, based on information from the MDM module 524, the OS 516, or
other components, determines when a window (or other display
object) is active or not active. The Window Management module 532
may then put a non-visible window (or other display object) in a
"not active state" and in conjunction with the Task Management
module 540 to suspend the application's operation. Further, the
Window Management module 532 may assign a screen identifier to the
window (or other display object) or manage one or more other items
of data associated with the window (or other display object). The
Window Management module 532 may also provide the stored
information to the application 564, the Task Management module 540,
or other components interacting with or associated with the window
(or other display object).
[0129] The Input Management module 536 is operable to manage events
that occur with the device. An event is any input into the window
environment, for example, a user interface interactions with a
user. The Input Management module 536 receives the events and
logically stores the events in an event buffer 556. Events can
include such user interface interactions as a "down event," which
occurs when a screen 104, 108 receives a touch signal from a user,
a "move event," which occurs when the screen 104, 108 determines
that a user's finger is moving across a screen(s), an "up event,
which occurs when the screen 104, 108 determines that the user has
stopped touching the screen 104, 108, etc. These events are
received, stored, and forwarded to other modules by the Input
Management module 536.
[0130] A task can be an application component that provides a
screen with which users can interact in order to do something, such
as dial the phone, take a photo, send an email, or view a map. Each
task may be given a window in which to draw a user interface. The
window typically fills the display 110,114, but may be smaller than
the display 110,114 and float on top of other windows. An
application usually consists of multiple activities that are
loosely bound to each other. Typically, one task in an application
is specified as the "main" task, which is presented to the user
when launching the application for the first time. Each task can
then start another task to perform different actions.
[0131] The Task Management module 540 is operable to manage the
operation of the one or more applications 564 that may be executed
by the device. Thus, the Task Management module 540 can receive
signals to execute an application stored in the application store
560. The Task Management module 540 may then instantiate one or
more tasks or components of the application 564 to begin operation
of the application 564. Further, the Task Management module 540 may
suspend the application 564 based on user interface changes.
Suspending the application 564 may maintain application data in
memory but may limit or stop access to processor cycles for the
application 564. Once the application becomes active again, the
Task Management module 540 can again provide access to the
processor.
[0132] The Display Controller 544 is operable to render and output
the display(s) for the multi-screen device. In embodiments, the
Display Controller 544 creates and/or manages one or more frame
buffers 548. A frame buffer 548 can be a display output that drives
a display from a portion of memory containing a complete frame of
display data. In embodiments, the Display Controller 544 manages
one or more frame buffers. One frame buffer may be a composite
frame buffer that can represent the entire display space of both
screens. This composite frame buffer can appear as a single frame
to the OS 516. The Display Controller 544 can sub-divide this
composite frame buffer as required for use by each of the displays
110, 114. Thus, by using the Display Controller 544, the device 100
can have multiple screen displays without changing the underlying
software of the OS 516.
[0133] The Application Manager 562 can be a service that provides
the presentation layer for the window environment. Thus, the
Application Manager 562 provides the graphical model for rendering
by the Window Management Module 556. Likewise, the Desktop 566
provides the presentation layer for the Application Store 560.
Thus, the desktop provides a graphical model of a surface having
selectable application icons for the Applications 564 in the
Application Store 560 that can be provided to the Window Management
Module 556 for rendering.
[0134] An embodiment of the MDM module 524 is shown in FIG. 5B. The
MDM module 524 is operable to determine the state of the
environment for the device, including, but not limited to, the
orientation of the device, what applications 564 are executing, how
the applications 564 are to be displayed, what actions the user is
conducting, the tasks being displayed, etc. To configure the
display, the MDM module 524 interprets these environmental factors
and determines a display configuration, as described in conjunction
with FIGS. 6A-6J. Then, the MDM module 524 can bind the
applications 564 or other device components to the displays. The
configuration may then be sent to the Display Controller 544 and/or
the OS 516 to generate the display. The MDM module 524 can include
one or more of, but is not limited to, a Display Configuration
Module 568, a Preferences Module 572, a Device State Module 574, a
Gesture Module 576, a Requirements Module 580, an Event Module 584,
and/or a Binding Module 588.
[0135] The Display Configuration Module 568 determines the layout
for the display. In embodiments, the Display Configuration Module
568 can determine the environmental factors. The environmental
factors may be received from one or more other MDM module 524
modules or from other sources. The Display Configuration Module 568
can then determine from the list of factors the best configuration
for the display. Some embodiments of the possible configurations
and the factors associated therewith are described in conjunction
with FIGS. 6A-6F.
[0136] The Preferences Module 572 is operable to determine display
preferences for an application 564 or other component. For example,
an application can have a preference for Single or Dual displays.
The Preferences Module 572 can determine or receive the application
preferences and store the preferences. As the configuration of the
device changes, the preferences may be reviewed to determine if a
better display configuration can be achieved for the application
564.
[0137] The Device State Module 574 is operable to determine or
receive the state of the device. The state of the device can be as
described in conjunction with FIGS. 3A and 3B. The state of the
device can be used by the Display Configuration Module 568 to
determine the configuration for the display. As such, the Device
State Module 574 may receive inputs and interpret the state of the
device. The state information is then provided to the Display
Configuration Module 568.
[0138] The Gesture Module 576 is operable to determine if the user
is conducting any actions on the user interface. Thus, the Gesture
Module 576 can receive task information either from the task stack
552 or the Input Management module 536. These gestures may be as
defined in conjunction with FIGS. 4A through 4H. For example,
moving a window causes the display to render a series of display
frames that illustrate the window moving. The gesture associated
with such user interface interaction can be received and
interpreted by the Gesture Module 576. The information about the
user gesture is then sent to the Task Management Module 540 to
modify the display binding of the task.
[0139] The Requirements Module 580, similar to the Preferences
Module 572, is operable to determine display requirements for an
application 564 or other component. An application can have a set
display requirement that must be observed. Some applications
require a particular 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. As the orientation of the
device changes, the Requirements Module 580 can reassert the
display requirements for the application 564. The Display
Configuration Module 568 can generate a display configuration that
is in accordance with the application display requirements, as
provided by the Requirements Module 580.
[0140] The Event Module 584, similar to the Gesture Module 576, is
operable to determine one or more events occurring with an
application or other component that can affect the user interface.
Thus, the Gesture Module 576 can receive event information either
from the event buffer 556 or the Task Management module 540. These
events can change how the tasks are bound to the displays. For
example, an email application receiving an email can cause the
display to render the new message in a secondary screen. The events
associated with such application execution can be received and
interpreted by the Event Module 584. The information about the
events then may be sent to the Display Configuration Module 568 to
modify the configuration of the display.
[0141] The Binding Module 588 is operable to bind the applications
564 or the other components to the configuration determined by the
Display Configuration Module 568. A binding associates, in memory,
the display configuration for each application with the display and
mode of the application. Thus, the Binding Module 588 can associate
an application with a display configuration for the application
(e.g. landscape, portrait, multi-screen, etc.). Then, the Binding
Module 588 may assign a display identifier to the display. The
display identifier associated the application with a particular
screen of the device. This binding is then stored and provided to
the Display Controller 544, the OS 516, or other components to
properly render the display. The binding is dynamic and can change
or be updated based on configuration changes associated with
events, gestures, state changes, application preferences or
requirements, etc.
[0142] User Interface Configurations:
[0143] With reference now to FIGS. 6A-J, various types of output
configurations made possible by the device 100 will be described
hereinafter.
[0144] FIGS. 6A and 6B depict two different output configurations
of the device 100 being in a first state. Specifically, FIG. 6A
depicts the device 100 being in a closed portrait state 304 where
the data is displayed on the primary screen 104. In this example,
the device 100 displays data via the touch sensitive display 110 in
a first portrait configuration 604. As can be appreciated, the
first portrait configuration 604 may only display a desktop or
operating system home screen. Alternatively, one or more windows
may be presented in a portrait orientation while the device 100 is
displaying data in the first portrait configuration 604.
[0145] FIG. 6B depicts the device 100 still being in the closed
portrait state 304, but instead data is displayed on the secondary
screen 108. In this example, the device 100 displays data via the
touch sensitive display 114 in a second portrait configuration
608.
[0146] It may be possible to display similar or different data in
either the first or second portrait configuration 604, 608. It may
also be possible to transition between the first portrait
configuration 604 and second portrait configuration 608 by
providing the device 100 a user gesture (e.g., a double tap
gesture), a menu selection, or other means. Other suitable gestures
may also be employed to transition between configurations.
Furthermore, it may also be possible to transition the device 100
from the first or second portrait configuration 604, 608 to any
other configuration described herein depending upon which state the
device 100 is moved.
[0147] An alternative output configuration may be accommodated by
the device 100 being in a second state. Specifically, FIG. 6C
depicts a third portrait configuration where data is displayed
simultaneously on both the primary screen 104 and the secondary
screen 108. The third portrait configuration may be referred to as
a Dual-Portrait (PD) output configuration. In the PD output
configuration, the touch sensitive display 110 of the primary
screen 104 depicts data in the first portrait configuration 604
while the touch sensitive display 114 of the secondary screen 108
depicts data in the second portrait configuration 608. The
simultaneous presentation of the first portrait configuration 604
and the second portrait configuration 608 may occur when the device
100 is in an open portrait state 320. In this configuration, the
device 100 may display one application window in one display 110 or
114, two application windows (one in each display 110 and 114), one
application window and one desktop, or one desktop. Other
configurations may be possible. It should be appreciated that it
may also be possible to transition the device 100 from the
simultaneous display of configurations 604, 608 to any other
configuration described herein depending upon which state the
device 100 is moved. Furthermore, while in this state, an
application's display preference may place the device into
bilateral mode, in which both displays are active to display
different windows in the same application. For example, a Camera
application may display a viewfinder and controls on one side,
while the other side displays a mirrored preview that can be seen
by the photo subjects. Games involving simultaneous play by two
players may also take advantage of bilateral mode.
[0148] FIGS. 6D and 6E depicts two further output configurations of
the device 100 being in a third state. Specifically, FIG. 6D
depicts the device 100 being in a closed landscape state 340 where
the data is displayed on the primary screen 104. In this example,
the device 100 displays data via the touch sensitive display 110 in
a first landscape configuration 612. Much like the other
configurations described herein, the first landscape configuration
612 may display a desktop, a home screen, one or more windows
displaying application data, or the like.
[0149] FIG. 6E depicts the device 100 still being in the closed
landscape state 340, but instead data is displayed on the secondary
screen 108. In this example, the device 100 displays data via the
touch sensitive display 114 in a second landscape configuration
616. It may be possible to display similar or different data in
either the first or second portrait configuration 612, 616. It may
also be possible to transition between the first landscape
configuration 612 and second landscape configuration 616 by
providing the device 100 with one or both of a twist and tap
gesture or a flip and slide gesture. Other suitable gestures may
also be employed to transition between configurations. Furthermore,
it may also be possible to transition the device 100 from the first
or second landscape configuration 612, 616 to any other
configuration described herein depending upon which state the
device 100 is moved.
[0150] FIG. 6F depicts a third landscape configuration where data
is displayed simultaneously on both the primary screen 104 and the
secondary screen 108. 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 of the
primary screen 104 depicts data in the first landscape
configuration 612 while the touch sensitive display 114 of the
secondary screen 108 depicts data in the second landscape
configuration 616. The simultaneous presentation of the first
landscape configuration 612 and the second landscape configuration
616 may occur when the device 100 is in an open landscape state
340. It should be appreciated that it may also be possible to
transition the device 100 from the simultaneous display of
configurations 612, 616 to any other configuration described herein
depending upon which state the device 100 is moved.
[0151] FIGS. 6G and 6H depict two views of a device 100 being in
yet another state. Specifically, the device 100 is depicted as
being in an easel state 312. FIG. 6G shows that a first easel
output configuration 618 may be displayed on the touch sensitive
display 110. FIG. 6H shows that a second easel output configuration
620 may be displayed on the touch sensitive display 114. The device
100 may be configured to depict either the first easel output
configuration 618 or the second easel output configuration 620
individually. Alternatively, both the easel output configurations
618, 620 may 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 a modified easel state 316. It
should be appreciated that simultaneous utilization of the easel
output configurations 618, 620 may facilitate two-person games
(e.g., Battleship.RTM., chess, checkers, etc.), multi-user
conferences where two or more users share the same device 100, and
other applications. As can be appreciated, it may also be possible
to transition the device 100 from the display of one or both
configurations 618, 620 to any other configuration described herein
depending upon which state the device 100 is moved.
[0152] FIG. 6I depicts yet another output configuration that may be
accommodated while the device 100 is in an open portrait state 320.
Specifically, the device 100 may be configured to present a single
continuous image across both touch sensitive displays 110, 114 in a
portrait configuration referred to herein as a Portrait-Max (PMax)
configuration 624. In this configuration, data (e.g., a single
image, application, window, icon, video, etc.) may be split and
displayed partially on one of the touch sensitive displays while
the other portion of the data is displayed on the other touch
sensitive display. The Pmax configuration 624 may facilitate a
larger display and/or better resolution for displaying a particular
image on the device 100. Similar to other output configurations, it
may be possible to transition the device 100 from the Pmax
configuration 624 to any other output configuration described
herein depending upon which state the device 100 is moved.
[0153] FIG. 6J depicts still another output configuration that may
be accommodated while the device 100 is in an open landscape state
348. Specifically, the device 100 may be configured to present a
single continuous image across both touch sensitive displays 110,
114 in a landscape configuration referred to herein as a
Landscape-Max (LMax) configuration 628. In this configuration, data
(e.g., a single image, application, window, icon, video, etc.) may
be split and displayed partially on one of the touch sensitive
displays while the other portion of the data is displayed on the
other touch sensitive display. The Lmax configuration 628 may
facilitate a larger display and/or better resolution for displaying
a particular image on the device 100. Similar to other output
configurations, it may be possible to transition the device 100
from the Lmax configuration 628 to any other output configuration
described herein depending upon which state the device 100 is
moved.
[0154] FIGS. 7A-7C illustrate an embodiment showing device 100 and
how device 100 responds when an incomplete gesture is made. FIG. 7A
illustrates device 100 (with screens 104 and 108) when a focus is
on screen 104 and display area 110. As noted above, "focus" means
active and selected for receiving input. Accordingly, in FIG. 7A
screen 104 and display area 110 are active and selected for input.
Highlight 704 provides an indication to a user that screen 104 and
display area 110 have the focus. If a user presses configurable
area 112, device 100 will consider the inputs as inputs for screen
104 and/or for display 110.
[0155] As shown in FIG. 7B, a user can make a gesture 708, such as
a drag or flick gesture on gesture capture area 120. Device 100
receives the gesture. A determination is made by device 100 as to
whether the gesture 708 was complete. If the gesture was not
complete, then as shown in FIG. 7C the focus is maintained on
screen 104 and display area 110.
[0156] Highlighting 704 as noted above, indicates that screen 104
and display 110 are active. Highlighting 704 can be effected in a
number of different ways. In some embodiments, the highlighting 704
is accomplished using light. In these embodiments, a backlight in
device 100 may be configured to provide brighter light in some
areas, such as around a border as shown in FIGS. 7A-7C. In other
embodiments, the brighter light may be located on just one
side/area or may be the entire display 110, which is made brighter
than at least a portion of screen 108 and/or display 114.
[0157] In other embodiments, highlighting 704 may be accomplished
using color, or a displayed image such as an icon that indicates
that the screen 104 and display 110 have the focus. In other
embodiments, the highlighting may be accomplished by some other
difference, such as changing text to a different font type, size,
or other characteristic. In some embodiments, the highlighting can
be accomplished, or enhanced, by changing a different screen,
display, and/or displayed image. For example, in embodiments, the
screen, display and/or displayed image that does not have the
focus, will be deemphasized by darkening, a color change, or other
features that distinguishes it from the highlighted screen,
display, and/or image. As can be appreciated, a combination of one
or more of the above highlighting features may be used in some
embodiments.
[0158] In one embodiment, in addition to highlighting 704,
configurable area 112 of screen 104 is highlighted to indicate that
screen 104 and display 110 have the focus. Device 100 can be
configured so that configurable areas are only highlighted when the
corresponding screen has the focus. That is, configurable area 112
is highlighted when screen 104 is in focus, while configurable area
116 is highlighted when focus is on screen 108. As indicated above,
the highlighting may be effected by lighting, color, or an image
displayed near the configurable area. In the embodiment, shown in
FIGS. 7A-7C, when screen 104 is in focus, the configurable area 112
is back lit to show buttons that can be used to receive input from
a user.
[0159] In some embodiments, when configurable area 112 is
highlighted, input can be received by pressing portions of area
112. At the same time, device 100 may be configured so that no
input is received from configurable area 116. Thus, even if a user
presses on area 116, no input will be received by device 100.
Similarly, when configurable area 116 is highlighted device 100
will allow input to be received from area 116, and no input will be
received from area 112. In other embodiments, only one configurable
area will be highlighted at a time reflecting the particular
screen, display, or image that is in focus. That is, when
configurable area 112 is highlighted configurable area 116 will not
be highlighted, and when configurable area 116 is highlighted
configurable area 112 will not be highlighted.
[0160] It is noted that although gesture 708 is being made in
gesture capture area 120, which is not on display 110, in other
embodiments, the gesture 708 is made on one or more portions of
displays 110 and 114. The gesture 708 may involve touching some
portion of displays 110 and 114 (which are touch sensitive) or can
involve only movement above the surface of displays 110 and
114.
[0161] In some embodiments, even though the gesture 708 is
incomplete, device 100 may be configured to make changes to
displays 104 and 108 to show that gesture 704 has been received.
For example, in some embodiments image 712 (all of the image(s)
displayed on display 110) appears to move across both displays 110
and 114 when gesture 708 is received. This feature allows a user to
appreciate that the gesture 708 has been received, however it is
probably incomplete as the focus was not changed to screen 108 and
display 114 and was maintained on screen 104 and display 108 (FIG.
7C). The user can then make the gesture 708 again. This feature
provides some visual feedback to a user regarding the incomplete
gesture.
[0162] FIGS. 8A-8C illustrate another embodiment that provides
feedback to a user about an incomplete gesture. FIG. 8A illustrates
an image 804 displayed on display 110. The image 804 may be any
type of displayed image such as a photo, a document, an icon that
represent an application, or a window of an application. Image 804
is highlighted in FIG. 8A indicating that it is in focus. When
gesture 708 is received by gesture capture area 120, image 804
appears to move from display 110 to display 114. Because a
determination is made that the gesture was not complete, the image
804 is returned back to its original position. The movement of
image 804 indicates to a user that the gesture 708 was received but
because image 804 was not displayed on display 114 it must have
been incomplete. The user can then make gesture 708 again to change
focus.
[0163] In some embodiments, image 712 or image 804 may be displayed
as moving depending upon how device 100 is configured. For example,
the device 100 may be configured to move image 712 (entire image(s)
displayed on display 110) when the gesture 708 is a drag gesture
and image 804 (active window, icon, photo, document) if gesture 708
is a flick gesture or some other gesture. In other embodiments, the
location of the gesture 708, whether in gesture capture region 120
or some other portion of displays 110 and 114, may determine
whether image 710 or image 804 is shown as moving from display 110
to display 114.
[0164] FIGS. 9A-9C illustrates an embodiment of device 100 and its
output in response to receiving a completed gesture. In FIG. 9A the
focus is on screen 104, display 110, and image 804. Image 804 is in
embodiments a window of an active application which is selected to
receive input from a user. In the embodiment shown in FIGS. 9A-9C,
a user makes a gesture 708 in gesture capture region 120. The
gesture is a complete gesture. In response to the complete gesture,
device 100 changes focus away from screen 104, display 110, and
image 804 and to screen 108 and display 114.
[0165] In some embodiments, as shown in FIG. 9C, in addition to
changing the focus to screen 108 and display 114, the focus is also
automatically on an image that is displayed on display 114, i.e.,
image 904. In these embodiments, device 100 may be configured by a
user so that when focus is changed to a screen or display, the
focus will also be on an image, e.g., a window of an open
application, if one is open on the display to which the focus has
changed. The user may, for example, list applications in order of
priority such that if there is an open window the focus will change
to an application at the top of the list. If no window is open for
an application at the top the list, then the list can be traversed
in order of priority until an application with an open window is
found. If none of the applications on the list have open windows
then the focus will not change to any images on the display. In
some embodiments, the focus may be changed to a window of the same
application that was previously in focus.
[0166] In other embodiments, the focus may always change to a
default image (e.g., open window) selected by a user. In some
embodiments, if the default application does not have an open
window, device 100 may be configured to launch the application and
open a window that will then be in focus.
[0167] In some embodiments, device 100 is configured so that
depending upon the particular gesture 708, an image on the newly
focused display may be in focus or not. For example, the device 100
may be configured to have in image in focus when the gesture 708 is
a drag gesture. If the gesture 708 is a flick gesture or some other
gesture, no image will be in focus, and instead only display 114
will be focus. In other embodiments, the location of the gesture
708, whether in gesture capture region 120 or some other portion of
displays 110 and 114, may determine whether an image on the newly
focused display may be in focus or not.
[0168] It is noted that although gesture 708 is being made in
gesture capture area 120, which is not on display 110 or display
114, in other embodiments, the gesture 708 is made on one or more
portions of displays 110 and 114. The gesture 708 may involve
touching some portion of displays 110 and 114 (which are touch
sensitive) or can involve only movement above the surface of
displays 110 and 114.
[0169] As shown in FIG. 9C, when focus is changed to screen 108 and
display 114, configurable area 116 is highlighted to indicate that
the focus is changed. Device 100 can be configured so that
configurable areas are only highlighted when the corresponding
screen has the focus. That is, configurable area 112 is highlighted
when screen 104 and/or display 110 is in focus, while configurable
area 116 is highlighted when focus is on screen 108 and/or display
114. As indicated above, the highlighting may be effected by
lighting, color, or an image displayed near the configurable area.
In the embodiment, shown in FIGS. 9A-9C, when screen 104 and/or
display 110 is in focus, the configurable area 112 is back lit to
show buttons that can be used to receive input from a user.
Similarly, when focus changes to screen 108 and/or display 114, the
configurable area 116 is back lit to show buttons that can be used
to receive input from a user.
[0170] Referring now to FIG. 10, a flow diagram 1000 in accordance
with at least some embodiments of the present disclosure is shown
and will be described. Flow 1000 is in embodiments performed by a
device such as device 100. More specifically, one or more hardware
or software components may be involved in performing flow 1000. In
one embodiment, modules in middleware 520 (FIG. 5A) such as
multi-display management class 524 (FIG. 5B) perform one or more of
the steps of flow 1000. In other embodiments, in addition to, or in
lieu of, middleware 520 performing steps of flow 1000, operating
system kernel(s) 516a, processor 504, and/or drivers 512a-512b may
also perform steps of flow 1000.
[0171] Flow 1000 is initiated at 1004. Flow 1000 passes from 1004
to optional step 1008 where input regarding focus behavior is
received. In this step, a user may provide configuration
information that indicates how a device should handle focus when
receiving gestures. In embodiments, the device is device 100 (FIGS.
1-3) which includes multiple screens. The user may input any
information that affects how a device 100 may handle input
gestures, including but not limited to, changes (if any) that occur
to displays 104 and 108 when gestures are incomplete to show that a
gesture has been received, what is highlighted when focus is
changed, priority list of applications when focus is changed,
whether focus changes are limited to a display, screen, and/or
displayed image, whether focus behavior changes based on the type
of gesture received, and other information. In one embodiment, the
input indicates that in response to an incomplete gesture, the
focus should be maintained on the screen, display, and/or image
with the focus.
[0172] From step 1008, flow 1000 passes to step 1012 where a
gesture is received. The gesture can be received in some
embodiments by a gesture capture area such as areas 120 and 124
and/or pressure sensitive displays 110 and 114. In some
embodiments, as shown in FIGS. 1 and 2, the gesture capture area(s)
is distinct and located away from the pressure sensitive displays.
In other embodiments the gesture capture area may overlap partially
or completely with the pressure sensitive displays.
[0173] The gesture may be any type of gesture. In embodiments, the
gesture is one or more of the gestures illustrated in FIG. 4A-4H.
The device 100 is configured so that the gesture received at step
1012 indicates a request to change focus from the current
focus.
[0174] In some embodiments, flow 1000 may include an optional step
1016 that changes one or more of the displays to indicate the
receipt of the gesture. The change may be for example, moving an
image displayed on a first screen toward a second screen. The
particular changes made to the displays may be based, in part, on
the information received at optional step 1008.
[0175] After step 1016, a determination is made at 1020 as to
whether the gesture is complete. A determination can be made that
the gesture is complete if the input is recognized as a complete
gesture. In other words, data at step 1012 corresponds to a gesture
stored within the memory of device 100. If, however, the data
received at step 1012 does not correspond to any gesture stored
within the memory of device 100, then a determination can be made
that the gesture is not complete.
[0176] In those embodiments in which the gesture is complete, flow
1000 passes from determination 1020 to step 1024 where the focus is
changed. The focus is changed in accordance with predetermined
configurations, some of which may be based on the input received at
optional step 1008. For example, if the device 100 is configured so
that the gesture received at step 1012 indicates that the focus
should be changed to a second display, at step 1024 the focus will
be changed to the second display. If the configuration information
indicates that the focus should also be changed to an open window
displayed on the second display, then at step 1024 the open window
displayed on the second display will also be in focus. After step
1024, flow 1000 ends at 1028.
[0177] It should be noted that in some embodiments, step 1024 may
involve a number of sub steps. For example, in some embodiments as
part of step 1024, a configurable area may be highlighted, a
display may be highlighted, an icon may be generated indicating the
focus change, and/or portions of a first screen may be changed to
emphasize the highlighting on a second screen. In some embodiments,
the substeps may involve not allowing input from a configurable
area associated with a first screen and allowing input from a
configurable area associated with a second screen.
[0178] If at determination 1020, it is determined that the gesture
is not complete, then flow passes to step 1032. At step 1032, the
focus is maintained on the screen, display, and/or image where it
is currently. Flow 1000 ends at 1028.
[0179] The exemplary systems and methods of this disclosure have
been described in relation to FIGS. 1-10. However, to avoid
unnecessarily obscuring the present disclosure, the preceding
description omits a number of known structures and devices. This
omission is not to be construed as a limitation of the scopes of
the claims. Specific details are set forth to provide an
understanding of the present disclosure. It should however be
appreciated that the present disclosure may be practiced in a
variety of ways beyond the specific detail set forth herein.
[0180] Furthermore, while the exemplary aspects, embodiments,
and/or configurations illustrated herein show the various
components of the system collocated, certain components of the
system can be located remotely, at distant portions of a
distributed network, such as a LAN and/or the Internet, or within a
dedicated system. Thus, it should be appreciated, that the
components of the system can be combined in to one or more devices,
such as a ______, or collocated on a particular node of a
distributed network, such as an analog and/or digital
telecommunications network, a packet-switch network, or a
circuit-switched network. It will be appreciated from the preceding
description, and for reasons of computational efficiency, that the
components of the system can be arranged at any location within a
distributed network of components without affecting the operation
of the system. For example, the various components can be located
in a switch such as a PBX and media server, gateway, in one or more
communications devices, at one or more users' premises, or some
combination thereof. Similarly, one or more functional portions of
the system could be distributed between a telecommunications
device(s) and an associated computing device.
[0181] Furthermore, it should be appreciated that the various links
connecting the elements can be wired or wireless links, or any
combination thereof, or any other known or later developed
element(s) that is capable of supplying and/or communicating data
to and from the connected elements. These wired or wireless links
can also be secure links and may be capable of communicating
encrypted information. Transmission media used as links, for
example, can be any suitable carrier for electrical signals,
including coaxial cables, copper wire and fiber optics, and may
take the form of acoustic or light waves, such as those generated
during radio-wave and infra-red data communications.
[0182] Also, while the flowcharts have been discussed and
illustrated in relation to a particular sequence of events, it
should be appreciated that changes, additions, and omissions to
this sequence can occur without materially affecting the operation
of the disclosed embodiments, configuration, and aspects.
[0183] A number of variations and modifications of the disclosure
can be used. It would be possible to provide for some features of
the disclosure without providing others.
[0184] For example in one alternative embodiment, all of the focus
behavior information may be preprogrammed into the device 100. In
these embodiments, there would be no input received by a user
regarding how a device 100 handles gestures indicating a change in
focus.
[0185] In other alternative embodiments, device 100 may be in any
configuration described above with respect to FIGS. 6A-6J. In these
embodiments, gestures would be received as described above
indicating a request for changing focus. The focus would then
change from a first screen, display, or image to a second screen,
display, or image.
[0186] In yet another embodiment, the systems and methods of this
disclosure can be implemented in conjunction with a special purpose
computer, a programmed microprocessor or microcontroller and
peripheral integrated circuit element(s), an ASIC or other
integrated circuit, a digital signal processor, a hard-wired
electronic or logic circuit such as discrete element circuit, a
programmable logic device or gate array such as PLD, PLA, FPGA,
PAL, special purpose computer, any comparable means, or the like.
In general, any device(s) or means capable of implementing the
methodology illustrated herein can be used to implement the various
aspects of this disclosure. Exemplary hardware that can be used for
the disclosed embodiments, configurations and aspects includes
computers, handheld devices, telephones (e.g., cellular, Internet
enabled, digital, analog, hybrids, and others), and other hardware
known in the art. Some of these devices include processors (e.g., a
single or multiple microprocessors), memory, nonvolatile storage,
input devices, and output devices. Furthermore, alternative
software implementations including, but not limited to, distributed
processing or component/object distributed processing, parallel
processing, or virtual machine processing can also be constructed
to implement the methods described herein.
[0187] In yet another embodiment, the disclosed methods may be
readily implemented in conjunction with software using object or
object-oriented software development environments that provide
portable source code that can be used on a variety of computer or
workstation platforms. Alternatively, the disclosed system may be
implemented partially or fully in hardware using standard logic
circuits or VLSI design. Whether software or hardware is used to
implement the systems in accordance with this disclosure is
dependent on the speed and/or efficiency requirements of the
system, the particular function, and the particular software or
hardware systems or microprocessor or microcomputer systems being
utilized.
[0188] In yet another embodiment, the disclosed methods may be
partially implemented in software that can be stored on a storage
medium, executed on programmed general-purpose computer with the
cooperation of a controller and memory, a special purpose computer,
a microprocessor, or the like. In these instances, the systems and
methods of this disclosure can be implemented as program embedded
on personal computer such as an applet, JAVA.RTM. or CGI script, as
a resource residing on a server or computer workstation, as a
routine embedded in a dedicated 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.
[0189] Although the present disclosure describes components and
functions implemented in the aspects, embodiments, and/or
configurations with reference to particular standards and
protocols, the aspects, embodiments, and/or configurations are not
limited to such standards and protocols. Other similar standards
and protocols not mentioned herein are in existence and are
considered to be included in the present disclosure. Moreover, the
standards and protocols mentioned herein and other similar
standards and protocols not mentioned herein are periodically
superseded by faster or more effective equivalents having
essentially the same functions. Such replacement standards and
protocols having the same functions are considered equivalents
included in the present disclosure.
[0190] The present disclosure, in various aspects, embodiments,
and/or configurations, includes components, methods, processes,
systems and/or apparatus substantially as depicted and described
herein, including various aspects, embodiments, configurations
embodiments, subcombinations, and/or subsets thereof. Those of
skill 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, includes providing devices and
processes in the absence of items not depicted and/or described
herein or in various aspects, embodiments, and/or configurations
hereof, including in the absence of such items as may have been
used in previous devices or processes, e.g., for improving
performance, achieving ease and\or reducing cost of
implementation.
[0191] The foregoing discussion has been presented for purposes of
illustration and description. The foregoing is not intended to
limit the disclosure to the form or forms disclosed herein. In the
foregoing Detailed Description for example, various features of the
disclosure are grouped together in one or more aspects,
embodiments, and/or configurations for the purpose of streamlining
the disclosure. The features of the aspects, embodiments, and/or
configurations of the disclosure may be combined in alternate
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, inventive aspects lie in less than all features of
a single foregoing disclosed aspect, embodiment, and/or
configuration. Thus, the following claims are hereby incorporated
into this Detailed Description, with each claim standing on its own
as a separate preferred embodiment of the disclosure.
[0192] Moreover, though the description has included description of
one or more aspects, embodiments, and/or configurations and certain
variations and modifications, other variations, combinations, and
modifications are within the scope of the disclosure, e.g., as may
be within the skill and knowledge of those in the art, after
understanding the present disclosure. It is intended to obtain
rights which include alternative aspects, embodiments, and/or
configurations to the extent permitted, including alternate,
interchangeable and/or equivalent structures, functions, ranges or
steps to those claimed, whether or not such alternate,
interchangeable and/or equivalent structures, functions, ranges or
steps are disclosed herein, and without intending to publicly
dedicate any patentable subject matter.
* * * * *