BR112015012539B1 - Display device and method for controlling the same - Google Patents

Abstract

DISPLAY DEVICE AND CONTROL MODE THEREOF. A display device with a touchscreen that runs at least one application and a method for controlling the display device is provided. The method includes receiving an application run command to run at least one application, determining at least one of a size and position of a window that runs the at least one application according to a position at which the execution command of application is introduced, and display the window according to at least one of the window's size and position.

Description

TECHNICAL FIELD

[001] The present description relates to a display device and a method for controlling the same. More particularly, the present description relates to a display device that displays a window in which an application runs and a method of controlling the display device.

BACKGROUND OF THE TECHNIQUE

[002] A desktop computer is equipped with at least one display device (eg, a monitor). Likewise, a mobile device having a touch screen (eg, a portable phone, a smart phone, a tablet Personal Computer (PC), or the like) is also provided with a display device.

[003] A user can use a desktop computer, splitting the screen of a display device (eg, the screen is split horizontally or vertically and a plurality of windows are invoked in split screens) according to a task environment. When a web browser is running, the user can scroll up or down a web page using a page up button or a page down button on a keyboard. If the user uses a mouse instead of the keyboard, the user can scroll up or down a web page by selecting a scroll bar on one side of the web page using a mouse cursor. The user can also go to the top of the web page by selecting a top button displayed as text or an icon at the bottom of the web page.

[004] Compared to a desktop computer, a mobile device has a small screen size and limitations in inputting to the screen. Thus, it is difficult to split the screen on mobile device.

[005] A variety of apps can run on the mobile device. Apps include basic apps installed in a manufacturing process by a manufacturer and additional apps downloaded from app sales websites. Additional apps can be developed and registered for the app selling websites by regular users. Therefore, anyone can sell their app developed for mobile users freely through a website that sells apps. Currently, tens of thousands to hundreds of thousands of free or paid apps are available for mobile devices depending on the products.

DISCLOSURE OF THE INVENTION TECHNICAL PROBLEM

[006] While many applications stimulating user interest and satisfying user demands are provided for mobile devices, mobile devices have limits on display size and user interface (UI) due to their portable dimensions. As a result, users feel uncomfortable running a multitude of applications on their mobile devices. For example, when a user runs an app on a mobile device, the app is displayed over the entirety of a display area. If the user is running another application while the current application is running, the user must first terminate the current application and then select a run key to run the intended application. For example, the user has to go through a frustrating process of repeating and terminating each application in order to run a plurality of applications. However, a method for running a plurality of applications simultaneously on a mobile device has not yet been specified.

[007] As described above, although many applications stimulating user interest and satisfying user demands are provided for mobile devices, mobile devices have limits on display size and user interface due to their portable sizes. As a result, users feel uncomfortable running a multitude of applications on their mobile devices.

[008] Accordingly, there is a need for the development of a method for displaying a plurality of windows in a single view. Furthermore, a method is needed to easily invoke a plurality of windows and facilitate the arrangement of windows after the window call.

[009] More particularly, when a plurality of overlapping windows are displayed, a structure of switching from a currently displayed window to another window of lower priority needs to be specified.

[010] The above information is presented as background information only to assist in understanding this disclosure. No determination has been made, and no assertion is made, as to whether any of the above may be applicable as prior art with respect to the present disclosure.

SOLUTION TO THE PROBLEM

[011] Aspects of the present disclosure are to address at least the aforementioned problems and/or disadvantages and provide at least the advantages described below. Accordingly, one aspect of the present disclosure is to provide a display device for running a plurality of windows in various sizes on a single screen and to facilitate switching from one window to another lower-tier window, and a method for controlling the display device.

[012] In accordance with one aspect of the present invention, a method for controlling a display device with a touch screen, which runs at least one application, is provided. The method includes receiving an application run command to run at least one application, determining at least one of a size and position of a window that runs the at least one application according to a position where the application execution command is introduced, and to display the window according to at least one of the window's size and position.

[013] In accordance with another aspect of the present disclosure, a display device is provided. The display device includes a touch screen configured to receive an application run command to run at least one application, and a controller configured to determine at least one of a size and position of a window running the at least one application according to a position in which the application execution command is entered and to control the window display on the touch screen according to at least one of the window size and position.

[014] In accordance with another aspect of the present disclosure, a method for running an application on a display device including a touch screen is provided. The method includes displaying an application execution window in each of a plurality of regions of the touch screen, displaying a button on at least one boundary that separates the plurality of regions, receiving input that selects the button, and displaying a list of at least one application running in a specific region from among the plurality of regions in the specific region according to the input received.

[015] In accordance with another aspect of the present disclosure, a method for running an application on a display device including a touch screen is provided. The method includes displaying an application execution window in each of a plurality of regions of the touch screen, displaying a button on at least one boundary separating the plurality of regions, displaying a list of at least one execution icon of app on a partial area of the touchscreen, receive a drag input from dragging an app run icon from the list, determine a region to run a new app based on an end position of the drag input and a position button, and display an application launch window corresponding to the application launch icon in the given region.

[016] In accordance with another aspect of the present disclosure, a display device is provided. The display device includes a touch screen configured to display a window running an application in each of a plurality of regions, display a button on at least one boundary separating the plurality of regions, and receive input that selects the button, and a controller configured to display a list of at least one application running in a specific region from among the plurality of regions in the specific region according to the input received.

[017] In accordance with another aspect of the present disclosure, a display device is provided. The display device includes a touch screen configured to display a window running an application in each of a plurality of regions, display a button on at least one boundary separating the plurality of regions, display a list of at least one app run icon in a partial area of the touchscreen, and receive a drag input of dragging an app run icon from the list, and a controller configured to determine a region to run a new app based on an end position of the drag input and a position of the button, and control the touchscreen to display an application run window corresponding to the application run icon in the given region.

[018] Other salient aspects, advantages and features of the present description will be apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the accompanying drawings, describes various embodiments of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

[019] The foregoing and other aspects, features, and advantages of certain embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which: Figure 1 is a block diagram of a display in accordance with an embodiment of the present invention; Figures 2a, 2b, 2c, 2d, 2e, 2f, 2g, 2h, 2i, 2j, and 2k illustrate a windowing method according to an embodiment of the present invention; Figures 3a, 3b, 3c, 3d, 3e, 3f, 3g, 3h, and 3i illustrate stacks of activities managed in a display device in accordance with embodiments of the present invention; Figure 4a is a flowchart illustrating a method for controlling a display device in accordance with an embodiment of the present invention; Figure 4b is a flowchart illustrating a method for controlling a display device in accordance with an embodiment of the present invention; Figure 5 illustrates a window display ordering (Z-order) according to an embodiment of the present disclosure; Figures 6a, 6b, 6c, and 6d illustrate a method of running an application in accordance with an embodiment of the present invention; Figure 7 is a flowchart illustrating a method for controlling a display device in accordance with an embodiment of the present invention; Figures 8a, 8b, 8c, 8d, 8e, 8f, 8g, 8h, 8i, 8j, 8k, 8l, and 8m illustrate a method for displaying a plurality of windows in accordance with an embodiment of the present invention; Figures 9a, 9b, 9c, 9d, 9e, 9f, 9g, and 9h illustrate arrangements in accordance with embodiments of the present invention; Figures 10a, 10b, 10c, and 10d illustrate screens of a display device in accordance with embodiments of the present invention; Figures 11a, 11b, and 11c illustrate screens of a display device in accordance with embodiments of the present invention; Figures 12a, 12b, and 12c illustrate screens of a display device in accordance with embodiments of the present invention; Figures 13a, 13b, and 13c illustrate screens of a display device in accordance with embodiments of the present invention; Figures 14a, 14b, and 14c illustrate screens of a display device in accordance with embodiments of the present invention; Figures 15a, 15b, and 15c illustrate screens of a display device in accordance with embodiments of the present invention; Figures 16a, 16b, 16c and 16d illustrate screens of a display device in accordance with embodiments of the present invention; Figure 17 illustrates screens of a display device in accordance with an embodiment of the present invention; Figures 18a and 18b illustrate a 9-area division mode in accordance with embodiments of the present invention; Figure 19 is a flowchart illustrating a method for controlling a display device in accordance with an embodiment of the present invention; Figure 20 is a flowchart illustrating a method for controlling a display device in accordance with an embodiment of the present invention; Figures 21a, 21b, and 21c are screens of a display device in accordance with embodiments of the present invention; Figure 22 illustrates an activity stack in accordance with an embodiment of the present invention; Figures 23a and 23b illustrate screens of a display device depicting a Z-order change command in accordance with an embodiment of the present invention; Figure 24 illustrates an activity stack in accordance with an embodiment of the present invention; Figures 25a and 25b illustrate display screens depicting a Z-order change command in accordance with an embodiment of the present invention; Figure 26 illustrates an activity stack in accordance with an embodiment of the present invention; Figures 27a and 27b illustrate screens of a display device depicting a Z-order change command in accordance with an embodiment of the present invention; Figure 28 illustrates an activity stack in accordance with an embodiment of the present invention; Figures 29a and 29b illustrate screens of a display device depicting a Z-order change command in accordance with an embodiment of the present invention; Figure 30 illustrates an activity stack in accordance with an embodiment of the present invention; Figures 31a and 31b illustrate screens of a display device depicting a Z-order change command in accordance with an embodiment of the present invention; Figure 32 illustrates an activity stack in accordance with an embodiment of the present invention; Figures 33a and 33b illustrate screens of a display device depicting a Z-order change command in accordance with an embodiment of the present invention; Figure 34 illustrates an activity stack in accordance with an embodiment of the present invention; Figure 35 is a flowchart illustrating a method for controlling a display device in accordance with an embodiment of the present invention; Figures 36a, 36b, and 36c illustrate screens of a display device depicting a Z-order change command in accordance with an embodiment of the present invention; Figures 37a, 37b, and 37c illustrate activity stacks in accordance with embodiments of the present invention; Figures 38a, 38b, and 38c illustrate screens of a display device depicting a Z-order change command in accordance with an embodiment of the present invention; and Figures 39a, 39b, and 39c illustrate activity stacks in accordance with embodiments of the present disclosure. Figures 40a, 40b, 40c, 40d, 40e, 40f, 40g, 40h, 40i, 40j, and 40k illustrate a method for displaying an application execution window in accordance with an embodiment of the present invention; Figures 41a, 41b, 41c, 41d, 41e, and 41f illustrate activity stacks in accordance with various embodiments of the present invention; Figure 42 is a flowchart illustrating a method for running a display device application in accordance with an embodiment of the present invention; Figures 43a and 43b illustrate a method for controlling a display area of an application execution window using a center button in accordance with an embodiment of the present invention; Figures 44a, 44b, 44c, 44d, 44e, 44f, 44g, 44h, 44i, 44j, 44k, 44l, 44m, 44n, 44o, 44p, 44q, 44r, 44s, 44t, 44u, 44v, and 44w illustrate a method for running a plurality of applications in accordance with an embodiment of the present invention; Figures 45a, 45b, 45c, 45d, 45e, 45f, 45g, 45h, 45i, and 45j illustrate stacks of activities in accordance with embodiments of the present invention; Figure 46 is a flowchart illustrating a method for providing a user interface in which to run an application on a display device in accordance with an embodiment of the present invention; Figure 47 is a flowchart illustrating a method for running an application on a display device in accordance with an embodiment of the present invention; Figure 48 is a block diagram of a display device in accordance with an embodiment of the present invention; and Figures 49a, 49b, 49c, and 49d illustrate a method for displaying a button in accordance with an embodiment of the present disclosure.

[020] Throughout the drawings, identical reference numbers will be understood to refer to similar parts, components and structures.

MODE FOR THE INVENTION

[021] The following description with reference to the accompanying drawings is provided to aid in a comprehensive understanding of various embodiments of the present invention as defined by the claims and their equivalents. It includes several specific details to aid in this understanding, but these are to be regarded as illustrative only. Thus, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein may be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and brevity.

[022] The terms and words used in the following description and claims are not limited to bibliographic meanings, but are merely used by the inventor to allow a clear and consistent understanding of the present disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the present invention is provided for illustrative purposes only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

[023] It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a surface component" includes reference to one or more such surfaces.

[024] By the term "substantially" it is meant that the characteristic, parameter or value recited need not be achieved exactly, but that deviations or variations, including, for example, tolerances, measurement errors, limitations of measurement accuracy and others factors known to those skilled in the art, may occur in amounts that do not detract from the effect the trait is intended to provide.

[025] Although ordinal numbers such as first, second, and the like can be used to describe a number of components, these components are not limited by terms. Terms are used to distinguish a component from other components. For example, a first component may be referred to as a second component or vice versa within the scope and spirit of the present disclosure. The term "and/or" means the inclusion of a combination of a plurality of associated items described or one of the items.

[026] The technical terms used herein are provided to describe various embodiments and are not intended to limit the present disclosure. Here, singular expressions include plural expressions unless otherwise noted in the context. In this specification, the term "include" or "have" is not necessarily interpreted to include all features, numbers, steps, operations, components, parts, or a combination thereof described in the specification. On the contrary, it should be understood that there is the possibility of omitting or adding one or more features, numbers, steps, operations, components, parts, or combinations thereof.

[027] Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meanings as terms generally understood by those skilled in the art. In addition, terms defined in a general dictionary must be understood to have the same meanings as the contextual meanings of the related art. Unless definitively defined herein, the terms are not to be interpreted as ideally or overly formal meanings.

[028] Figure 1 is a block diagram of a display device according to an embodiment of the present disclosure.

[029] Referring to Figure 1, a display device 100 can be connected to an external device (not shown) via a mobile communication module 120, a communication sub-module 130, or a connector 165. The term "external device" " covers a variety of devices, such as another device (not shown), a portable phone (not shown), a smart phone (not shown), a tablet Personal Computer (PC) (not shown), a server (not shown) , and the like.

[030] The display device 100 includes a touch-sensitive screen 190 and a touch-sensitive screen controller 195. The display device 100 further includes a controller 110, the mobile communication module 120, the communication sub-module 130, a multimedia module 140, a camera module 150, a Global Positioning System (GPS) module 155, an input/output (I/O) module 160, a sensor module 170, a memory (storage) 175, and a power source 180. Communication sub-module 130 includes at least one of a wireless local area network (WLAN) module 131 and a short-range communication module 132. Multimedia module 140 includes at least one of a broadcast communication module 141, an audio playback module 142, and a video playback module 143. The camera module 150 includes at least one of a first camera 151 and a second camera 152, and the I/O module. The 160 includes at least one of buttons 161, a microphone 162, a speaker speaker 163, a vibration motor 164, connector 165, and a keyboard 166.

[031] The controller 110 may include a central processing unit (CPU) 111, a read-only memory (ROM) 112 that stores a control program for controlling the display device 100, and a random access memory (RAM) 113 which is used as a memory space for an operation performed by the display device 100. The CPU 111 may include one or more cores. CPU 111, ROM 112, and RAM 113 can be connected to each other via an internal bus.

[032] Controller 110 can control mobile communication module 120, communication sub-module 130, multimedia module 140, camera module 150, GPS module 155, I/O module 160, sensor 170, memory 175, power source 180, touchscreen 190, and touchscreen controller 195.

[033] Mobile communication module 120 links display device 100 to an external device via one or more antennas (not shown) by mobile communication under the control of controller 110. Mobile communication module 120 transmits signals wirelessly to or receive wireless signals from a handheld phone (not shown), a smart phone (not shown), a tablet PC (not shown), or another device (not shown) that has a phone number entry for the display device 100, for a voice call, a video call, a Short Message Service (SMS), or a multimedia messaging service (MMS).

[034] The communication sub-module 130 may include at least one of the WLAN module 131 and the short-range communication module 132.

[035] WLAN module 131 can be connected to the Internet under the control of controller 110 in a place where a wireless AP (not shown) is installed. The WLAN 131 module supports the Institute of Electrical and Electronics Engineers (IEEE) 802.11x WLAN standard. Short-range communication module 132 can perform short-range wireless communication between display device 100 and an imaging device (not shown) under the control of controller 110. Short-range communication may comply with Bluetooth, Infrared Data Association (IrDA), ZigBee, or the like.

[036] Display device 100 may include at least one mobile communication module 120, WLAN module 131, and short-range communication module 132 according to their capabilities. For example, display device 100 may include a combination of mobile communication module 120, WLAN module 131, and short-range communication module 132 according to its capabilities.

[037] Multimedia module 140 may include broadcast communication module 141, audio playback module 142, or video playback module 143. Broadcast communication module 141 may receive a broadcast signal (for (e.g. a television broadcast signal, a radio broadcast signal, or a data broadcast signal) and additional broadcast information (for example, an Electronic Program Guide (EPG) or an Electronic Services Guide (ESG) ) from a broadcast station via a broadcast communication antenna (not shown) under the control of controller 110. Audio playback module 142 can open a stored or received digital audio file (e.g., a with such an extension as mp3, wma, ogg, or wav) under the control of controller 110. Video playback module 143 can open a stored or received digital video file (for example, a file with an extension such as mpeg , mpg, mp4, avi, mov or avi) so b controlling controller 110. Video playback module 143 can also open a digital audio file.

[038] Multimedia module 140 may include audio playback module 142 and video playback module 143 without broadcast communication module 141. Alternatively, audio playback module 142 or video playback module video 143 of multimedia module 140 can be embedded in controller 110.

[039] The camera module 150 may include at least one of the first camera 151 and the second camera 152, to capture a still image or a video under the control of the controller 110. The first camera 151 or the second camera 152 may include a auxiliary light source (e.g. a flash (not shown)) to provide an intensity of light used to capture an image. The first camera 151 may be arranged on the front surface of the display device 100, while the second camera 152 may be arranged on the rear surface of the device 100. Alternatively, the first camera 151 and the second camera 152 may be arranged close together. to each other (for example, the distance between the first camera 151 and the second camera 152 can be between 1 centimeter and 8 centimeters) in order to capture a three-dimensional still image or video.

[040] The GPS module 155 can receive wave signals from a plurality of GPS satellites (not shown) in Earth orbit and calculate a position of the display device 100 based on the Time of Arrivals (ToAs) of satellite signals from the GPS satellites to the display device 100.

[041] The I/O module 160 may include at least one of the plurality of buttons 161, the microphone 162, the speaker 163, the vibration motor 164, the connector 165, and the keyboard 166.

[042] Buttons 161 may be formed on the front surface, a side surface, or the rear surface of a display device housing 100, and may include at least one of an on/lock button (not shown), a volume (not shown), a menu button, a home button, a back button, and a search button.

[043] Microphone 162 receives a voice or sound and converts the voice or sound received into an electrical signal under the control of controller 110.

[044] Speaker 163 can emit sounds corresponding to various signals (e.g., a wireless signal, a broadcast signal, a digital audio file, a digital video file, a photo, and the like) received from the audio module. mobile communication 120, communication sub-module 130, multimedia module 140, and camera module 150 to the outside of display device 100. Speaker 163 may emit sounds corresponding to functions (e.g., a sound button manipulation, a callback touch for a call, and the like) performed by the display device 100. One or more speakers 163 may be arranged in an appropriate display device housing position or positions 100.

[045] The vibration motor 164 can convert an electrical signal to a mechanical vibration under the control of the controller 110. For example, when the display device 100 receives an incoming voice call from another mobile device (not shown) in a vibration mode, the vibration motor 164 operates. One or more vibration motors 164 may be mounted within the display device housing 100. The vibration motor 164 may operate in response to a user's touch on the touch screen 190 and continuous movement of the touch on the touch screen. ring 190.

[046] Connector 165 can be used as an interface connecting display device 100 to an external device (not shown) or a power source (not shown). Connector 165 can transmit data stored in memory 175 to the external device via a cable connected to connector 165 or can receive data from the external device through the cable under the control of controller 110. Display device 100 can receive power or charge a battery (not shown) from the power source via the cable connected to connector 165.

[047] Keyboard 166 may receive key input from the user to control display device 100. Keyboard 166 includes a physical keyboard (not shown) formed on display device 100 or a virtual keyboard (not shown) displayed on the display 190. The physical keyboard cannot be provided according to the capacity or configuration of the display device 100.

[048] Sensor module 170 includes at least one sensor (not shown) for detecting a state of display device 100. For example, sensor module 170 may include a proximity sensor that detects whether the user is in close proximity to the device. sensor 100, an illuminance sensor that detects the amount of ambient light around the display device 100, or a motion sensor that detects movement of the display device 100 (e.g., a rotation, an acceleration, a vibration, or similar). At least one sensor can detect a state of the display device 100, generate a signal corresponding to the detected state, and transmit the generated signal to the controller 110. A sensor can be added to or removed from the sensor module 170 according to the capabilities of the sensor. display device 100.

[049] Memory 175 can store input/output signals or data according to the operations of mobile communication module 120, communication sub-module 130, multimedia module 140, camera module 150, GPS module 155 , I/O module 160, sensor module 170, and touch screen 190 under the control of controller 110. Memory 175 may store a control program for controlling display device 100 or controller 110, and apps.

[050] The term "memory" encompasses the memory 175, ROM 112 and RAM 113 within the controller 110, or a memory card (not shown) (e.g. an SD (Secure Digital) card or a memory card. memory) mounted on display device 100. The memory may include non-volatile memory, volatile memory, hard disk drive (HDD), or Solid State Drive (SSD).

[051] Power source 180 can supply power to one or more batteries (not shown) mounted in display device housing 100 under the control of controller 110. One or more batteries provide power to display device 100. In addition In addition, power source 180 may supply power received from an external power source (not shown) through the cable connected to connector 165 to display device 100.

[052] Touchscreen 190 can provide User Interfaces (UIs) corresponding to various services (eg, a call, data transmission, broadcast, photo, and others) to the user. Touchscreen 190 may transmit an analog signal corresponding to at least one touch on a user interface to touchscreen controller 195. Touchscreen 190 may receive at least one touch input via a of the user's body (e.g. a finger) or a touch input means (e.g. a stylus pen). Touch screen 190 may also receive a digital input signal corresponding to continuous movement of a touch between one or more touches. Touchscreen 190 can transmit an analog signal corresponding to continuous movement of the input touch to touchscreen controller 195.

[053] As used in this description, "touch" may include a non-contact touch (i.e., a detectable difference between the touchscreen 190 and a user part or a touch input means is 1 mm or less), and need not be limited to contact between the touch screen 190 and the user's body part or the touch input tool. A detectable gap for the touch screen 190 may vary depending on the capabilities or configuration of the display device 100.

[054] The touch screen 190 can be implemented, for example, as a resistive type, a capacitive type, an infrared type, or an acoustic wave type.

[055] Touchscreen controller 195 converts an analog signal received from touchscreen 190 to a digital signal (eg, X and Y coordinates). Controller 110 may control touchscreen 190 using the digital signal received from touchscreen controller 195. For example, controller 110 may control the selection or execution of a displayed shortcut icon (not shown). on the touchscreen 190, in response to a touch. Touchscreen controller 195 can be incorporated into controller 110.

[056] Figures 2a, 2b, 2c, 2d, 2e, 2f, 2g, 2h, 2i, 2j, and 2k illustrate a method of windowing in accordance with an embodiment of the present disclosure. It will be readily understood by those skilled in the art that a display device 200 can be any display device 100 illustrated in Figure 1, a standard TV, an Internet TV, a medical data display device, and the like. Therefore, insofar as it is equipped with a means for displaying a rendered image, any device can be used as a display device.

[057] Referring to Figure 2a, the display device 200 may define a plurality of window display areas 201, 202, 203, and 204 on a touch screen. For example, a controller (not shown) may configure a first window display area 201, a second window display area 202, a third window display area 203, and a fourth window display area 204. The controller may define a first boundary 211 between the first and second window display areas 201 and 202, a second boundary 212 between the third and fourth window display areas 203 and 204, a third boundary 213 between the first and third display areas 201 and 203, and a fourth boundary 214 between the second and fourth window display areas 202 and 204. The first and second boundary lines 211 and 212 may be connected in a single line, and the third and fourth lines of boundary 213 and 214 can be connected in a single line. The controller configures the first through fourth window display areas 201, 202, 203, and 204 such that they do not overlap with each other. Referring to Figure 2a, for example, the controller sets the first window display area 201 to an upper left corner, the second window display area 202 to an upper right corner, the third window display area 203 to an upper right corner. lower left corner, and the fourth window display area 204 in a lower right corner. The controller divides the screen into right and left halves by the first and second boundary lines 211 and 212 and divides the screen into upper and lower halves by the third and fourth boundary lines 213 and 214.

[058] The controller displays a center button 220 at an intersection where the first and second boundary lines 211 and 212 cross the third and fourth boundary lines 213 and 214. The center button 220 may be a function key that changes the size from an application display area or transitions the display device 200 to a window relocation mode.

[059] Controller controls display of a window in each of window display areas 201, 202, 203, and 204, to run an application in the window. For example, the controller controls to display a window in each of the window display areas 201, 202, 203, and 204, as illustrated in Figures 2b, 2c, 2d, 2e, 2f, 2g, 2h, 2i, 2j, and 2k

[060] A window can cover a running screen of a specific application and a title of the running application. Application-related objects can be displayed on the application run screen. Objects can take many forms, such as text, a picture, an icon, a button, a checkbox, a photo, a video, a web page, a map, and so on. When a user taps an object, a function or event corresponding to the tapped object can be executed in the application. An object can be called a view according to an operating system (OS). The title bar can include at least one control key that controls a window's display. For example, the control key can at least include a minimize window button, a maximize window button, and a close window button.

[061] Applications are programs written independently by a display device manufacturer 200 or application developers. Thus, running one application does not require preliminary execution of another application. Even when one application terminates, another application may run continuously.

[062] Compared to a composite function application (or a dual application) designed by adding some functions (e.g. a memory function, a message transmit/receive function, and so on) available from other applications to an application (for example, a video application), an application is configured independently. The composite function app is a single app that is configured to include multiple roles, unlike existing apps. Therefore, the composite function app only provides limited functions like the existing apps and a user must purchase such a new composite function app additionally.

[063] With reference to Figure 2b, the controller controls display of a first window 230 to run a launcher application, application L in the first window display area 201. The launcher application, application L displays available application icons 231, 232 , 233, 234, 235, 236, 237, and 238, as illustrated in Figure 2b. After receiving an application run command by tapping one of application icons 231, 232, 233, 234, 235, 236, 237, and 238, the application launcher, application L displays an application corresponding to the icon tapped on a from the first to the fourth display areas 201, 202, 203 and 204.

[064] Figures 3a, 3b, 3c, 3d, 3e, 3f, 3g, 3h, and 3i illustrate stacks of activities managed on a display device in accordance with embodiments of the present disclosure.

[065] Referring to Figure 3a, the controller generates and administers an initiator application stack 301 in an activity stack in response to the execution of the initiator application.

[066] Referring to Figures 2C and 2D, user 1 can touch an icon 232 representing application B. When icon 232 representing application B is touched, the controller controls display of a second window 240 in the second window display area 202 , where application B runs. The controller can display windows in the first through fourth window display areas 201, 202, 203, and 204 in order. For example, the controller can control display of new windows in a clockwise direction from the second, third, and fourth window display areas 202, 203, and 204. The clockwise window display order is an example of a window display control. new windows and therefore the controller can control display of new windows in a counterclockwise direction. The display order of new windows in window display areas 201, 202, 203, and 204 can be changed.

[067] Figure 3b illustrates a stack of activities corresponding to the windows shown in Figure 2d. The controller generates an application stack B 302 on the activity stack in response to the execution of application B. The controller places the stack of the last executed application B 302 on the initiator application stack 301. This may imply that the Z-order (which may also be described as an order, rank, or priority) of application B is greater than the Z-order of the initiating application, application L.

[068] Referring to Figure 2e, user 1 can tap an icon 233 corresponding to application C.

[069] Figure 3c illustrates a stack of activities corresponding to the windows illustrated in Figure 2e. Since user 1 enters an application run command to the initiating application, application L, as illustrated in Figure 2e, it is noted from Figure 3c that the Z-order of the initiating application, application L is greater than the Z order of application B.

[070] Referring to Figure 2f, when the icon 233 representing application C is touched, the controller controls display of a third window 250 in the fourth window display area 204, in which application C is executed.

[071] Figure 3d illustrates a stack of activities corresponding to the windows illustrated in Figure 2f. The controller generates an application stack C 303 in the activity stack in response to the execution of application C. The controller places the stack of the last executed application C 303 on the initiator application stack 301. This may imply that the Z-order of application C is greater than the Z order of the initiator application, application L.

[072] With reference to Figure 2g, user 1 can touch an icon 234 representing application D.

[073] Figure 3e illustrates a stack of activities corresponding to the windows illustrated in Figure 2g. Once the user enters an application run command to the initiating application, application L, as illustrated in Figure 2g, it is noted from Figure 3e that the Z-order of the initiating application, application L is greater than the C application Z order.

[074] Referring to Figure 2h, when the icon 234 representing application D is touched, the controller controls display of a fourth window 260 in the third window display area 203, in which application D runs.

[075] Figure 3f illustrates a stack of activities corresponding to the windows illustrated in Figure 2h. The controller generates an application stack D 304 in the activity stack in response to the execution of application D. The controller places the stack of last executed application D 304 on the initiator application stack 301. This may imply that the Z-order of application D is higher than the Z order of the initiator application, application L.

[076] With reference to Figure 2i, user 1 can handle application B.

[077] Figure 3g illustrates a stack of activities corresponding to the windows illustrated in Figure 2i. The controller places application B's stack 302 on top of the activity stack in response to user input to application B.

[078] Referring to Figure 2j, user 1 can touch an icon 235 representing application E.

[079] Figure 3h illustrates a stack of activities corresponding to Figure 2j. Once user 1 enters an application execution command for the initiating application, application L as illustrated in Figure 2j, it is noted from Figure 3h that the Z order of the initiating application, application L is greater than the order D application Z.

[080] Referring to Figure 2k, when the icon 235 representing application E is touched, the controller controls display of a fifth window 270 in the fourth window display area 204, in which application E runs. In the absence of an empty window display area, the controller can refer to the activity stack illustrated in Figure 3h. The controller can determine the application having the lowest Z-order in the activity stack. For example, the controller might determine that application C's Z-order is the lowest in the activity stack of Figure 3h. The controller controls fifth window display 270 running application E, substituting for application C having the lowest order Z, in fourth window display area 204.

[081] Figure 3i illustrates a stack of activities corresponding to the windows illustrated in Figure 2k. The controller generates an application stack E 305 in the activity stack in response to the execution of application E. The controller places the stack of the last executed application E 305 on the initiator application stack 301. This may imply that the Z-order of application E is greater than the Z order of the initiator application, application L.

[082] Figure 4a represents a flowchart illustrating a method for controlling a display device in accordance with an embodiment of the present disclosure.

[083] Referring to Figure 4a, the display device can run a plurality of applications in operation S401. For example, the display device can run an application in response to an application run command triggered by a user tapping an icon representing the application. The display device, particularly a display device window manager, can generate a window in which the application runs.

[084] The display device can determine an arrangement for arranging the window. The arrangement defines the window display areas in which windows can be arranged. For example, two modes are available for arrangement, namely a split mode and a freestyle mode.

[085] In split mode, a screen is split in such a way that a plurality of windows are presented without overlapping. For example, if the display device displays first and second windows, the display can split a screen, such as a touchscreen, into a defined arrangement and define the split-screen parts as window display areas. The display device can display one window in each window display area. Since each window display area is a screen segment, the display device can display a plurality of windows without overlapping.

[086] The display device can allocate a plurality of windows to a window display area in split mode. For example, the display device can assign the first and second windows to the first window display area. In this case, the display device can compare the Z orders (orders, sorts, positions in a stack) of the first and second windows. If the Z-order of the first window is greater than the Z-order of the second window, the display device can display the first window in the first window display area. In this case, although the display device generates the second window as laid out in the first window display area, the display device does not display the second window in the first window display area.

[087] On the other hand, a plurality of windows can be displayed superimposed according to their display priority levels in freestyle mode. For example, if the first window display area overlaps with the second window display area, the display device can compare the Z orders of the first and second windows. The Z-order of a window can refer to the window's display ordering. For example, if the Z-order of the first window is greater than the Z-order of the second window, the display device can control the display of the first window in the overlapping part instead of the second window.

[088] In split mode, various arrangements are available, such as a top/low 2 area split arrangement, a left/right 2 area split arrangement, a 3 area split arrangement, a 4 areas, and the like. The display device can determine whether the window arrangement is in split mode or freestyle mode in S405 operation. If the arrangement is in split mode, the display device can still determine whether the arrangement is the top/bottom 2 area split arrangement, the left/right 2 area split arrangement, the 3rd split arrangement areas, or the 4-area division arrangement.

[089] Once the array mode is determined in operation S405, the display device can determine a window position in the array in operation S407. In the case of 2 top/bottom area arrangement, the display device can determine to arrange the first and third windows in an upper window display area and the second window in a lower window display area. Alternatively, in freestyle mode, the display device can determine a coordinate area for the first window and a coordinate area for the second window.

[090] The display device can determine the Z orders of a plurality of applications in operation S409 and can display a plurality of windows based on the Z orders of the applications in operation S411. For example, in the case of 2 top/bottom area split mode, the display device can compare the Z orders of the first and third windows. In addition, the display device can control display of a window that has a relatively high Z-order in a corresponding window display area. In freestyle mode, the display device can compare the Z-orders of the first and second windows and can control display of a window that has a relatively high Z-order in an overlapping area.

[091] Figure 4b is a flowchart illustrating a method for controlling a display device in accordance with an embodiment of the present disclosure.

[092] Referring to Figure 4b, the display device can run a plurality of applications in operation S401. An application run command can be triggered by, for example, a drag gesture of dragging an icon representing an application to a point where a window should be displayed for the application. Drag gesture input is an example of an app run command, and therefore apps can be run in a variety of ways. Those skilled in the art will readily understand that the present disclosure is not limited to a specific application execution method.

[093] The display device can determine whether a current arrangement is in freestyle mode in S421 operation. In the case of the freestyle mode arrangement, the display device can determine the Z-order of each of the windows in which the plurality of applications run in operation S423. The display device can display the overlapping windows according to the Z orders of windows in S425 operation.

[094] In the case of split mode arrangement in operation S421, the display device can arrange windows in window display areas in operation S431. In addition, the display device can determine the Z order of windows in each window display area in operation S433. For example, the display device can determine the Z-orders of the windows, as shown in Table 1. Table 1

[095] As described above, the display device can control display of window A having a relatively high Z order, not window E, in a first window display area. The display device can control the display of window D having a relatively high Z order, not window B, in a second windowed display area. In addition, the display device can display window C in a third window display area and window F in a fourth window display area. For example, the display device may display a window having a higher Z-order in each window display area among the windows allocated to the window display area in operation S435.

[096] Figure 5 illustrates a window display ordering (Z-order) according to an embodiment of the present disclosure.

[097] With reference to Figure 5, the Z order of a screen can be divided into N layers and an N-th layer can be a top layer placed on top of an (N-1)-th layer. A window can exist on each layer and an application can run in the window. For example, after running a first application, the first application runs in a first-tier window. After a second application runs, the second application runs in a second-tier window, and after a third application runs, the third application runs in a third-tier window. Thus, the first, second, and third layers are created hierarchically. The last layer can be created on top of the layer stack and therefore can be displayed on the top layer of the canvas. For example, a plurality of windows (a) through (d) may be displayed superimposed on a main screen. For example, the first window (a) is displayed superimposed over the second, third and fourth windows (b), (c) and (d), the second window (b) is displayed superimposed on the third and fourth windows (c) and (d), and the third window (c) is displayed superimposed on the fourth window (d). For example, when the plurality of windows (a) to (d) are shown superimposed, the display order of windows (a) to (d) is the Z orders of windows (a) to (d). The Z-order might be the order of displaying windows about the Z axis. A layer viewer (e) might be a screen that displays the Z-orders of windows hierarchically. The Z order can be referred to as a display order.

[098] Figures 6a, 6b, 6c, and 6d illustrate a method of running an application in accordance with an embodiment of the present disclosure. More particularly, Figures 6a, 6b, 6c, and 6d illustrate a method for running applications in a freestyle mode arrangement.

[099] Referring to Figures 6a, 6b, 6c, and 6d, a display device 600 features a window display area 620. The display device 600 features a tray 610 that contains available application icons 611, 612, 613 , 614, 615, 616, and 617 to the left of the window display area 620. A user 10 can manipulate the display device 600 to run a first application A1. For example, user 10 can make a drag gesture 625 of dragging an icon 611 representing the first application A1 to a first point in the window display area 620 in Figure 6b. The display device 600 may display a first window 630 at the first point in the window display area 620, in response to the drag gesture 625 to run the first application A1 in the first window 630. The first window 630 may be presented in a size and standard format or in a user-defined size and format 10 prior to termination.

[100] User 10 can manipulate display device 600 to additionally run a third A3 application. For example, user 10 may display a drag gesture 635 of dragging an icon 613 representing the third application A3 to a second point in the window display area 620 as illustrated in Figure 6c. The display device 600 may display a third window 640 at the second point in the window display area 620 in response to the execution command input, i.e., the drag gesture 635 to run the third application A3 in the third window 640. third window 640 can be displayed in a standard size and format or in a user defined size and format 10 before termination. Since the third window 640 is the last window to which user 10 has applied a gesture input, a controller (not shown) can assign a higher task priority level to the third application A3 than the first application A1. In this way, the controller can control the display of the third application A3 over the first application A1.

[101] Figure 7 is a flowchart illustrating a method for controlling a display device in accordance with an embodiment of the present disclosure.

[102] Referring to Figure 7, the display device can display at least one icon representing an application in S701 operation. For example, the display device may display a tray that contains at least one icon on a portion of a touchscreen.

[103] When a user drags an icon to a first point where a window should be placed, the display device can receive drag gesture input in S703 operation. The display device can recognize the drag gesture from the icon to the first point as a command to run an application corresponding to the icon. More particularly, the display device can determine the position of the first point where the drag gesture ended, in an arrangement in operation S705. For example, if the split mode has been set to the array, the display device can determine a pane to which the first point corresponds in the array.

[104] The display device can determine at least one of the window dimension and position according to the position of the first point on the S707 running array. The display device can display the window according to the size and/or position determined in the S709 operation.

[105] Figures 8a, 8b, 8c, 8d, 8e, 8f, 8g, 8h, 8i, 8j, 8k, 8l, and 8m illustrate a method for displaying a plurality of windows in accordance with an embodiment of the present disclosure.

[106] Referring to Figures 8a, 8b, 8c, 8d, 8e, 8F, 8g, 8h, 8i, 8j, 8k, 8l, and 8m, a display device 800 displays a menu screen 817. The menu screen 817 may be a launcher program run screen and may include icons representing applications. In addition, the menu screen 817 can include information about a current weather and can even include widgets. Display device 800 displays a tray containing 810 available icons 811, 812, 813, 814, 815, and 816 to the left of a touch screen.

[107] User 10 can manipulate display device 800 to run a first application A, as illustrated in Figure 8b. For example, user 10 can tap icon 811 representing the first application A and drag tapped icon 811 to menu screen 817 as illustrated in Figure 8c. A controller (not shown) can control the display of the 811 icon at the dragged point. The controller can even control the display of a ghost view 818 at the dragged point. Phantom view 818 refers to a preview of the size and shape of a window in which the first application A will run so that the user 10 can select a window position. Because no windows were displayed, the controller may display the 818 ghost view in full screen. As described below, the controller can control display of a full-screen phantom view in the absence of any windows already displayed on the touchscreen. If a single window is already displayed on the touchscreen, the controller can display the ghost view in a shape and size that matches one of the halves of the touchscreen. If two windows are already displayed on the touchscreen, the controller can display the ghost view in a shape and size corresponding to half of one of the two windows on the touchscreen. If three windows are already displayed on the touchscreen, the controller can display the ghost view in a shape and size that is half the largest of the three windows.

[108] The controller may recognize the previous drag gesture as a command to run a new application. The controller can generate a first window 819 to run the first application A. The controller can control the display of the first window 819 in full screen, as illustrated in Figure 8d.

[109] User 10 may manipulate display device 800 to additionally run a second application B. For example, user may tap icon 812 representing second application B as illustrated in Figure 8e and drag tapped icon 812 to a lower part of the first window 819 as illustrated in Figure 8f. The controller can control the display of the 812 icon at the dragged point. Also, the controller can control display of a ghost view 823 at the dragged point. As described before, since the single window 819 is already displayed on the touchscreen, the controller can control the display of the ghost view 823 in a shape and size corresponding to half of the touchscreen. Although not shown, if the user 10 drags the tapped icon 812 to a top of the touchscreen, the controller controls display of the phantom view 823 on an upper half of the touchscreen. Showing the phantom view on a lower half of the touchscreen is just an example of displaying the phantom view, so the controller can split the touchscreen into right and left halves and can control the phantom view display on a of the left and right halves of the touchscreen.

[110] If the user finishes dragging on a lower part of the touch screen, as illustrated in Figure 8f, the controller determines that a new application execution command has been received. As illustrated in Figure 8g, the controller controls display of a second window 830 on the lower half of the touchscreen in correspondence with the ghost view 823 illustrated in Figure 8f. Furthermore, the controller shrinks the first window 819 in size and shape to a first window 820 so that the first window 820 can be displayed in the upper half of the touch screen. The controller generates and displays a central button 825 on the boundary between the first and second windows 820 and 830.

[111] User 10 can manipulate display device 800 to additionally run a third application C. For example, user can tap icon 813 representing third application C as illustrated in Figure 8h and drag tapped icon 813 to a right part of the first window 820 as illustrated in Figure 8i. The controller controls display of the 813 icon at the dragged point. In addition, the controller can control display of a ghost view 827 at the dragged point. As described before, since the two windows 820 and 830 are already presented on the touchscreen, the controller can control the display of the ghost view 827 in a shape and size that corresponds to one half of the first window 820. Although not shown , if user 10 drags the tapped icon 813 to the left part of the first window 820, the controller controls display of the ghost view 827 in a left half of the first screen 820. Displaying the ghost view 827 in the right half of the first window 820 is merely an example of displaying the ghost view and so the controller can split the first window 820 into two upper and lower halves and can control the display of the ghost view 827 in one of the upper and lower halves of the first screen 820. Display the ghost view 827 in one half of the first window 820 is another example of displaying the ghost view. The controller can determine the size and shape of the ghost view 827 relative to the center button 825 and display the ghost view 827 accordingly.

[112] If the user finishes dragging the right part of the first window 820 as illustrated in Figure 8i, the controller determines that a new application execution command has been received. As illustrated in Figure 8j, the controller controls display of a third window 840 on the right half of the first screen 820, in correspondence with the ghost view 827 illustrated in Figure 8i. Alternatively, the controller can control the display of the third window 840, in correspondence with the position of the central button 825. Thus, when new applications are selected for execution, portions of the screen can be progressively subdivided so as to allocate a respective portion of the screen to every application run.

[113] Also, the controller shrinks the first window 820 in size and shape in correspondence with the creation of the third window 840. For example, the controller can control the display of the first window 820 in a different area than the display area of the third window 840.

[114] User 10 can manipulate display device 800 to additionally run a fourth application D. For example, user can tap icon 814 representing fourth application D as illustrated in Figure 8k and drag tapped icon 814 to a right part of the second window 830 as illustrated in Figure 81. The controller controls display of the 814 icon at the dragged point. Additionally, the controller can control display of a ghost view 831 at the dragged point. As described before, since the three windows 820, 830 and 840 are already displayed on the touchscreen, the controller can control the display of the ghost view 831 in a size and shape that corresponds to one half of the second window 830. is not shown, if user 10 drags the tapped icon 814 to a left part of the second window 830, the controller controls the display of the ghost view 831 on a left half of the second screen 830. Display the ghost view 831 on a right half of the screen. second window 820 is merely an example of displaying the ghost view, so the controller can split the second window 830 into two halves and control the top and bottom display of the ghost view 831 in one of the upper and lower halves of the second screen 830. Display the ghost view 831 in one half of the second window 830 is just another example of displaying the ghost view. The controller can determine the size and shape of the ghost view 831 relative to the center button 825 and display the ghost view 831 accordingly.

[115] If user 10 finishes dragging the right part of the second window 830 as illustrated in Figure 81, the controller determines that a new application execution command has been received. As illustrated in Figure 8j, the controller controls display of a fourth window 850 on the right half of the second screen 830 in correspondence with the ghost view 831 illustrated in Figure 8l. Alternatively, the controller may control the display of the fourth window 850 in correspondence with the position of the center button 825.

[116] In addition, the controller shrinks the second window 830 in size and shape in correspondence with the creation of the fourth window 850.

[117] As described above, the display device can control display of a window in a window display area where a drag gesture ends. In Figures 8a, 8b, 8c, 8d, 8e, 8F, 8g, 8h, 8i, 8j, 8k, 8l, and 8m, windows are displayed at the same size in different positions. With reference to Figures 9a, 9b, 9c, 9d, 9e, 9f, 9g, 9h, 10a, 10b, 10c, 10d, 11a, 11b, 11c, 12a, 12b, 12c, 13a, 13b, 13c, 14a, 14b, 14c, 15a, 15b, 15c, 16a, 16b, 16c, 16d and 17, various modes of configuring windows in different sizes in different positions will be described below.

[118] Figures 9a, 9b, 9c, 9d, 9e, 9f, 9g, and 9h illustrate arrangements in accordance with embodiments of the present disclosure.

[119] Figure 9a illustrates a full screen arrangement for a case where the split mode is not set. A display device defines a first window display area 901 over an entire screen in Figure 9a.

[120] Figure 9b illustrates an input area 902 corresponding to the first window display area 901.

[121] Figure 9c illustrates a screen arrangement in a 2 top/bottom area split mode. In Figure 9c , the display device can divide the screen into upper and lower area and define first and second window display areas 911 and 912 in the upper and lower area, respectively.

[122] Figure 9d illustrates input areas in 2 top/down area split mode. A first input area 913 may correspond to the first window display area 911 and a third input area 915 may correspond to the second window display area 912. A second input area 914 may correspond to the boundary between the first and second areas. window display 911 and 912. For example, when a user makes a drag gesture of dragging an icon to the first input area 913, the display device may display a window in the first window display area 911 illustrated in Figure 9c. For example, when the user drags an icon to the third input area 915, the display device may display a window in the second window display area 912 illustrated in Figure 9c. For example, when the user drags an icon to the second input area 912, the display device may display a window over the entirety of the first and second window display areas 911 and 912 illustrated in Figure 9c.

[123] Figure 9e illustrates a screen arrangement in a 2 left/right area split mode. In Figure 9e , the display device can divide the screen into right and left area and define first and second window display areas 921 and 922 in the left and right area respectively.

[124] Figure 9f illustrates input areas in left/right 2 area split mode. A first input area 923 may correspond to the first window display area 921 and a third input area 925 may correspond to the second window display area 922. A second input area 924 may correspond to the boundary between the first and second areas window display 921 and 922. For example, when a user makes a drag gesture of dragging an icon to the first input area 923, the display device may display a window in the first window display area 921 illustrated in Figure 9 and. For example, when the user drags an icon to the third input area 925, the display device may display a window in the second window display area 922 illustrated in Figure 9e. For example, when the user drags an icon to the second input area 924, the display device may display a window over the entirety of the first and second window display areas 921 and 922 illustrated in Figure 9e.

[125] Figure 9g illustrates a 4-area split mode arrangement in accordance with an embodiment of the present invention and Figure 9h illustrates input areas defined in accordance with the 4-area split mode arrangement illustrated in Figure 9g .

[126] Referring to Figures 9g and 9h, the display device defines first through fourth window display areas 931, 932, 933, and 934. Therefore, the user can manipulate the display device to run a window in any one of the first through fourth window display areas 941, 942, 943, and 944. For example, when the user drags an icon representing an application to the second window display area 932, the display device can arrange and display a window in the second window display area 932. If the user finishes the drag gesture on the boundary between the first and second display areas 931 and 932, the display device can display a window over the entirety of the first and second display areas 931 and 932. For example, the display device may define a first input area 941 corresponding to the first window display area 931 and a second input area 942 corresponding to the second area of window display 931 and 932. window display 932. The display device may further define a fifth input area 945 on the boundary between the first and second window display areas 931 and 932. Likewise, the display device may define third and fourth input areas 943 and 944 corresponding to the third and fourth window display areas 933 and 934, respectively. The display device may further define a sixth input area 946 on the boundary between the first and third window display areas 931 and 933, a seventh input area 947 on the boundary between the second and fourth window display areas 932 and 934 , and an eighth input area 948 on the boundary between the third and fourth window display areas 933 and 934. The display device may further define a ninth input area 949 at an intersection where the first to fourth window display areas 931, 932, 933 and 934 meet. When the drag gesture ends in a specific input area, the display device determines a window display area to display a window based on a mapping relationship illustrated in Table 2. Table 2

[127] As described above, the display device can define an input area to determine an application display area where a drag gesture ends. More particularly, the display device may define an input area corresponding to the boundary between a plurality of window display areas or an input area corresponding to an intersection where a plurality of window display areas meet. When a drag gesture ends in an input area corresponding to the boundary between the window display areas, the display device can display a window over the entirety of the window display areas. When a drag gesture ends at an input area corresponding to an intersection where a plurality of window display areas meet, the display device can display a window over the entirety of the window display areas. The display device can display a window in a different position at a different size. With reference to Figures 10a, 10b, 10c, 10d, 11a, 11b, 11c, 12a, 12b, 12c, 13a, 13b, 13c, 14a, 14b, 14c, 15a, 15b, 15c, 16a, 16b, 16c, 16d and 17, the above-described configurations of windows viewed at different positions at different sizes are described in greater detail. More particularly, Figures 10a, 10b, 10c, 10d, 11a, 11b, 11c, 12a, 12b, 12c, 13a, 13b, 13c, 14a, 14b, 14c, 15a, 15b, 15c, 16a, 16b, 16c, 16d and 17 illustrate arrangements in a 4-area split mode. Thus, Figures 9g and 9h will also be referred to in the following description.

[128] Figures 10a, 10b, 10c, and 10d illustrate screens of a display device in accordance with embodiments of the present disclosure.

[129] Referring to Figures 10a, 10b, 10c, and 10d, a controller controls display of a window display area 1000 and a tray 1010 that contains available icons 1011, 1012, 1013, 1014, 1015, 1016, and 1017 representing applications. The controller can display tray 1010 all the time. Alternatively, the controller may display tray 1010 only upon receipt of a tray recall command. The tray call command can be generated in response to a light edge tap received from a left edge of the touch screen. Those skilled in the art will readily understand that the present disclosure is not limited to input types that trigger a tray call command. The display device is assumed to be displaying a first window that runs an application A in the window display area 1000.

[130] Referring to Figure 10b, user 10 can display a drag gesture 1021 of dragging icon 1016 representing application F to a first point 1027 at a lower part of window display area 1000. In Figure 10c, the controller can determine a window display area. In the case of a 4-area array, the controller can determine an input area in which the drag gesture 1021 ends. For example, if the first point 1027 is located in the eighth input area 948 of Figure 9h, the controller may determine to display an F window 1024 over the entirety of the third and fourth window display areas 933 and 934, as illustrated in Table 2. The controller can then display a 1023 ghost view in the determined areas.

[131] User 10 can determine whether a window will be displayed in a desired position by viewing ghost view 1023. User 10 can release drag gesture 1021 and window F 1024 can be displayed over the entirety of the third and fourth window display areas 933 and 934, as illustrated in Figure 10d. As the F 1024 window is displayed, the controller can reduce the size of the A 1000 window by half and display the A 1000 window collapsed. The controller can gradually decrease the A 1000 window in the same horizontal-vertical relationship or in a new horizontal-vertical relationship.

[132] Figures 11a, 11b, and 11c illustrate screens of a display device in accordance with embodiments of the present disclosure. More particularly, Figures 11a, 11b and 11c illustrate an operation subsequent to the operation of Figures 10a, 10b, 10c, and 10d.

[133] Referring to Figure 11a, the display device displays window A 1000 and window F 1024 respectively at the top and bottom of the screen in split mode. User 10 may manipulate the display device to additionally run application E. User 10 may make a drag gesture 1032 by dragging icon 1015 representing application E to a second point 1033.

[134] Referring to Figures 11b and 11c, the controller may determine an input area corresponding to the second point 1033. If the controller determines that the second point 1033 corresponds to the eighth input area 948 illustrated in Figure 9h, the controller may determine display an E window 1034 over the entirety of the third and fourth window display areas 933 and 934, as illustrated in Table 2. In this way, the controller can display the determined window display areas as a ghost view 1031.

[135] User 10 can determine whether the window will be displayed in a desired position by viewing the ghost view 1031. User 10 can release the drag gesture 1032. Window E 1034 can be displayed over the entirety of the third and fourth window display areas 933 and 934.

[136] Figures 12a, 12b, and 12c illustrate screens of a display device in accordance with embodiments of the present disclosure. More particularly, Figures 12a, 12b and 12c illustrate an operation subsequent to the operation of Figures 11a, 11b and 11c.

[137] Referring to Figure 12a, the display device presents a window 1000 and window E 1034 respectively at the top and bottom of the screen in split mode. User 10 may manipulate the display device to additionally run application L. User 10 may make a drag gesture 1041 of dragging icon 1017 representing application G to a third point 1042.

[138] Referring to Figures 12b and 12c, the controller may determine an input area corresponding to the third point 1042. If the controller determines that the third point 1042 corresponds to the ninth input area 949 illustrated in Figure 9h, the controller may determine display an L window 1044 over the entirety of the first to fourth window display areas 931-934, as illustrated in Table 2. In this way, the controller can display the determined window display areas as a ghost view 1043.

[139] User 10 can determine whether the window will be displayed in a desired position by viewing ghost view 1043. User 10 can release drag gesture 1042. G window 1044 can be displayed full screen as illustrated in Figure 12c.

[140] Figures 13a, 13b, and 13c illustrate screens of a display device in accordance with embodiments of the present disclosure. More particularly, Figures 13a, 13b and 13c illustrate an operation subsequent to the operation of Figures 12a, 12b and 12c.

[141] Referring to Figures 13a, 13b, 13c e, the display device is displaying window G 1044. User 10 can make a drag gesture 1051 of dragging icon 1012 representing application B to a fourth point 1052 in a bottom of the G 1044 window in Figure 13b. When the controller determines that the fourth point 1052 corresponds to the eighth input area 948 illustrated in Figure 9h , the controller may determine to display a window B 1054 over the entirety of the third and fourth window display areas 933 and 934, as illustrated in Fig. Table 2. In this way, the controller can display the determined window display areas as a 1053 ghost view.

[142] User 10 can determine whether the window will be displayed in a desired position by viewing the ghost view 1053. User 10 can release the drag gesture 1052. Window B 1054 can be displayed over the entirety of the third and fourth window display areas 933 and 934, as illustrated in Figure 13c. As the window B 1054 is displayed, the controller can shrink the window G 1044 to half the screen and display the window G 1044 collapsed in the upper half of the screen.

[143] Figures 14a, 14b, and 14c illustrate screens of a display device in accordance with embodiments of the present disclosure. More particularly, Figures 14a, 14b and 14c illustrate an operation subsequent to the operation of Figures 13a, 13b and 13c.

[144] Referring to Figure 14a, the display device shows window G 1044 and window B 1054 respectively at the top and bottom of the screen in split mode. User 10 may manipulate the display device to additionally run application C. User 10 may make a drag gesture 1061 of dragging the icon representing application B 1013 to a fifth point 1062.

[145] Referring to Figures 14b and 14c, the controller may determine an input area corresponding to the fifth point 1062. If the controller determines that the fifth point 1062 corresponds to the second input area 942 illustrated in Figure 9h, the controller may determine display a C window 1064 in the second window display area 932, as illustrated in Table 2. In this way, the controller can display the determined window display area as a ghost view 1063.

[146] User 10 can determine whether the window will be displayed in a desired position by viewing the ghost view 1063. User 10 can release the drag gesture 1061. Window C 1064 can be displayed in the second window display area 932 as illustrated in Figure 14c.

[147] Figures 15a, 15b, and 15c illustrate screens of a display device in accordance with embodiments of the present disclosure. More particularly, Figures 15a, 15b, and 15c illustrate an operation subsequent to the operation of Figures 14a, 14b, 14c e.g.

[148] Referring to Figure 15a, the display device shows L-window 1044, B-window 1054, and C-window 1064 in a 3-area split mode. User 10 may manipulate the display device to additionally run application D. User 10 may make a drag gesture 1071 of dragging the icon representing application D 1014 to a sixth point 1072.

[149] Referring to Figures 15b and 15c, the controller may determine an input area corresponding to the sixth point 1072. If the controller determines that the sixth point 1072 corresponds to the fourth input area 944 illustrated in Figure 9h, the controller may determine display a window D 1074 in the fourth window display area 934, as illustrated in Table 2. In this way, the controller can display the determined window display area as a ghost view 1073.

[150] User 10 can determine whether the window will be displayed in a desired position by viewing the ghost view 1073. User 10 can release the drag gesture 1071. Window D 1074 can be displayed in the fourth window display area 934, as illustrated in Figure 15c.

[151] Figures 16a, 16b, 16c and 16d illustrate screens of a display device in accordance with embodiments of the present disclosure.

[152] Figure 16a illustrates screens of a display device in accordance with an embodiment of the present disclosure. More particularly, Figure 16a illustrates an operation subsequent to the operation of Figures 15a, 15b and 15c.

[153] Referring to Figure 16a, the display device displays window G 1044, window B 1054, window C 1064, and window D 1074 in a 4-area split mode. User 10 can manipulate the display device to additionally run application H. User 10 can make the drag gesture of dragging an icon representing application 1018 H to a seventh point 1081.

[154] Referring to Figure 16a, the controller may determine an input area corresponding to the seventh point 1081. If the controller determines that the seventh point 1081 corresponds to the fifth input area 945 illustrated in Figure 9h, the controller may determine to display a window H 1083 in the first and second window display areas 931 and 932, as illustrated in Table 2. In this way, the controller can display the determined window display areas as a ghost view 1082. Icons 1015, 1016, 1017, 1018, 1019, 1020, and 1021 representing applications E to K can be arranged in tray 1010. User 10 can introduce, for example, a drag gesture up across tray 1010 so that hidden icons 1018, 1019, 1020 , and 1021 representing applications H through K may appear in tray 1010.

[155] User 10 can determine whether the window will be displayed in a desired position by viewing the ghost view 1082. User 10 can release the drag gesture. The H window 1083 may be displayed in the first and second window display areas 931 and 932, as illustrated in Figure 16a.

[156] Figure 16b illustrates screens of a display device in accordance with an embodiment of the present disclosure. More particularly, Figure 16b illustrates an operation subsequent to the operation of Figures 15a, 15b and 15c.

[157] Referring to Figure 16b, the display device displays window G 1044, window B 1054, window C 1064, and window D 1074 in 4-area split mode. User 10 may manipulate the display device to additionally run application H. User 10 may make a drag gesture by dragging icon 1018 representing application H to an eighth point 1084.

[158] Referring to Figure 16b, the controller may determine an input area corresponding to the eighth point 1084. If the controller determines that the eighth point 1084 corresponds to the sixth input area 946 illustrated in Figure 9h, the controller may determine to display a H window 1086 in the first and third window display areas 931 and 933, as illustrated in Table 2. In this way, the controller can display the determined window display areas as a ghost view 1085.

[159] User 10 can determine whether the window will be displayed in a desired position by viewing the ghost view 1085. User 10 can release the drag gesture. The H window 1086 may be displayed in the first and third window display areas 931 and 933, as illustrated in Figure 16b.

[160] Figure 16c illustrates screens of a display device in accordance with an embodiment of the present disclosure. More particularly, Figure 16c illustrates an operation subsequent to the operation of Figures 15a, 15b and 15c.

[161] Referring to Figure 16c, the display device displays window G 1044, window B 1054, window C 1064, and window D 1074 in 4-area split mode. User 10 can manipulate the display device to additionally run application H. User 10 can make the drag gesture of dragging icon 1018 representing application H to a ninth point 1087.

[162] With reference to Figure 16c, the controller may determine an input area corresponding to the ninth point 1087. If the controller determines that the ninth point 1087 corresponds to the eighth input area 948 illustrated in Figure 9h, the controller may determine to display a H window 1089 in the third and fourth window display areas 933 and 934, as illustrated in Table 2. In this way, the controller can display the determined window display areas as a ghost view 1088.

[163] User 10 can determine whether the window will be displayed in a desired position by viewing the ghost view 1088. User 10 can release the drag gesture. The H window 1089 may be displayed in the third and fourth window display areas 933 and 934, as illustrated in Figure 16c.

[164] Figure 16d illustrates screens of a display device in accordance with an embodiment of the present disclosure. More particularly, Figure 16d illustrates an operation subsequent to the operation of Figures 15a, 15b and 15c.

[165] Referring to Figure 16d, the display device displays window G 1044, window B 1054, window C 1064, and window D 1074 in 4-area split mode. User 10 can manipulate the display device to additionally run application H. User 10 can make the drag gesture by dragging icon 1018 representing application H to a tenth point 1090.

[166] With reference to Figure 16d, the controller may determine an input area corresponding to the tenth point 1090. If the controller determines that the tenth point 1090 corresponds to the seventh input area 947 illustrated in Figure 9h, the controller may determine to display a H window 1092 in the second and fourth window display areas 932 and 934, as illustrated in Table 2. In this way, the controller can display the determined window display areas as a ghost view 1091.

[167] User 10 can determine whether the window will be displayed in a desired position by viewing the ghost view 1091. User 10 can release the drag gesture. Window H 1092 may be displayed in the second and fourth window display areas 932 and 934, as illustrated in Figure 16d.

[168] Figure 17 illustrates screens of a display device in accordance with an embodiment of the present disclosure. More particularly, Figure 17 illustrates an operation subsequent to the operation of Figures 15a, 15b and 15c.

[169] Referring to Figure 17, the display device displays window G 1044, window B 1054, window C 1064, and window D 1074 in 4-area split mode. User 10 may manipulate the display device to additionally run application H. User 10 may make the drag gesture of dragging the icon representing application 1018 H to an eleventh point 1093.

[170] Referring to Figure 17, the controller can determine an input area corresponding to the eleventh point 1093. If the controller determines that the eleventh point 1093 corresponds to the ninth input area 949 illustrated in Figure 9h, the controller can determine display an H window 1095 in the third and fourth window display areas 932 and 934, as illustrated in Table 2. In this way, the controller can display the determined window display areas as a ghost view 1094.

[171] User 10 can determine whether the window will be displayed in a desired position by viewing the ghost view 1094. User 10 can release the drag gesture. The H 1095 window can be displayed full screen.

[172] As described above, the display device can provide a different size window in a different position according to the end point of a drag gesture. While the 4-area splitting mode was described above, the above description can be extended to a 9-area splitting mode or the like.

[173] Figures 18a and 18b illustrate a 9-area division mode in accordance with embodiments of the present invention.

[174] Referring to Figures 18a and 18b, the display device can define nine split-window display areas. In addition, the display device can set input areas A, C, E, K, M, O, U, W, and Y corresponding to the respective window display areas, input areas B, D, F, H, J, L, N, P, R, T, V, and X corresponding to boundaries between window display areas, and input areas L, I, Q, and S corresponding to intersections where the window display areas meet. meet. When the endpoint of a drag gesture is positioned in an input area corresponding to the boundary between the window display areas, the display device can display a window over the entirety of the window display areas. When the endpoint of a drag gesture is positioned on an input area corresponding to an intersection where window display areas meet, the display device can display a window over the entirety of the window display areas. In this way, the display device can display a different size window in a different position according to the position of the end point of a drag gesture.

[175] Figure 19 is a flowchart illustrating a method for controlling a display device in accordance with an embodiment of the present disclosure.

[176] Referring to Figure 19, the display device can display at least one icon representing a running application S1901. The display device can receive a drag gesture of dragging an icon to a first point in operation S1903. The display device can determine the position of the end of the drag gesture in an S1905 running scheme.

[177] The display device can determine if the drag gesture ends at the boundary between the window display areas in operation S1907. If the drag gesture ends at the boundary between the window display areas, the display device can display a window over the entirety of the window display areas in operation S1909.

[178] The display device can determine if the drag gesture ends at an intersection where window display areas meet in S1911 operation. If the drag gesture ends at an intersection where the window display areas meet, the display device can display a window over the entirety of the window display areas in operation S1913.

[179] The display device can determine if the drag gesture ends in a window display area in operation S1915. If the drag gesture ends in a window display area, the display device can display a window in the window display area in operation S1917.

[180] Figure 20 is a flowchart illustrating a method for controlling a display device in accordance with an embodiment of the present disclosure.

[181] Referring to Figure 20, the controller can set an array in a split mode in S2001 operation. The controller can define a plurality of window display areas according to the operating division mode S2003. Furthermore, the controller can allocate a plurality of windows to the operating window display areas S2005. More particularly, the controller may allocate a plurality of windows to a window display area.

[182] The controller can control display of a window with a higher Z-order in each window display area, among the windows allocated to the window display area in S2007 operation. For example, if a plurality of windows are assigned to the first window display area, the controller can control display of a window having the highest Z-order of the allocated windows.

[183] The controller can determine if a Z-order change command has been received via the touch screen in S2009 operation. The Z-order change command is a command requesting to change the Z-order of a window. For example, the Z-order change command can be triggered by a light gesture on the touchscreen. Upon receipt of the Z order change command in S2009 operation, the controller can change at least one Z order and display windows based on the changed Z order in S2011 operation.

[184] Figures 21a, 21b, and 21c illustrate display devices in accordance with embodiments of the present disclosure.

[185] Referring to Figure 21a, a display device 2100 displays a first window 2101 in a first area for running application A, a second window 2102 in a second area for running application B, a third window 2103 in a third area for run application C, and a fourth window 2104 in a fourth area to run application D. The display device 2100 still displays a central button 2110.

[186] Figure 22 illustrates an activity stack according to an embodiment of the present disclosure.

[187] Referring to Figure 22, a controller (not shown) can manage the left activity stack. The controller can manage the Z orders of windows in the order of applications C, F, G, A, D, B, J, K, H, M, L, and I. The controller allocates windows for applications C, F, and G for the third area, windows for applications A, J, and L for the first area, windows for applications D, H, and M for the fourth area, and windows for applications B, K, and I for the second area.

[188] The controller detects applications that are supposed to run in the first area and compares the Z orders of the detected applications. The controller can determine that application A has a higher Z-order in the first area. Thus, the controller controls display of the first window 2101 in which an application runs, in the first area. The controller detects applications that are supposed to run in the second area and compares the Z orders of the detected applications. The controller can determine that application B has a higher Z-order in the second area. Thus, the controller controls display of the second window 2102, in which application B runs, in the second area. The controller detects applications that are supposed to run in the third area and compares the Z orders of detected applications. The controller can determine that application C has a higher Z-order in the third area. Thus, the controller controls display of the third window 2103, in which application B runs, in the third area. The controller detects applications that are supposed to run in the fourth area and compares the Z orders of detected applications. The controller can determine that application D has a higher Z-order in the fourth area. Thus, the controller controls the display of the fourth window 2104 in which application D runs, in the fourth area.

[189] With continued reference to Figure 21a, User 1 can enter a Z-order change command for the third area. For example, user 1 can flick right 2120 across the third area. The controller can recognize the slight right gesture 2120 as the Z-order change command. The slight right gesture 2120 can be defined as a command to allocate a higher Z-order to an application having a lower Z-order in an area window display. The Z-order change is reflected in a right activity stack illustrated in Figure 22. It is noted from the right activity stack illustrated in Figure 22 that application L is placed at the top of the activity stack. The slight right gesture 2120 represents an example of assigning a Z-order in a window display area, and therefore those skilled in the art will readily understand that the Z-order change command can be set by a gesture made in a direction other than to the right. For example, the Z-order change command can be defined by various gestures, such as a flick left, a flick down, a flick up, and so on. Furthermore, many gestures other than light gestures, including tilting, dragging, shaking, and the like, can be defined as the Z-order change command, which should not be construed as limiting the present disclosure. Here, the right direction can be referred to as a first direction, while the first direction is not limited to the right direction.

[190] Referring to Figures 21b and 21c, the controller can control display of a fifth window 2113 in the third area in order to run application L. After receiving a Z-order change command by a slight gesture to the right through from the third area, the controller can determine that application F has a lower Z-order in the third area, as illustrated in Figure 21c. The controller can control display of a sixth window 2123 in the third area in order to run application F.

[191] Figures 23a and 23b illustrate screens of a display device depicting a Z-order change command in accordance with an embodiment of the present disclosure. Figure 24 illustrates an activity stack in accordance with an embodiment of the present disclosure. Figure 23a may be substantially identical to Figure 21c and a left activity stack illustrated in Figure 24 may depict the Z orders of windows shown in Figure 23a.

[192] Referring to Figure 23a, user 1 can enter a Z-order change command for the first area by flicking right 2121 across the first area. A controller (not shown) may determine that application L has a lower Z-order in the first area. The controller can allocate the largest application Z order L as illustrated in a right activity stack illustrated in Figure 24.

[193] Referring to Figure 23b, the controller can control display of a seventh window 2131 in the first area in order to run application L.

[194] Figures 25a and 25b illustrate screens of a display device depicting a Z-order change command in accordance with an embodiment of the present disclosure. Figure 26 illustrates a stack of activities in accordance with an embodiment of the present disclosure.

[195] Referring to Figures 25a and 25b, user 1 can enter a Z-order change command for the second area by flicking left 2130 across the second area. A controller (not shown) may recognize the left flick as the Z-order change command. The left flick can be defined as a command to allocate a lower Z-order to an application having a higher Z-order in a window display area. The direction to the left can be referred to as a second direction.

[196] In this way, the controller can allocate the lowest Z to an application that has the highest Z-order in the second area, as illustrated in a right activity stack illustrated in Figure 26. As application B is assigned with the lowest Z order, the controller can control the assignment of the highest Z order to application J in the second area.

[197] Therefore, the controller can display an eighth window 2142 in the second area in order to run application K as illustrated in Figure 25b. The resulting activity stack change is illustrated in Figure 26.

[198] As described earlier, the controller can recognize a slight left gesture as a command to allocate a higher Z-order to an application having a lower Z-order in a window display area. Additionally, the controller may recognize a slight right gesture as a command to allocate a lower Z-order to an application that has a second higher Z-order value in a windowed display area. Thus, a user can easily switch to an application screen having the lowest or highest Z-order.

[199] Figures 27a and 27b illustrate screens of a display device depicting a Z-order change command in accordance with an embodiment of the present disclosure. Figure 28 illustrates a stack of activities in accordance with an embodiment of the present disclosure.

[200] Referring to Figures 27a and 27b, the display device 2100 displays the first window 2101 in the first area for running an application, the second window 2102 in the second area for running application B, the third window 2103 in the third area for run application C, and the fourth window 2104 in the fourth area to run application D. The display device 2100 can control a stack of activities, as illustrated in Figure 28. User 1 can enter a Z-order change command for the third area. For example, user 1 can make a right tilt gesture 2700 while touching the third area, as indicated by the reference number 2701. The controller can recognize the touch and right tilt gesture as a change command. of order Z.

[201] The controller can change Z-orders in the activity stack illustrated in Figure 28 based on the Z-order change command, which was described earlier with reference to Figure 22 and therefore will not be described redundantly. The controller can control display of the fifth window 2113 in the third area in order to run application L as illustrated in Figure 27b.

[202] Figures 29a and 29b illustrate screens of a display device depicting a Z-order change command in accordance with an embodiment of the present disclosure.

[203] Referring to Figures 29a and 29b, the display device 2100 displays the first window 2101 in the first area for running an application, the second window 2102 in the second area for running application B, the third window 2103 in the third area for run application C, and the fourth window 2104 in the fourth area to run application D. The display device 2100 can control a stack of activities, as illustrated in Figure 30. User 1 can enter a Z-order change command for the second area. For example, user 1 can make a left tilt gesture 2900 while touching the second area, as indicated by the reference number 2901. The controller can recognize the touch and left tilt gesture as a change of direction command. Z order.

[204] The controller can change Z orders in an activity stack illustrated in Figure 30 based on the Z order change command, which was described earlier with reference to Figure 26 and therefore will not be described redundantly. The controller can control display of the eighth window 2142 in the second area so as to run application K as illustrated in Figure 29b.

[205] Figures 31a and 31b illustrate screens of a display device depicting a Z-order change command in accordance with an embodiment of the present disclosure. Figure 32 illustrates an activity stack in accordance with an embodiment of the present disclosure.

[206] Referring to Figures 31a, 31b and 32, the display device 2100 displays the first window 2101 in the first area for running an application, the second window 2102 in the second area for running application B, the third window 2103 in the third area for executing application C, and the fourth window 2104 in the fourth area for executing application D. The display device 2100 can manage a stack of activity, as illustrated in Figure 32. User 1 can enter a Z-order change command to the third area. For example, user 1 can touch a point 3100 in the third area and make a slight right edge gesture 3101 in the third area. The controller can recognize the slight right edge gesture as a Z-order change command.

[207] The controller can change Z-orders in the activity stack illustrated in Figure 32 based on the Z-order change command, which was described earlier with reference to Figure 22 and therefore will not be described redundantly. The controller can control the display of the fifth window 2113 in the third area in order to run application L as illustrated in Figure 31b.

[208] Figures 33a and 33b illustrate screens of a display device depicting a Z-order change command in accordance with an embodiment of the present disclosure. Figure 34 illustrates an activity stack in accordance with an embodiment of the present disclosure.

[209] Referring to Figures 33a, 33b and 34, the display device 2100 displays the first window 2101 in the first area for running an application, the second window 2102 in the second area for running application B, the third window 2103 in the third area for executing application C, and the fourth window 2104 in the fourth area for executing application D. The display device 2100 can manage a stack of activities, as illustrated in Figure 34.

[210] User 1 can enter a Z-order change command for the second area. For example, user 1 can touch a point 3300 in the second area and make a slight left edge gesture 3301 in the second area. The controller can recognize the slight left edge gesture as a Z-order change command.

[211] The controller can change Z orders in the activity stack illustrated in Figure 34 based on the Z order change command, which was described earlier with reference to Figure 26 and therefore will not be described redundantly. The controller can control the display of the eighth window 2142 in the second area so as to run application K as illustrated in Figure 33b.

[212] Methods of changing a Z order into a division mode have been described so far. Now, description will be given of methods of changing a Z-order in a freestyle mode.

[213] Figure 35 is a flowchart illustrating a method for controlling a display device in accordance with an embodiment of the present disclosure.

[214] Referring to Figure 35, a controller can define an array in a freestyle mode in S3501 operation. The controller can receive application execution commands, and thus, can generate a plurality of windows to execute a plurality of applications in operation S3503. The controller may determine the Z-order of each of the plurality of operating windows S3505 and may display the overlapping windows based on their operating Z-orders S3507.

[215] The controller can determine if a Z-order change command was received in operation S3509. Upon receipt of the Z-order change command, the controller can control the display of the overlapping windows according to a changed Z-order in operation S3511.

[216] Figures 36a, 36b, and 36c illustrate screens of a display device depicting a Z-order change command in accordance with an embodiment of the present invention and Figures 37a, 37b, and 37c illustrate stacks of activities in accordance with modalities of this disclosure.

[217] Referring to Figures 36a, 36b, 36c, 37a, 37b, and 37c, the controller can manage the activity stack illustrated in Figure 37a. For example, the controller might allocate a lower Z-order to window A that runs application A, a medium Z-order to window B that runs application B, and a higher Z-order to window C that runs application C. Accordingly, the controller can control the display of windows in the order of window C 3631 and 3632, window B 3621 and 3622, and window A 3611 and 3612, as illustrated in Figure 36a.

[218] User 1 can enter a Z-order change command. The Z-order change command can be triggered by a pinch-out gesture 3642 to the left, while a title bar 3631 is tapped in window C, as indicated by reference number 3641. Pinch may be a two-point spread gesture. In this case, the Z-order of window C 3631 and 3632 can be reset to the lowest Z-order. As a result, the controller assigns the average Z-order to window A, the highest Z-order to window B, and the smallest Z-order for window C. For example, the controller can allocate the smallest Z-order to window C, while increasing the Z-orders of other windows by 1. Therefore, the controller can control display of windows in the order of window B 3621 and 3622, window A 3611 and 3612, and window C 3631 and 3632. Pinch is a Z-order change command and therefore it will be readily understood by those skilled in the art that the Z-order change command can be triggered by various gestures including light touch, drag , light edge touch, touch and tilt, tilt, and shake.

[219] User 1 can enter a Z-order change command. The Z-order change command can be triggered by a left pinch-out gesture 3652 while an application run screen 3632 is tapped on the window C, as indicated by the reference number 3651. In this case, the Z order of window C 3631 and 3632 can be reset to the lowest order Z. As a result, the controller assigns the highest order Z to window A, the lowest order Z for window B that runs application B, and the average Z order for window C that runs application C. For example, the controller can allocate the lowest Z order to window B, while increasing the Z orders of other windows by 1. Therefore, the controller can control the display of windows in the order of window A 3611 and 3612, window C 3631 and 3632, and window B 3621 and 3622.

[220] Figures 38a, 38b, and 38c illustrate screens of a display device depicting a Z-order change command in accordance with an embodiment of the present invention, and Figures 39a, 39b, and 39c illustrate stacks of activities in accordance with such embodiments. of the present disclosure.

[221] Referring to Figures 38a, 38b, 38c, 39a, 39b, 39c e, the controller can manage the activity stack illustrated in Figure 39a. For example, the controller might allocate a lower Z-order to window A that runs application A, the average Z-order to window B that runs application B, and the highest Z-order to window C that runs application C. Therefore , the controller can control the display of windows in the order of window C 3631 and 3632, window B 3621 and 3622, and window A 3611 and 3612, as illustrated in Figure 38a.

[222] User 1 can enter a Z-order change command. The Z-order change command can be triggered by a pinch-in gesture 3842 from the left, while the title bar 3631 is tapped in window C , as indicated by the reference number 3841. Pinching in can be a gesture of narrowing the distance between two touched points. In this case, the Z-order of window A 3631 and 3632 having the lowest Z-order can be reset to the highest Z-order, while decreasing the Z-order of other windows by 1. Therefore, the controller can allocate the highest Z-order to the window. A, the smallest Z-order for window B running application B, and the average Z-order for window C running application C, as illustrated in Figure 39b.

[223] As illustrated in Figure 38b, the controller can control the display of windows in the order of window A 3611 and 3612, window C 3631 and 3632, and window B 3621 and 3622. User 1 can enter a window change command. Z-order. The Z-order change command can be triggered by a pinch-in gesture 3852 from the left, while the title bar 3631 is tapped in window C, as indicated by the reference number 3851. The Z-order of window B 3621 and 3622 with the lowest Z-order can be reset to the highest Z-order, while the Z-order of the other windows is decreased by 1. As a result, the controller can allocate the average Z-order to window A which runs application A, the highest Z order for window B which runs application B, and the lowest Z order for window C which runs application C, as illustrated in Figure 39c.

[224] Therefore, the controller can control the display of windows in the order of window B 3621 and 3622, window A 3611 and 3612, and window C 3631 and 3632.

[225] As described above, upon receipt of a Z-order change command by a pinch-out gesture, the controller can allocate the lowest Z-order to a window that has the highest Z-order. a Z-order change command by a pinch-in gesture, the controller can allocate the highest Z-order to a window that has the smallest Z-order. Since a user can change the Z-orders of windows through a simple manipulation, an intended window appears on the top layer of a canvas. Therefore, user convenience can be increased.

[226] Figures 40a, 40b, 40c, 40d, 40e, 40f, 40g, 40h, 40i, 40j, and 40k illustrate a method for displaying an application execution window in accordance with an embodiment of the present disclosure.

[227] Referring to Figures 40a, 40b, 40c, 40d, 40e, 40f, 40g, 40h, 40i, 40j, and 40k, a display device 4200 may define a plurality of regions 4201, 4202, 4203, and 4204 in a touch screen. For convenience of description in Figure 40a and subsequent drawings, the plurality of regions 4201, 4202, 4203, and 4204 are referred to as the first, second, third, and fourth regions 4201, 4202, 4203, and 4204 (Region 1, Region 2, Region 3, and Region 4), respectively. Both the first and third regions 4201 and 4203 form a fifth region (region 5, not shown) and both the second and fourth regions 4202 and 4204 form a sixth region (region 6, not shown). Both the first and second regions 4201 and 4202 form a seventh region (Region 7, not shown) and both the third and fourth regions 4203 and 4204 form an eighth region (Region 8, not shown). The first to fourth regions 4201, 4202, 4203, and 4204 form region F. A first boundary 4211 can be established between the first and second regions 4201 and 4202, a second boundary 4212 can be defined between the third and fourth regions 4203 and 4204, a third boundary 4213 may be defined between the first and third regions 4201 and 4203, and a fourth boundary 4214 may be defined between the second and fourth regions 4202 and 4204. The first and second boundaries 4211 and 4212 may form a single line, and the third and fourth borders 4213 and 4214 can form a single line. The first to fourth boundaries 4211-4214 do not necessarily have to be explicitly displayed. On the contrary, the first to fourth boundaries 4211-4214 can be virtual lines. A controller (not shown) can configure the first through fourth regions 4201, 4202, 4203, and 4204 such that the first through fourth regions 4201, 4202, 4203, and 4204 do not overlap. For example, as illustrated in Figure 40a, the controller can configure the first region 4201 in an upper left corner, the second region 4202 in an upper right corner, the third region 4203 in a lower left corner, and the fourth region 4204 in an upper left corner. bottom right. The controller can divide the screen into left and right parts by the first and second borders 4211 and 4212 and into top and bottom parts by the third and fourth borders 4213 and 4214.

[228] The touchscreen can display a center button 4220 at an intersection where the first to fourth boundaries 4211-4214 meet. The center button 4220 can be a function key that changes the size of a region in which to display an application execution window or that defines an operating mode of controlling an execution window.

[229] The controller can control the touch screen so that an application execution window is displayed in each of a plurality of regions. For example, the controller can control the touchscreen so that a window that presents a running application, i.e., an application execution window, is displayed in each of regions 4201, 4202, 4203, and 4204, as illustrated. in Figures 40b, 40c, 40d, 40e, 40f, 40g, 40h, 40i, 40j, and 40k.

[230] Application-related objects can be displayed on the application run screen. Objects can take many forms, such as text, a picture, an icon, a button, a checkbox, a photo, a video, a web page, a map, and so on. When a user taps an object, a function or event corresponding to the tapped object can be executed in the application. An object can be called a view according to an operating system. For example, at least one of a capture button that captures a run window to control the run window's display, a minimize button that minimizes the size of a run window, a maximize button that maximizes the size of a window run, and an exit button that ends a run window can be displayed.

[231] Referring to Figure 40b, the controller can control display of icons 4231, 4232, 4233, 4234, 4235, 4236 and 4237 representing executable applications on the touch screen. The display device 4200 can execute application A. As illustrated in Figure 40b, in response to the execution of application A, the controller can control the touch screen to display an execution window 4230 of application A in the first region 4201. In addition In addition, the controller can control display of icons 4231, 4232, 4233, 4234, 4235, 4236, and 4237 representing the executable applications at a specific position on the touchscreen. Upon receipt of a touch input for one of icons 4231, 4232, 4233, 4234, 4235, 4236, and 4237, i.e. upon receipt of an input that selects an icon representing an application to run, the display device 4200 can display an application run window that corresponds to the selected icon in one of the first to fourth regions 4201, 4202, 4203, and 4204.

[232] The controller may display an indicator 4221 indicating an active region, on the center button displayed 4220. The active region may be a region where the execution window of a last executed application or a last application selected by a user is displayed. A user-manipulated application can be considered a user-selected application.

[233] The 4221 indicator can be implemented in several ways to indicate the position of an active region. For example, at least a portion of an application execution window presented in an active region may be presented in an overlapping area between the application execution window of the active region and the center button 4220. Alternatively, an arrow indicating the direction of an active region can be displayed on the center button 4220.

[234] The active region can be determined based on a stack of activities. The last run application or the last user selected application can be placed at the top of the activity stack. The 4200 display device can determine, as an active region, a region in which an application execution window at the top of the activity stack is displayed. The active region can be referred to as a focused region. For example, indicator 4221 may indicate the first region 4201 in Figure 40b.

[235] Figures 41a, 41b, 41c, 41d, 41e, and 41f illustrate stacks of activities in accordance with various embodiments of the present invention.

[236] Referring to Figure 41a, which illustrates an activity stack handled by the display device 4200. The controller can generate and handle an activity 4301 for application A in the activity stack in response to the execution of application A.

[237] Referring to Figure 40c, user 1 can tap icon 4232 representing application B. When icon 4232 representing application B is tapped, the controller controls display of an execution window 4240 of application B in the second region 4202, as illustrated in Figure 40d. The controller can determine a region in which to display an execution window according to a certain order. For example, the controller can control display of new execution windows in the order of the second, third, and fourth regions 4202, 4203, and 4204. The above execution window display order is just an example, and therefore the display order the new execution windows in regions 4201, 4202, 4203, and 4204 can be changed in accordance with various embodiments of the present invention.

[238] As the execution window 4240 of application B is displayed in the second region 4202, the indicator 4221 can indicate the second region 4202 in Figure 40d.

[239] Referring to Figure 41b, which illustrates an activity stack corresponding to Figure 40d. The controller generates an activity 4301 for application B in the activity stack in response to the execution of application B. The controller can put activity 4302 of the last executed application B into activity 4301 of application A.

[240] Referring to Figure 40e, user 1 can tap the 4233 icon corresponding to application C. When the icon representing application 4233 C is tapped, the controller controls display an execution window 4250 of application C, in the fourth region 4204, as illustrated in Figure 40f. Along with displaying the execution window 4250 of application C, in the fourth region 4204, the indicator 4221 can indicate the fourth region 4204.

[241] Figure 41c illustrates an activity stack corresponding to Figure 40f. The controller generates a 4303 activity for application C in the activity stack in response to the execution of application C. The controller 4303 places the activity of the last C application executed at the top of the activity stack.

[242] With reference to Figure 40g, user 1 can touch icon 4234 representing application D. When icon 4234 representing application D is touched, the controller controls display of an execution window 4260 of application D in the third region 4203, as illustrated in Figure 40h. As the execution window 4260 of application D is presented in the third region 4203, the indicator 4221 of the central button 4220 can indicate the third region 4203.

[243] Figure 41d illustrates an activity stack corresponding to Figure 40h. The controller generates an activity 4304 for application D in the activity stack in response to the execution of application D. The controller 4304 places the activity of the last executed application D at the top of the activity stack.

[244] With reference to Figure 40i, user 1 can manipulate application B. Figure 41e illustrates an activity stack corresponding to Figure 40i. The controller moves activity 4302 from application B to the top of the activity stack in response to user input to the execution window 4240 from application B.

[245] Upon receipt of user input for execution window 4240 of application B, the controller may determine the second region 4202 to be an active region, as illustrated in Figure 40i. Therefore, the indicator 4221 on the central button 4220 can indicate the second region 4202.

[246] With reference to Figure 40j, user 1 can touch icon 4235 representing application E. When icon 4235 representing application E is touched, the controller controls display of an execution window 4270 of application E in the fourth region 4204 on the screen touch-sensitive, as illustrated in Figure 40k. In the absence of an empty region, the controller can refer to the activity stack illustrated in Figure 41e. The controller can select the lowest application activity from the activity stack and can display the execution window 4270 of application E, substituting for application C corresponding to the lowest activity, in the fourth region 4204.

[247] Figure 41f illustrates an activity stack corresponding to Figure 40k. The controller generates an activity 4305 for application E in the activity stack in response to the execution of application E. The controller places activity 4305 of the last executed application E at the top of the activity stack.

[248] Fig. 42 is a flowchart illustrating a method for running a display device application in accordance with an embodiment of the present disclosure.

[249] Referring to Figure 42, the display device can run a plurality of applications in S4410 operation. For example, the display device might run an application in response to receiving touch input on an icon representing the application.

[250] The display device can determine an arrangement for arranging run windows of running applications S4420. The arrangement defines regions in which run windows can be arranged. For example, various arrangements are available, including a 2-area split-up/down arrangement, a 2-area split-up arrangement, a 3-area split arrangement, a 4-area split arrangement, and the like.

[251] The display device can determine the position of windows in the S4430 running array. In the case of a left/right 2 area split arrangement where the fifth and sixth regions are defined, the display device can allocate run windows of a web browser and a phone book application to the fifth region and a running window of a video playback application for the sixth region.

[252] The display device can display a plurality of execution windows according to the priority levels of running applications S4440. For example, if the run windows of the web browser and the phone book application are allocated to the fifth region, the run window of an application having a higher priority between the web browser and the phone book application may be displayed in the fifth region.

[253] Figures 43a and 43b illustrate a method for controlling an area of an application execution window using a center button in accordance with an embodiment of the present disclosure display.

[254] Referring to Figure 43a, a display device 4500 may define a first region 4501, a second region 4502, a third region 4503, a fourth region 4504, a first boundary 4505, a second boundary 4507, a third boundary 4506 , and a fourth boundary 4508, which should not be construed as limiting the present disclosure. Thus, the display device 4500 can define regions and boundaries in various ways.

[255] Display device 4500 can display center button 4220 on at least one border. For example, if the first boundary 4505, the second boundary 4507, the third boundary 4506, and the fourth boundary 4508 are defined, the display device 4500 can display the center button 4220 at an intersection, where the first boundary 4505, the second boundary 4507, third boundary 4506, and fourth boundary 4508 meet, as illustrated in Figure 43a. In another example, if the display device 4500 defines the fifth and sixth regions (not shown) and the first and second borders 4505 and 4507, the display device 4500 may display the center button 4220 on the first or second borders 4505 or 4507.

[256] Referring to Figure 43b, if user 10 touches center button 4220 and drags center tapped button 4220, display device 4500 can move center button 4220 to a dragged position. When the center button 4220 moves, the display device 4500 can change the sizes and positions of the regions in which to display application run windows and borders.

[257] Figures 44a, 44b, 44c, 44d, 44e, 44f, 44g, 44h, 44i, 44j, 44k, 44l, 44m, 44n, 44o, 44p, 44q, 44r, 44s, 44t, 44u, 4V, and 44w illustrate a method for running a plurality of applications in accordance with an embodiment of the present disclosure.

[258] Referring to Figures 44a, 44b, 44c, 44d, 44e, 44f, 44g, 44h, 44i, 44j, 44k, 44l, 44m, 44n, 44o, 44p, 44q, 44r, 44s, 44t, 44u, 4V , and 44W, while application A is running, a 4600 display device can display a 4610 list of at least one application. The 4610 application list lists executable applications. For example, icons 4611, 4612, 4613, 4614, 4615, 4616, and 4617 representing executable applications can be listed in the 4610 application list.

[259] Figures 45a, 45b, 45c, 45d, 45e, 45f, 45g, 45h, 45i, and 45j illustrate activity stacks in accordance with embodiments of the present disclosure.

[260] Referring to Figure 45a, an activity stack corresponding to Figure 44a is illustrated. When an application execution window A is presented in Region F that occupies the entirety of a screen, a controller (not shown) generates an activity for application as illustrated in Figure 45a.

[261] User 10 can manipulate display device 4600 to additionally run application B. For example, user 10 can tap icon 4612 representing application B as illustrated in Figure 45b and drag tapped icon 4612 to a sixth region 4623 as illustrated in Figure 45c.

[262] If the drag input ends in the sixth region 4623, the display device 4600 executes application B corresponding to the selected icon 4612. Furthermore, the display device 4600 moves application A shown in region F to a fifth region 4619, while displaying application B in the sixth region 4623.

[263] Eventually, a 4620 run window of application A is displayed in the fifth region 4619, while a 4630 run window of application B is displayed in the sixth region 4623.

[264] The display device 4600 may display a central button 4622 on the boundary between the fifth and sixth regions 4619 and 4623. The display device 4600 may also display an indicator 4621, indicating the execution window 4630 of the last application B executed in the center button 4622. Indicator 4621 can indicate a region where the execution window of an application placed on top of an activity stack is displayed.

[265] Figure 45b illustrates an activity stack corresponding to Figure 44d. The activity of application A is presented in Region F is changed so that application A can be presented in the fifth region 4619. When application B runs, an activity for application B is generated and application B is placed in the sixth region 4623. Application activity B is placed at the top of the activity stack.

[266] With reference to Figure 44e, the user 10 can move the displayed center button 4622. As illustrated in Figures 43a and 43b, along with the movement of the center button 4622, the sizes of the regions in which to display the execution windows of application can be changed.

[267] Subsequently, user 10 can tap icon 4613 representing application C, as illustrated in Figure 44f and drag tapped icon 4613 to a fourth region 4627 as illustrated in Figure 44g. The size of the fourth region 4627 can be determined according to the position of the central button 4622. When dragging the icon 4613 representing application C ends in the fourth region 4627, the display device 4600 can run application C. As illustrated in Figure 44h , the display device 4600 can display a run window 4640 of application C in the fourth region 4627. The display device 4600 can display the indicator 4621 indicating the active region by displaying the run window 4640 of application C at the center button 4622.

[268] Figure 45c illustrates an activity stack corresponding to Figure 44h. A controller (not shown) generates an activity for application C in response to the execution of application C. Application C is wrapped in the fourth region 4627. Once the region displaying the execution window 4630 of application B is divided, application B is allocated to the second region in Figure 44e.

[269] Referring to Figure 44i, the user 10 can control the size of the regions displaying application run windows 4620 to 4640 by applying an input that moves the center button 4622.

[270] User 10 can tap icon D representing application 4614 as illustrated in Figure 44j and drag tapped icon 4614 to a third region 4631 as illustrated in Figure 44k.

[271] If the drag of the tapped icon 4614 representing application D ends in the third region 4631, the display device 4600 can run application D. The display device 4600 can display a run window 4650 of application D in the third region 4631 as illustrated in Figure 44l. The 4600 display device can display the 4621 indicator indicating the active region by displaying the 4650 run window of application D, on the 4622 button.

[272] Figure 45d illustrates an activity stack corresponding to Figure 44l. The controller generates an activity for application D in response to the execution of application D. Application D is allocated to the third region 4631. Since the region displaying application A's execution window 4620 is divided, application A is allocated to the first region in the Figure 44i.

[273] User 10 can tap the icon representing application 4615 E and drag the tapped icon 4615 to the boundary region 4659, as illustrated in Figure 44m. The display device 4600 sets the boundary region 4659 to include a boundary 4685.

[274] If the drag of the tapped icon 4615 representing application E ends in the boundary region 4659, the display device 4600 can run the application E. The display device 4600 can arrange a running window 4660 of application E in a seventh region including the first and second regions adjacent to the boundary 4685 included in the boundary region 4659, as illustrated in Figure 44n. The 4600 display device can display the 4621 indicator indicating the active region by displaying application execution window 4660 E, on button 4622.

[275] Figure 45e illustrates an activity stack corresponding to Figure 44n. The controller generates an activity for application E in response to executing application E. Application E is allocated to the seventh region, and applications A and B shown in the first and second regions included in the seventh region are placed in the seventh region.

[276] User 10 can tap icon 4616 representing application F and drag tapped icon 4616 to second region 4661, as illustrated in Figure 44o.

[277] If the drag of the tapped icon 4616 representing application F ends in the second region 4661, the display device 4600 can run application F. The display device 4600 can display a run window 4670 of application F in the second region 4661, as illustrated in Figure 44p.

[278] Referring to Figure 45f, the controller can generate an activity for application F disposed in the second region. As the seventh region is split, applications A, B, and E presented in the seventh region can be arranged in the first region.

[279] The touch screen can receive an input that selects application execution window 4660 E from user 10, as illustrated in Figure 44p.

[280] Referring to Figure 45g, in response to the 4660 execution window selection of application E, the controller can move application activity E to the top of the activity stack. Display device 4600 can display indicator 4621 which indicates the position of run window 4660 on button 4622.

[281] Referring to Fig. 44q , display device 4600 may receive input that selects application execution window 4660 E from user 10. For example, UE 10 may tap button 4622. In response to reception from the input that selects the 4622 button, the 4600 display device can display a list of 4611, 4612, and 4615 applications displayed in the first region that is now active. For example, display device 4600 may display icons representing applications A, B, and E allocated to the first region, in the first region referring to the stack of activities illustrated in Figure 45g.

[282] In response to receiving input that selects button 4622, display device 4600 may further display icons 4691, 4692, and 4693 representing operations related to the execution window of an application displayed in the first region.

[283] After receiving an input that selects icon 4611 representing application A from among the icons displayed in the first region, the display device 4600 can display the execution window 4620 of application A in the first area, as illustrated in Figure 44s.

[284] Figure 45h illustrates an activity stack corresponding to Figure 44s. In response to receiving input that selects icon 4611 representing application A, the controller can move application activity A from the top of the activity stack.

[285] Referring to Figure 44t, upon receipt of an input that selects center button 4622, the list of applications 4611, 4612, and 4615 allocated to the first region being an active region can be displayed. Also, a drag input of dragging icon 4612 representing application B to a region displaying the 4640 execution window of application C may be received by user 10. When the drag input is complete, the display device 4600 may display the execution window 4630 of application B in the fourth region, as illustrated in Figure 44u. Display device 4600 can display indicator 4621 which indicates the position of execution window 4630 of application B, on button 4622.

[286] Figure 45i illustrates an activity stack corresponding to Figure 44u. Once application B's execution window 4630 is presented in the fourth region, the controller updates the region application B is allocated to to the fourth region and moves application B's activity to the top of the activity stack.

[287] Referring to Figure 44v, after receiving an input that selects center button 4622, icons 4691, 4692, and 4693 representing operations related to the execution window of an application presented in the first region being an active region can still be displayed. displayed. Application run window related operations can perform many additional functions in relation to the application run window. For example, icons representing operations related to the application run window may include at least an exit button 4691 which terminates the run window, the maximize button 4692 which displays the run window in full screen, and the capture button 4693 that captures the execution window, which should not be interpreted as limiting the present disclosure. After receiving an input that selects exit button 4691 from user 10, the controller can terminate the application execution window A, as illustrated in (b) of Figure 44v.

[288] Figure 45j illustrates an activity stack corresponding to Figure 44v. After application A's execution window ends, application A's activity can be removed from the activity stack.

[289] Referring to Figure 44w, upon receiving an input that selects the maximize button 4692 from user 10, the display device 4600 can display a running window 4660 of application A displayed in an active region on screen full on the touch screen.

[290] Upon receipt of an input that selects the capture button of 4693 from user 10, the display device 4600 can capture the active run window 4660.

[291] Figure 46 is a flowchart illustrating a method for providing a user interface in which an application runs on a display device in accordance with an embodiment of the present disclosure.

[292] Referring to Figure 46, the display device can display application execution windows in a plurality of defined regions on a touch screen in S4810 operation. The display device may also display a button at at least one boundary between a plurality of regions in operation S4820.

[293] The display device may display an indicator on the button to indicate an active region. The active region can refer to a last area selected from the plurality of regions. Also, active region means a region where the execution window is presented in a state controllable by a user input.

[294] The display device can receive an input that selects the S4830 operating button. Upon receipt of input that selects the button, the display device can display a list of applications in a specific region in S4840 operation. Here, the specific region can be an active region.

[295] The application list can list at least one icon representing at least one application. Upon receipt of an input that selects at least one of the applications included in the application list, the display device can display a running window of the selected application in the specific region. Upon receipt of a drag input of dragging an icon included in the application list, the display device can display an application run window corresponding to the dragged icon in the dragged region.

[296] The display device can also display icons that represent operations related to the application execution window displayed in the specific region. Icons representing operations related to the application run window can include at least one of a capture button that captures a run window to control the display of the run window, a minimize button that minimizes the size of a window button, a maximize button that maximizes the size of a run window, and an exit button that ends a run window.

[297] Fig. 47 is a flowchart illustrating a method for running a display device application in accordance with an embodiment of the present disclosure.

[298] Referring to Figure 47, the display device can display application execution windows in a plurality of defined regions on a touch screen in S4910 operation. The display device may also display a button on at least one boundary between a plurality of regions in operation S4920.

[299] The display device may display a list of at least one application run icon on a partial area of a touchscreen in S4930 operation.

[300] The display device can determine a region in which to launch a new application based on a position to which the application launch icon is dragged and the position of the operating button S4940. The new application execution region is a region where the execution window of the additionally executed application will be displayed.

[301] If the dragged position falls within a boundary region including at least one boundary, the region of execution of the new application can be determined to include regions adjacent to at least one boundary.

[302] Thereafter, the display device can display the application execution window in the region determined in S4950 operation.

[303] Fig. 48 is a block diagram of a display device according to an embodiment of the present disclosure.

[304] Referring to Figure 48, a display device 5000 may include a touch screen 5010 configured to display application execution windows in a plurality of regions, display a button on at least one boundary between a plurality of regions, and receiving input that selects the button, and a controller 5020 configured to control the touch screen 5010 to display a list of at least one application running in a specific region, selected from the plurality of regions in the specific region based on the input received.

[305] The specific region includes an active region controllable by user input. The active region may be a last region selected from among the plurality of regions.

[306] Additionally, the 5020 controller can control the 5010 touchscreen to display an indicator that indicates the active region of the button.

[307] Figures 49a, 49b, 49c, and 49d illustrate a method for displaying a button in accordance with an embodiment of the present disclosure.

[308] Referring to Figure 49a, a display device 5100 may display a button 5122 on a boundary that separates regions in which the execution windows of a plurality of applications are displayed. Furthermore, the display device 5100 may define an alignment line 5120 in accordance with an arrangement of application execution windows. Alignment line 5120 may include a dotted line and the outside line of a touch screen.

[309] Display device 5100 may further define an alignment region 5110. Alignment line 5120 may be included in alignment region 5110.

[310] As illustrated in Figure 49a, alignment line 5120 and alignment region 5110 can be determined according to the number and positions of application execution windows displayed on the touch screen. For example, if the array is a top/bottom 2 area split array, a left/right 2 area split array, a 3 area split array, or a 4 area split array, the line alignment region 5120 and alignment region 5110 can be defined according to the arrangement.

[311] Referring to Figure 49b, upon receiving an input that moves the button 5122 in the alignment region 5110 on the touch screen, the display device 5100 can move the button 5122 over a portion of the alignment line 5120 closest to the last position of button 5122.

[312] Display device 5100 can determine a region in which to display application run windows based on the position of button 5122 on alignment line 5120. Therefore, display device 5100 can align display regions of windows of application execution.

[313] Referring to Figure 49c, the display device 5100 can set an alignment point 5130 at a certain position of the alignment line 5120. After receiving an input to button 5122 (for example, two consecutive presses of button 5122) , display device 5100 can move button 5122 to alignment point 5130.

[314] Referring to Figure 49d, if the button 5122 moves in the manner illustrated in Figures 49a, 49b, and 49c, the movement can be animated according to a function illustrated in Figure 49d. For example, when center button 5122 moves to alignment line 5120 or alignment point 5130, button 5122 can move past alignment line 5120 or alignment point 5130 and back to alignment line 5120 or alignment point 5120. alignment 5130.

[315] Embodiments of the present invention provide a display device that can easily switch from one window to another lower priority window after running a plurality of windows in a single display, and a method for controlling the display device. Therefore, a user can simultaneously use a plurality of applications in a plurality of windows. Furthermore, if a plurality of windows are displayed overlapping, a currently displayed window is easily transferred to another window of lower priority. Consequently, the user can run a window at a desired size in a desired position with greater convenience in an environment where a plurality of windows are presented on one screen.

[316] It will be understood that the various embodiments of the present invention may be implemented in hardware, software, or a combination thereof. Software may be stored in a volatile or non-volatile memory device, such as a ROM, regardless of whether the data is erasable or rewritable, in memory, such as a RAM memory, a memory chip, a device, a circuit integrated, a data storage medium that can be recorded optically or magnetically and from which the data can be read by a machine (e.g. a computer), such as a compact disc (CD), a Digital Versatile Disc ( DVD), a magnetic disk, a magnetic tape, or the like. Furthermore, embodiments of the present invention may be implemented in a computer or a portable terminal that has a controller and memory, such as a machine-readable storage medium suitable for storing a program or programs including commands, to implement the modalities of this disclosure. Accordingly, the present disclosure includes a program that has code to implement the apparatus, or methods defined in the claims, and a machine-readable storage medium that stores the program. The program may be electronically transferred over a medium, such as a communication signal transmitted over a wire or a wireless link, wherein the medium and the equivalents of which are included in the present description.

[317] The device can receive and store the program from a program delivery device over a wired or wireless connection. The program delivery device may include a program including commands for implementing embodiments of the present invention, a memory for storing information used for embodiments of the present invention, a communication module for communicating with the mobile device via wire or a wireless link, and a controller to stream the program to the mobile device automatically or on demand.

[318] While the description has been particularly shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and detail may be made without departing from the spirit and scope of the present invention as defined. by the following claims and their equivalents.

Claims (15)

1. Method for controlling a display device with a touch screen, the method characterized in that it comprises: based on receiving, through the touch screen, a first touch input on a first application icon, executing a first app corresponding to the first app icon; on the basis of running the first application, display a screen of running the first application in a first application window on the touch screen; while the first application running screen is displayed, receiving, through the touch screen, a second touch input on a second application icon to run a second application corresponding to the second application icon; based on receiving the second touch input, display the first application window corresponding to the first application on a first part of the touchscreen and a second application window corresponding to the second application on a second part of the touchscreen respectively , the first part being different from the second part; based on receiving, through the touchscreen, a third touch input over a third application icon, determining a part of the touchscreen to display a third application running screen corresponding to the third application icon, in that the third touch input includes a drag input starting from the third app icon and being released within one of the first parts of the touch screen or the second part of the touch screen and where the third app icon is displayed while the third touch input is kept on the touch screen; and display a third application window corresponding to the third application over the given part of the touchscreen, wherein the given part of the touchscreen is within either the first part of the touchscreen or the second part of the touchscreen to touch, wherein if the determined portion is within the first part of the touchscreen, the display of the second application window on the second part of the touchscreen will be maintained, and wherein if the determined portion is within the second portion touchscreen, the display of the first application window on the first part of the touchscreen is maintained. 2. Method according to claim 1, characterized in that it further comprises displaying, on a predetermined part of the touch screen, at least one icon of the first application icon, the second application icon or the third icon of application. 3. Method according to claim 1, characterized in that the second touch input includes a drag gesture of dragging the second application's icon to a first point in the first application's window. 4. Method according to claim 1, characterized in that the first part is wider than the second part. 5. Method according to claim 1, characterized in that the third application window is partially overlapped and displayed in one of the first application window or in the second application window. 6. Method according to claim 2, characterized in that the predetermined part is a part that extends over the first application window and the second application window. 7. Method according to claim 1, characterized in that at least one of the first application icon, the second application icon or the third application icon is displayed along an edge of the touch screen. 8. Display device characterized in that it comprises: a touch-sensitive screen; and a controller configured to control the display device to: based on receiving, through the touchscreen, a first touch input on a first app icon, running a first app corresponding to the first app icon, based on run the first app, display a first app run screen in a first app window on the touchscreen, while the first app run screen is displayed, receive, through the touchscreen, a second touch input over a second application icon to run a second application corresponding to the second application icon, based on receiving the second touch input, display the first application window corresponding to the first application on a first part of the touch screen and a second application window corresponding to the second application on a second part of the touchscreen, respectively nte, the first part being different from the second part, based on receiving a third touch input on a third app icon, determining a part of the touch screen to display a third app running screen corresponding to the third app icon application, where the third touch input includes a drag entry starting from the third application icon and being released within either the first part of the touchscreen or the second part of the touchscreen and wherein the third icon of the application is displayed while the third touch input is held on the touchscreen, and display a third application window corresponding to the third application on the given part of the touchscreen, where the given part of the touchscreen is within the first part of the touchscreen or second part of the touchscreen, where if the given part is inside the first part of the screen touch screen, the display of the second application window in the second part of the touch screen will be kept, and where if the given part is inside the second part of the touch screen, the display of the first application window in the first part of the touch screen is maintained. 9. Display device according to claim 8, characterized in that the controller is configured to control the touchscreen to display, on a predetermined part of the touchscreen, at least one icon of the first icon of app, second app icon, or third app icon. 10. Display device according to claim 8, characterized in that the second touch input includes a drag gesture of dragging the second application's icon to a first point in the first application's window. 11. Display device, according to claim 8, characterized in that the first part is wider than the second part. 12. Display device according to claim 8, characterized in that the third application window is partially overlapped and displayed in one of the first application window or in the second application window. 13. Display device according to claim 9, characterized in that the predetermined part is a part that extends over the first application window and the second application window. 14. Display device according to claim 8, characterized in that at least one of the first application icon, the second application icon or the third application icon is displayed along an edge of the touch screen when Touch. 15. Display device, according to claim 8, characterized in that the first part and the second part are separate from each other.

Images