CN110427130B - Display device and method for controlling display device - Google Patents

Abstract

A display device having a touch screen, running at least one application, and a method for controlling the display device are provided. The method includes: receiving an application execution command for executing at least one application; determining at least one of a size and a position of a window running the at least one application according to a position input by the application execution command; and displaying the window according to at least one of the size and position of the window.

Description

Display device and method for controlling display device

This application is a divisional application of an invention patent application with an application date of December 6, 2013, an application number of 201380071613.8, and an invention title of “Display Device and Method for Controlling Display Device”.

technical field

The present disclosure relates to a display device and a method for controlling the display device. More particularly, the present disclosure relates to a display device displaying a window for running an application and a method for controlling the display device.

Background technique

Desktop computers are equipped with at least one display device (eg, monitor). Similarly, mobile devices (eg, mobile phones, smart phones, tablet personal computers (PCs), etc.) with touch screens are also equipped with display devices.

A user may divide a screen of a display device according to a task environment using a desktop computer (for example, a screen is divided horizontally or vertically and a plurality of windows are called in the divided screen). When running the web browser, the user can scroll up or down the webpage by means of the page up button or the page down button in the keyboard. If the user is using a mouse instead of a keyboard, the user can scroll up or down the web page by selecting the scroll bar in the side of the web page with the mouse cursor. The user can also move to the top of the web page by selecting the top button displayed as text or an icon in the bottom of the web page.

Compared to desktop computers, mobile devices have small screen sizes and are limited in terms of input to the screen. Therefore, it is difficult to divide a screen in a mobile device.

Various applications can be run on the mobile device. The applications include basic applications installed by the manufacturer during manufacturing and additional applications downloaded from application sales sites. Additional applications can be developed by ordinary users and registered to the application sales website. Therefore, anyone is free to sell the applications he or she develops to mobile users through application sales sites. Currently, tens to hundreds of thousands of free or paid applications are available for mobile devices, depending on the product.

Contents of the invention

technical problem

Although mobile devices are provided with many applications that stimulate users' interests and satisfy users' needs, mobile devices have limitations in display size and user interface (UI) due to their portable size. As a result, users feel inconvenienced when running multiple applications in their mobile devices. For example, when a user runs an application in a mobile device, the application is displayed over the entirety of the display area. If the user runs another application during the running of the current application, the user needs to first end the ongoing application and then select the run key to run the desired application. For example, a user needs to go through the frustrating process of repeatedly running and terminating each application in order to run multiple applications. However, methods for running multiple applications simultaneously on mobile devices have yet to be specified.

As described above, although mobile devices are provided with many applications that stimulate users' interest and meet user needs, mobile devices have limitations in display size and UI due to their portable size. As a result, users feel inconvenienced when running multiple applications in their mobile devices.

Therefore, there is a need to develop methods for displaying multiple windows on a single display. Furthermore, there is a need for a method of easily calling a plurality of windows and facilitating arrangement of windows after window calling.

More specifically, when multiple overlapping windows are displayed, it is necessary to specify a structure for switching the currently displayed window to another low-priority window.

The above information is presented as background information only to assist in understanding the present disclosure. No determination has been made or asserted whether any of the above might be available as prior art with respect to the present disclosure.

Technical solutions

Aspects of the present disclosure are to address at least the above problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present disclosure is to provide a display device that runs multiple windows in various sizes on a single display and facilitates switching from one window to another lower layer window, and a method for controlling the display device.

According to an aspect of the present disclosure, there is provided a method for controlling a display device having a touch screen and executing at least one application. The method includes: receiving an application running command for running at least one application; determining at least one of a size and a position of a window running the at least one application according to a position input by the application running command; and displaying the window according to at least one of the size and position of the window.

According to another aspect of the present disclosure, a display device is provided. The display device includes a touch screen configured to receive an application running command for running at least one application, and a controller configured to: determine at least one of a size and a position of a window for running the at least one application according to a position input by the application running command; and control display of the window on the touch screen according to at least one of the size and position of the window.

According to another aspect of the present disclosure, a method for executing an application in a display device including a touch screen is provided. The method includes: displaying an execution window of an application in each of a plurality of areas of the touch screen; displaying a button on at least one boundary separating the plurality of areas; receiving an input of selecting the button; and displaying in a specific area among the plurality of areas a list of at least one application running in the specific area according to the received input.

According to another aspect of the present disclosure, a method for executing an application in a display device including a touch screen is provided. The method includes: displaying a running window of an application in each of a plurality of areas of the touch screen; displaying a button on at least one boundary separating the multiple areas; displaying a list of at least one application running icon in a partial area of the touch screen; receiving a drag input for dragging the application running icon from the list; determining an area for running a new application according to an end position of the drag input and a position of a button;

According to another aspect of the present disclosure, a display device is provided. The display device includes: a touch screen configured to display an execution window of an application in each of a plurality of regions; displaying a button on at least one boundary separating the plurality of regions, and receiving an input of selecting the button; and a controller configured to display a list of at least one application running in a specific region among the plurality of regions according to the received input.

According to another aspect of the present disclosure, a display device is provided. The display device includes a touch screen and a controller configured to: display a running window of an application in each of a plurality of areas; display a button on at least one boundary separating the multiple areas; display a list of at least one application running icon in a partial area of the touch screen; and receive a drag input for dragging the application running icon from the list; the controller is configured to: determine an area for running a new application based on an end position of the drag input and a position of a button;

Other aspects, advantages and salient features of the present disclosure will become apparent to those skilled in the art from the following detailed description, taken in conjunction with the accompanying drawings, which discloses various embodiments of the present disclosure.

Description of drawings

The above and other aspects, features and advantages of specific embodiments of the present disclosure will become more apparent from the following description in conjunction with the accompanying drawings, in which:

FIG. 1 is a block diagram of a display device according to an embodiment of the present disclosure;

Figure 2a, Figure 2b, Figure 2c, Figure 2d, Figure 2e, Figure 2f, Figure 2g, Figure 2h, Figure 2i, Figure 2j and Figure 2k illustrate a window operation method according to an embodiment of the present disclosure;

3a, 3b, 3c, 3d, 3e, 3f, 3g, 3h and 3i illustrate action stacks managed in a display device according to an embodiment of the present disclosure;

FIG. 4a is a flowchart illustrating a method for controlling a display device according to an embodiment of the present invention;

FIG. 4b is a flowchart illustrating a method for controlling a display device according to an embodiment of the present invention;

FIG. 5 shows a display order (Z order) of windows according to an embodiment of the present disclosure;

Fig. 6a, Fig. 6b, Fig. 6c and Fig. 6d show the application running method according to the embodiment of the present disclosure;

7 is a flowchart illustrating a method for controlling a display device according to an embodiment of the present invention;

8a, 8b, 8c, 8d, 8e, 8f, 8g, 8h, 8i, 8j, 8k, 8l and 8m illustrate a method for displaying multiple windows according to an embodiment of the present disclosure;

Figures 9a, 9b, 9c, 9d, 9e, 9f, 9g and 9h illustrate layouts according to embodiments of the disclosure;

10a, 10b, 10c and 10d illustrate screens of display devices according to embodiments of the present disclosure;

11a, 11b and 11c illustrate screens of a display device according to an embodiment of the present disclosure;

12a, 12b and 12c illustrate screens of a display device according to an embodiment of the present disclosure;

13a, 13b and 13c illustrate screens of a display device according to an embodiment of the present disclosure;

14a, 14b and 14c illustrate screens of a display device according to an embodiment of the present disclosure;

15a, 15b and 15c illustrate screens of a display device according to an embodiment of the present disclosure;

16a, 16b, 16c and 16d illustrate screens of a display device according to an embodiment of the present disclosure;

FIG. 17 illustrates a screen of a display device according to an embodiment of the present disclosure;

Figures 18a and 18b illustrate a 9-region splitting scheme according to an embodiment of the present disclosure;

19 is a flowchart illustrating a method for controlling a display device according to an embodiment of the present invention;

20 is a flowchart illustrating a method for controlling a display device according to an embodiment of the present invention;

21a, 21b and 21c illustrate screens of a display device according to an embodiment of the present disclosure;

Figure 22 illustrates an action stack according to an embodiment of the disclosure;

23a and 23b illustrate screens of a display device describing Z-order changes according to an embodiment of the present disclosure;

Figure 24 illustrates an action stack according to an embodiment of the disclosure;

25a and 25b illustrate screens of a display device describing a Z order change command according to an embodiment of the present disclosure;

Figure 26 illustrates an action stack according to an embodiment of the disclosure;

27a and 27b illustrate screens of a display device describing a Z order change command according to an embodiment of the present disclosure;

Figure 28 illustrates an action stack according to an embodiment of the disclosure;

29a and 29b illustrate screens of a display device describing a Z order change command according to an embodiment of the present disclosure;

Figure 30 illustrates an action stack according to an embodiment of the present disclosure;

31a and 31b illustrate screens of a display device describing a Z order change command according to an embodiment of the present disclosure;

Figure 32 illustrates an action stack according to an embodiment of the present disclosure;

33a and 33b illustrate screens of a display device describing a Z-order change command according to an embodiment of the present disclosure;

Figure 34 illustrates an action stack according to an embodiment of the disclosure;

35 is a flowchart illustrating a method for controlling a display device according to an embodiment of the present invention;

36a, 36b and 36c illustrate screens of a display device describing a Z order change command according to an embodiment of the present disclosure;

37a, 37b and 37c illustrate action stacks according to embodiments of the disclosure;

38a, 38b, and 38c illustrate screens of a display device describing a Z-order change command according to an embodiment of the present disclosure;

Figure 39a, Figure 39b and Figure 39c illustrate action stacks according to embodiments of the present disclosure;

40a, 40b, 40c, 40d, 40e, 40f, 40g, 40h, 40i, 40j and 40k illustrate a method for displaying an application running window according to an embodiment of the present disclosure;

Figures 41a, 41b, 41c, 41d, 41e and 41f illustrate action stacks according to various embodiments of the present disclosure;

FIG. 42 is a flowchart illustrating a method for running an application in a display device according to an embodiment of the present invention;

43a and 43b illustrate a method for controlling a display area of an application execution window using a center button according to an embodiment of the present disclosure;

Figure 44a, Figure 44b, Figure 44c, Figure 44d, Figure 44e, Figure 44f, Figure 44g, Figure 44h, Figure 44i, Figure 44j, Figure 44k, Figure 44l, Figure 44m, Figure 44n, Figure 44o, Figure 44p, Figure 44q, Figure 44r, Figure 44s, Figure 44t, Figure 44u, Figure 44v and Figure 44w illustrate the A method for running multiple applications;

Figures 45a, 45b, 45c, 45d, 45e, 45f, 45g, 45h, 45i and 45j illustrate action stacks according to embodiments of the disclosure;

FIG. 46 illustrates a method for providing a user interface on which an application is executed in a display device according to an embodiment of the present invention;

FIG. 47 is a flowchart illustrating a method for running an application in a display device according to an embodiment of the present invention;

48 is a block diagram of a display device according to an embodiment of the present disclosure; and

49a, 49b, 49c, and 49d are diagrams illustrating a method for displaying a button according to an embodiment of the present disclosure.

Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures.

Detailed ways

The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the present disclosure as defined by the claims and their equivalents. The following description includes various specific details to aid in understanding, but these should be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the disclosure. Also, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are not limited to the bibliographical meanings, and the inventors used these data and words merely to enable a clear and consistent understanding of the present disclosure. Therefore, it should be apparent to those skilled in the art that the following descriptions of various embodiments of the present disclosure are provided for the purpose of illustration only, and are not intended to limit the present disclosure as defined by the claims and their equivalents.

It will 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 component surface" includes one or more of such surfaces.

With respect to the term "substantially", it means that the recited properties, parameters or values do not have to be achieved precisely, but deviations or variations may occur including, for example, tolerances, measurement errors, limits of measurement precision and other factors known to those skilled in the art, in any case not excluding the effect of the properties intended to be provided.

When an ordinal number such as first, second, etc. may be used to describe a plurality of components, the components are not limited by the term. This term is used to distinguish one 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" is meant to include a combination of a plurality of described associated items or one of the items.

Technical terms used herein are provided to describe various embodiments and are not intended to limit the present disclosure. Herein, singular expressions include plural expressions unless the context clearly indicates otherwise. In this description, the terms "comprising" or "having" are not interpreted as necessarily including all of the features, numbers, steps, operations, components, parts or combinations thereof described in the description. Rather, it should be understood that there is a possibility to omit or add one or more features, numbers, steps, operations, components, parts or combinations thereof.

Unless otherwise defined, all terms (including technical terms and scientific terms) used herein have the same meaning as commonly understood by those skilled in the art. Also, the terms defined in common dictionaries will be understood to have the same meanings as the contextual meanings of the prior art. Unless expressly defined herein, terms are not to be interpreted in an ideal or overly formal sense.

FIG. 1 is a block diagram of a display device according to an embodiment of the present disclosure.

Referring to FIG. 1 , the display device 100 may be connected to an external device (not shown) through the mobile communication module 120 , the sub-communication module 130 or the connector 165 . The term "external device" covers various devices such as another device (not shown), a mobile phone (not shown), a smartphone (not shown), a tablet personal computer (PC) (not shown), a server (not shown), and the like.

The display device 100 includes a touch screen 190 and a touch screen controller 195 . The display device 100 also includes a controller 110, a mobile communication module 120, a sub-communication 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 supply 180. The sub-communication module 130 includes at least one of a wireless local area network (WLAN) module 131 and a short-range communication module 132 . The multimedia module 140 includes at least one of a broadcast communication module 141 , an audio playing module 142 and a video playing 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 160 includes at least one of a button 161 , a microphone 162 , a speaker 163 , a vibration motor 164 , a connector 165 and a keypad 166 .

The controller 110 may include a central processing unit (CPU) 111, a read only memory (ROM) 112 storing a control program for controlling the display device 100, and a random access memory (RAM) 113 used as a storage space for operations performed by the display device 100. CPU 111 may include one or more cores. The CPU 111, ROM 112, and RAM 113 can be connected to each other through an internal bus.

The controller 110 may control the mobile communication module 120, the sub-communication module 130, the multimedia module 140, the camera module 150, the GPS module 155, the I/O module 160, the sensor module 170, the memory 175, the power supply 180, the touch screen 190, and the touch screen controller 195.

The mobile communication module 120 connects the display device 100 to external devices through mobile communication via one or more antennas (not shown) under the control of the controller 110 . The mobile communication module 120 transmits wireless signals to or receives wireless signals from a mobile phone (not shown), a smart phone (not shown), a tablet PC (not shown), or another device (not shown) having a phone number input to the display device 100, for voice calls, video calls, Short Message Service (SMS), or Multimedia Message Service (MMS).

The sub-communication module 130 may include at least one of a WLAN module 131 and a short-range communication module 132 .

The WLAN module 131 may be connected to the Internet under the control of the controller 110 at a place where a wireless AP (not shown) is installed. The WLAN module 131 supports a WLAN standard, Institute of Electrical and Electronics Engineers (IEEE) 802.11x. The short-range communication module 132 may implement short-range wireless communication between the display device 100 and an image forming device (not shown) under the control of the controller 110 . Short-range communications may conform to Bluetooth, Infrared Data Association (IrDA), Zigbee, and the like.

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

The multimedia module 140 may include a broadcast communication module 141 , an audio playing module 142 or a video playing module 143 . The broadcast communication module 141 may receive broadcast signals (eg, TV broadcast signals, radio broadcast signals, or data broadcast signals) and additional broadcast information (eg, electronic program guide (EPG) or electronic service guide (ESG)) from broadcast stations through a broadcast communication antenna (not shown) under the control of the controller 110. The audio playing module 142 may open a stored or received digital audio file (eg, a file having an extension such as mp3, wma, ogg, or wav) under the control of the control unit 110 . The video playing module 143 may open stored or received digital video files (eg, files with extensions such as mpeg, mpg, mp4, avi, mov, or mkv) under the control of the control unit 110 . The video playback module 143 can also open digital audio files.

The multimedia module 140 may include an audio playing module 142 and a video playing module 143 without the broadcast communication module 141 . Alternatively, the audio playing module 142 or the video playing module 143 of the multimedia module 140 may be incorporated into the controller 110 .

The camera module 150 may include at least one of a first camera 151 and a second camera 152 capturing still images or videos under the control of the control unit 110 . The first camera 151 or the second camera 152 may include an auxiliary light source (for example, a flash (not shown)) providing light intensity for capturing an image. The first camera may be disposed on the front surface of the display device 100 , and the second camera may be disposed on the rear surface of the display device 100 . Alternatively, the first camera 151 and the second camera 152 may be arranged close to each other (eg, the distance between the first camera 151 and the second camera 152 may be between 1 cm and 8 cm) to capture three-dimensional still images or video.

The GPS module 155 may receive signal waves from a plurality of GPS satellites (not shown) in earth orbit, and calculate a location of the display device 100 based on time of arrival (ToAs) of satellite signals from the GPS satellites to the display device 100 .

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

The buttons 161 may be formed on the front, side, or rear surface of the case of the display device 100, and may include a power on/lock button (not shown), a volume button (not shown), a menu button, a home button, a back button, and a search button.

The microphone 162 receives voice or sound and converts the received voice or sound into an electric signal under the control of the controller 110 .

The speaker 163 may output sounds corresponding to various signals received from the mobile communication module 120, the sub-communication module 130, the multimedia module 140, and the camera module 150 to the outside of the display device 100 (for example, wireless signals, broadcast signals, digital audio files, digital video files, photo shooting, etc.). The speaker 163 may output sounds corresponding to functions performed by the display device 100 (eg, button operation sounds, ringback tones for calls, etc.). One or more speakers 163 may be arranged at a suitable location or locations of the housing of the display device 100 .

The vibration motor 164 may convert electrical signals into mechanical vibrations under the control of the controller 110 . For example, the vibration motor 164 operates when the display device 100 receives an incoming voice call from another mobile device (not shown) in the vibration mode. One or more vibration motors 164 may be installed inside the housing of the display device 100 . The vibration motor 164 may operate in response to a user's touch on the touch screen 190 and continuous motion of the touch on the touch screen 190 .

The connector 165 may be used as an interface to connect the display device 100 to an external device (not shown) or a power source (not shown). The connector 165 may transmit data stored in the memory 175 to an external device via a cable connected to the connector 165 under the control of the controller 110 or may receive data from the external device via a cable. The display apparatus 100 may receive power from a power source or charge a battery (not shown) via a cable connected to the connector 165 .

The keypad 166 may receive key input from a user to control the display device 100 . The keypad 166 includes a physical keypad (not shown) formed in the display device 100 , or a virtual keypad (not shown) displayed on the display 190 . A physical keypad may not be provided according to the capabilities or configuration of the display device 100 .

The sensor module 170 includes at least one sensor (not shown) for detecting the state of the display device 100 . The sensor module 170 may include a proximity sensor that detects whether a user approaches the display device 100, an illuminance sensor that detects the amount of ambient light surrounding the display device 100, or a motion sensor that detects motion (eg, rotational acceleration, vibration, etc.) of the display device 100. At least one sensor may 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 . Sensors may be added to or removed from the sensor module 170 according to the capabilities of the device 100 .

The memory 175 may store input and output signals or data according to operations of the mobile communication 120, the sub-communication module 130, the multimedia module 140, the camera module 150, the GPS module 155, the I/O module 160, the sensor module 170, and the touch screen 190 under the control of the control unit 110. The memory 175 may store programs and applications for controlling the display device 100 or the controller 110 .

The term 'memory' covers the memory 175 installed in the display apparatus 100, the ROM 112 and RAM 113 within the controller 110, or a memory card (not shown) such as a Secure Digital (SD) card or a memory stick. The memory 110 may include nonvolatile memory, volatile memory, hard disk drive (HDD), or solid state drive (SSD).

The power supply 180 may supply power to one or more batteries (not shown) housed in the housing of the display device 100 under the control of the controller 110 . One or more batteries power the display device 100 . In addition, the power supply unit 180 may supply power received from an external power supply (not shown) to the display apparatus 100 via a cable connected to the connector 165 .

The touch screen 190 may provide a user interface (UI) corresponding to various services (eg, calling, data transmission, broadcasting, photography, etc.) to the user. The touch screen 190 may transmit an analog signal corresponding to at least one touch on the UI to the touch screen controller 195 . The touch screen 190 may receive at least one touch input through a user's body part (eg, finger) or a touch input device (eg, stylus pen). The touch screen 190 may also receive a touch input signal corresponding to a continuous motion of one touch among one or more touches. The touch screen 190 may transmit an analog signal corresponding to an input touch to the touch screen controller 195 .

As used in this description, "touch" may include contactless touch (i.e., a detectable gap between touch screen 190 and a user's part or touch input device is 1 mm or less), and need not be limited to contact between touch screen 190 and a user's body part or touch input implement. A gap detectable by the touch screen 190 may vary according to the capability or configuration of the display device 100 .

For example, the touch screen 190 may be implemented in a resistive type, a capacitive type, an infrared type, or an acoustic wave type.

The touch screen controller 195 converts analog signals received from the touch screen 190 into digital signals (eg, X and Y coordinates). The controller 110 may control the touch screen 190 using digital signals received from the touch screen controller 195 . For example, the controller 110 may control selection or execution of a shortcut icon (not shown) displayed on the touch screen 190 in response to a touch. The touch screen controller 195 may be incorporated into the controller 110 .

2a , 2b , 2c , 2d , 2e , 2f , 2g , 2h , 2i , 2j and 2k illustrate window operation methods according to embodiments of the present disclosure. Those skilled in the art will easily understand that the display device 200 may be any one of the display device 100 shown in FIG. 1 , a standard TV (television), Internet TV, a medical data display device, and the like. Therefore, any device can be used as a display device as long as it is equipped with means for displaying a presented image.

Referring to FIG. 2a, the display device 200 may define a plurality of window display areas 201, 202, 203, and 204 on the touch screen. For example, a controller (not shown) may configure the first window display area 201 , the second window display area 202 , the third window display area 203 and the fourth window display area 204 . The controller may set a first boundary line 211 between the first window display area 201 and the second window display area 202, a second boundary line 212 between the third window display area 203 and the fourth window display area 204, a third boundary line 213 between the first window display area 201 and the third window display area 203, and a fourth boundary line 214 between the second window display area 202 and the fourth window display area 204. The first boundary line 211 and the second boundary line 212 may be connected as a single line, and the third boundary line 213 and the fourth boundary line 214 may be connected as a single line. The controller configures the first to fourth window display areas 201, 202, 203, and 204 such that they do not overlap each other. Referring to 2a, for example, the controller defines the first window display area 201 at the upper left corner, defines the second window display area 202 at the upper right corner, defines the third window display area 203 at the lower left corner, and defines the fourth window display area 204 at the lower right corner. The controller divides the screen into a left half and a right half by a first boundary line 211 and a second boundary line 212 , and divides the screen into an upper half and a lower half by a third boundary line 213 and a fourth boundary line 214 .

The controller displays the center button 220 at an intersection point where the first border line 211 and the second border line 212 intersect with the third border line 213 and the fourth border line 214 . The center button 220 may be a function key to change the size of an application display area or transform the display device 200 into a window relocation mode.

The controller controls display of a window in each of the window display areas 201, 202, 203, and 204 to execute applications in the window. For example, as shown in Fig. 2b, Fig. 2c, Fig. 2d, Fig. 2e, Fig. 2f, Fig. 2g, Fig. 2h, Fig. 2i, Fig. 2j and Fig. 2k, the display of the window in each of the window display areas 201, 202, 203 and 204 is controlled by the controller.

The window may include an execution screen of a specific application and a title of the running application. Objects related to the application may be displayed on the running screen of the application. Objects can take many forms, such as text, graphics, icons, buttons, checkboxes, photos, videos, web pages, maps, and more. When a user touches an object, a function or event corresponding to the touched object may be executed in the application. An object may be called a view according to an operating system (OS). The title bar may include at least one control key to control the display of the window. For example, the at least one control key may include a window minimize button, a window maximize button, and a window close button.

An application is a program independently written by a manufacturer of the display device 200 or an application developer. Thus, the running of one application does not require the preparatory running of another application. Even when one application ends, another application can continue to run.

Compared to a combined function application (or dual application) designed by adding to one application (for example, a video application) some functions available to other applications (for example, a note function, a message sending/receiving function, etc.), applications are configured independently. Unlike existing applications, a combined function application is a single application configured to include multiple functions. Therefore, the combined function application only provides limited functions like existing applications, and the user will additionally purchase this new combined function application.

Referring to FIG. 2b , the controller controls the display of the first window 230 to run a startup application: application L in the first window display area 201 . As shown in Figure 2b, launching the application: application L displays available application icons 231 , 232 , 233 , 234 , 235 , 236 , 237 and 238 . When an application execution command is received through a touch on one of the application icons 231 , 232 , 233 , 234 , 235 , 236 , 237 and 238 , the application is started: the application L displays the application corresponding to the touched icon in one of the first to fourth display areas 201 , 202 , 203 and 204 .

3a, 3b, 3c, 3d, 3e, 3f, 3g, 3h and 3i illustrate action stacks managed in a display device according to an embodiment of the present disclosure.

Referring to FIG. 3a, the controller generates and manages a startup application in an action stack in response to execution of the startup application.

Referring to FIG. 2c and FIG. 2d, user 1 may touch an icon 232 representing application B. Referring to FIG. When the icon 232 representing the application B is touched, the controller controls to display the second window 240 in which the application B is executed in the second window display area 202 . The controller may display windows in the first to fourth window display areas 201, 202, 203, and 204 in order. For example, the controller may control the display of new windows in the clockwise order of the second window display area 202 , the third window display area 203 , and the fourth window display area 204 . The clockwise window display order is an example of controlling the display of new windows, and therefore, the controller may control the display of new windows in counterclockwise order. The order in which new windows are displayed in the window display areas 201, 202, 203, and 204 may be changed.

Fig. 3b shows an action stack corresponding to the window shown in Fig. 2d. The controller generates the application B stack 302 in the action stack in response to the execution of the application B. The controller places the last running application B stack 302 on top of the startup application stack 301 . This may imply that application B's Z-order (which may also be described as order, rank, or priority) is higher than the Z-order of the launching application: application L.

Referring to FIG. 2e, user 1 may touch an icon 233 corresponding to application C. Referring to FIG.

Fig. 3c shows an action stack corresponding to the window shown in Fig. 2e. Since User 1 enters an application run command to Launch Application: Application L as shown in Figure 2e, it is noted from Figure 3c that the Z-order of Launch Application L is higher than that of Application B.

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

Figure 3d shows an action stack corresponding to the window shown in Figure 2f. The controller generates the application C stack 303 in the action stack in response to the execution of the application C. The controller places the last running application C stack 303 on top of the startup application stack 301 . This may imply that the Z-order of application C is higher than that of the launching application: application L.

Referring to FIG. 2g, user 1 may touch an icon 234 representing application D. Referring to FIG.

Fig. 3e shows an action stack corresponding to the window shown in Fig. 2g. Since User 1 enters an application run command to Launch Application: Application L as shown in Figure 2g, it is noted from Figure 3e that the Z-order of Launch Application: Application L is higher than that of Application C.

Referring to FIG. 2h, when the icon 234 representing the application D is touched, the controller controls the display of the fourth window 260 in which the application D is executed in the third window display area 203. Referring to FIG.

Figure 3f shows an action stack corresponding to the window shown in Figure 2h. The controller generates an application D stack 304 in the action stack in response to the execution of the application D. The controller places the last running application D-stack 304 on top of the startup application stack 301 . This may imply that the Z-order of application D is higher than that of the startup application, Application L.

Referring to FIG. 2i , user 1 can operate application B. Referring to FIG.

Fig. 3g shows an action stack corresponding to the window shown in Fig. 2i. The controller places application B stack 302 on top of the action stack in response to user input for application B.

Referring to FIG. 2j , user 1 may touch an icon 235 representing application E. Referring to FIG.

Figure 3h shows the action stack corresponding to Figure 2j. Since User 1 enters the application run command to Launch Application: Application L as shown in Figure 2j, it is noted from Figure 3h that the Z-order of Application L is higher than the Z-order of Application D for Launch Application.

When the icon 235 representing the application E is touched, referring to FIG. 2k , the controller controls the display of the fifth window 270 in which the application E is executed in the fourth window display area 204 . In case there is no empty window display area, the controller can refer to the action stack shown in Fig. 3h. The controller can determine the application with the lowest Z-order in the action stack. For example, the controller may determine that application C's Z-order is the lowest in the action stack of Figure 3h. The controller controls the display of the fifth window 270 in which the application E is executed in the fourth window display area 204 instead of the window of the application C having the lowest Z order.

Fig. 3i shows an action stack corresponding to the window shown in Fig. 2k. The controller generates the application E stack 305 in the action stack in response to the execution of the application E. The controller places the last running application E-stack 305 on top of the startup application stack 301 . This may imply that the Z-order of application E is higher than the Z-order of the startup application, application L.

Fig. 4a is a flowchart illustrating a method for controlling a display device according to an embodiment of the present invention.

Referring to FIG. 4a, in operation S401, the display device may execute a plurality of applications. For example, a display device may run an application in response to an application run command triggered by a user touch on an icon representing the application. The display device, and in particular, the display device's window manager, can generate the windows in which the application runs.

A display device may determine a layout for arranging windows. A layout defines the window display area in which windows can be arranged. For example, two modes are available for layout, namely, split mode and freestyle mode.

In split mode, the screen is divided in such a way that multiple windows are displayed without overlapping. For example, if the display device displays a first window and a second window, the display may divide a screen such as a touch screen in a set layout and define the divided screen portion as a window display area. The display device can display windows in each window display area. Since each window display area is a screen segment, the display device can display multiple windows without overlapping.

A display device can assign multiple windows to one window display area in split mode. For example, the display device may assign the first window and the second window to the first window display area. In this case, the display device may compare the Z-order (order, rank, position in the stack) of the first window and the second window. If the Z-order of the first window is higher than the Z-order of the second window, the display device may display the first window in the first window display area. In this case, although the display device manages the second window to be arranged in the first window display area, the display device does not display the second window in the first window display area.

On the other hand, in Freestyle mode, multiple windows can be displayed overlapping according to their display priority. For example, if the display area of the first window overlaps the display area of the second window, the display device may compare the Z-orders of the first window and the second window. The Z-order of the windows may refer to the display order of the windows. For example, if the Z-order of the first window is higher than the Z-order of the second window, the display device may control to display the first window instead of the second window in the overlapping portion.

In split mode, various layouts are available, such as 2 top/bottom area split layouts, 2 left/right area split layouts, 3 area split layouts, 4 area split layouts and more. In operation S405, the display device may determine whether the layout of the window is in the split mode or the freestyle mode. If the layout is in split mode, the display device may further determine whether the layout is a 2 top/bottom area split layout, a 2 left/right area split layout, a 3 area split layout, or a 4 area split layout.

Once the mode of the layout is determined in operation S405, the display device may determine the window positions in the layout in operation S407. In the case of two upper/lower area layouts, the display device may determine to arrange the first window and the third window in the upper window display area and arrange the second window in the lower window display area. Alternatively, in the freestyle mode, the display device may determine a coordinate region for the first window and a coordinate region for the second window.

The display device may determine the Z-order of the plurality of applications in operation S409 and may display the plurality of windows based on the Z-order of the applications in operation S411. For example, in case of 2 upper/lower region split mode, the display device may compare the Z-orders of the first window and the third window. In addition, the display device can control to display windows with a relatively higher Z order in the corresponding window display area. In freestyle mode, the display device can compare the Z-orders of the first window and the second window and can control the window with the relatively higher Z-order to display in the overlapping region.

Fig. 4b is a flowchart illustrating a method for controlling a display device according to an embodiment of the present invention.

Referring to FIG. 4b, in operation S401, the display device may execute a plurality of applications. For example, the application run command may be triggered by a drag gesture of dragging an icon representing the application to a point at which a window for the application is to be displayed. A drag gesture input is an example of an application run command, therefore, the application can be run in various ways. It will be readily understood by those skilled in the art that the present disclosure is not limited to a particular method of application operation.

In operation S421, the display device may determine whether the current layout is in a freestyle mode. In case of the freestyle mode layout, in operation S423, the display device may determine a Z order of each of the windows in which the plurality of applications are executed. In operation S425, the display device may display the windows according to their Z-order.

In case of the split mode layout in operation S421, in operation S431, the display device may arrange windows in the window display area. Also, in operation S433, the display device may determine a Z order of windows in each window display area. For example, the display device may determine the Z-order of the windows as shown in Table 1.

[Table 1]

window Window display area (page) Z order A 1 1 B 2 5 C 3 6 D. 2 2 E. 1 3 f 4 4

As described above, the display device may control to display window A having a relatively higher Z order instead of window E in the first window display area. The display device may control to display window D having a relatively higher Z order instead of window B in the second window display area. Also, the display device may display window C in the third window display area and display window F in the fourth window display area. For example, in operation S435, the display device may display, in each window display area, a window having the highest Z-order among windows allocated to the window display area.

FIG. 5 illustrates a display order (Z order) of windows according to an embodiment of the present disclosure.

Referring to FIG. 5 , the Z order of the screen may be divided into N layers, and the Nth layer may be an upper layer placed on the (N-1)th layer. Windows can exist in each layer and applications can run in windows. For example, when running the first application, the first application runs in a window of the first layer. When the second application is executed, the second application is executed in a window of the second layer, and when the third application is executed, the third application is executed in a window of the third layer. Therefore, the first layer, the second layer and the third layer are created hierarchically. The layer created last can be the top of the layer stack and, therefore, can be displayed on top of the screen. For example, a plurality of windows (a) to (d) may be displayed overlappingly on the main screen. For example, the first window (a) is displayed overlapping the second window (b), the third window (c) and the fourth window (d), the second window (b) is displayed overlapping the third window (c) and the fourth window (d), and the third window (c) is displayed overlapping the fourth window (d). For example, when a plurality of windows (a) to (d) are overlapped and displayed, the order in which the windows (a) to (d) are displayed is the Z order of the windows (a) to (d). The Z-order may be the order in which the windows are displayed along the Z-axis. Layer view (e) may be a screen displaying Z-order of windows hierarchically. The Z-order may be referred to as a display order.

Fig. 6a, Fig. 6b, Fig. 6c and Fig. 6d illustrate an application running method according to an embodiment of the present disclosure. More specifically, Figures 6a, 6b, 6c and 6d illustrate a method for running an application in a freestyle mode layout.

Referring to FIGS. 6a , 6b , 6c and 6d , the display device 600 displays a window display area 620 . The display device 600 displays a tray 610 accommodating available application icons 611 , 612 , 613 , 614 , 615 , 616 , and 617 to the left of the window display area 620 . The user 10 may operate the display device 600 to execute the first application A1. For example, in FIG. 6 b , the user 10 may make a drag gesture 625 of dragging the icon 611 representing the first application A1 to the first point in the window display area 620 . The display device 600 may display the first window 630 at a first point in the window display area 620 in response to the drag gesture 625 to execute the first application A1 in the first window 630 . The first window 630 may be displayed in a default size and shape or in a size and shape set by the user 10 before being terminated.

The user 10 may operate the display device 600 to additionally execute the third application A3. For example, as shown in FIG. 6 c , the user 10 may make a drag gesture 635 of dragging the icon 613 representing the third application A3 to the second point in the window display area 620 . The display device 600 may display the third window 640 at the second point in the window display area 620 in response to the input execution command (ie, the drag gesture 635 ) to execute the third application A3 in the third window 640 . The third window 640 may be displayed in a default size and shape or in a size and shape set by the user 10 before being terminated. Since the third window 640 is the last window to which the user 10 has applied a gesture input, the controller (not shown) may assign a higher task priority level to the third application A3 than the first application A1. Accordingly, the controller may control the third application A3 to be displayed on the first application A1.

FIG. 7 is a flowchart illustrating a method for controlling a display device according to an embodiment of the present invention.

Referring to FIG. 7 , in operation S701, the display device may display at least one icon representing an application. For example, the display device may display a tray accommodating at least one icon in a portion of the touch screen.

In operation S703, when the user drags the icon to the first point where the window is to be arranged, the display device may receive a drag gesture input. The display device may recognize a drag gesture from the icon to the first point as a command to execute an application corresponding to the icon. More specifically, in operation S705, the display device may determine the position of the first point on the layout where the drag gesture has ended. For example, if the split mode has been set for the layout, the display device may determine the window area corresponding to the first point on the layout.

In operation S707, the display device may determine at least one of the size and position of the window according to the position of the first point on the layout. In operation S709, the display device may display the window according to the determined size and/or position.

8a, 8b, 8c, 8d, 8e, 8f, 8g, 8h, 8i, 8j, 8k, 8l, and 8m illustrate methods for displaying multiple windows according to embodiments of the present disclosure.

8a, 8b, 8c, 8d, 8e, 8f, 8g, 8h, 8i, 8j, 8k, 8l and 8m, the display device 800 displays a menu screen 817. The menu screen 817 may be an execution screen of a startup program and may include icons representing applications. In addition, the menu screen 817 may include information about the current time and may further include widgets. The display device 800 displays a tray 810 accommodating available icons 811, 812, 813, 814, 815, and 816 to the left of the touch screen.

As shown in FIG. 8b, the user 10 may operate the display device 800 to run the first application A. As shown in FIG. For example, as shown in FIG. 8 c , the user 10 may touch an icon 811 representing a first application A and drag the touched icon 811 to a menu screen 817 . A controller (not shown) may control the display of the icon 811 at the drag point. The controller may further control the display of a ghostview 818 at the drag point. The ghost view 818 refers to a preview of the size and shape of the window in which the first application A will run, so that the user 10 can select a window location. The controller may display the ghost view 818 full screen because no windows are already displayed. As described below, the controller may control the display of the full screen ghost view in the absence of any window already displayed on the touch screen. If a single window is already displayed on the touch screen, the controller may display the double view in a size and shape corresponding to half of the touch screen. If two windows are already displayed on the touch screen, the controller may display the double view in a size and shape corresponding to half of one of the two windows on the touch screen. If three windows have been displayed on the touch screen, the controller may display the double view in a size and shape corresponding to half of the largest one of the three windows.

The controller may recognize the above-mentioned drag gesture as a command for running a new application. The controller may generate a first window 819 for executing the first application A. Referring to FIG. As shown in FIG. 8d, the controller may control the display of the first window 819 in full screen.

The user 10 may operate the display device 800 to additionally execute the second application B. FIG. For example, as shown in FIG. 8e, the user may touch the icon 812 representing the second application B, and drag the touched icon 812 toward the lower half of the first window 819 as shown in FIG. 8f. The controller may control the display of the icon 812 at the dragged point. Also, the controller may control the display of the double view view 823 at the drag point. As previously described, since the single window 819 has been displayed on the touch screen, the controller may control the ghost view 823 to be displayed in a size and shape corresponding to half of the touch screen. Although not shown, if the user 10 drags the touched icon 812 toward the upper half of the touch screen, the controller controls the display of the ghost view 823 at the upper half of the touch screen. Displaying the double view on the lower half of the touch screen is just an example of displaying the double view, therefore, the controller may divide the touch screen into left and right halves and may control to display the double view in one of the left and right halves of the touch screen.

If the user finishes dragging in the lower half of the touch screen as shown in FIG. 8f, the controller determines that a new application execution command has been received. As shown in FIG. 8g, consistent with the double view view 823 shown in FIG. 8f, the controller controls to display a second window 830 in the lower half of the touch screen. In addition, the controller reduces the size and shape of the first window 819 to the 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 center button 825 at the border between the first window 820 and the second window 830 .

The user 10 may operate the display device 800 to additionally execute the third application C. FIG. For example, as shown in FIG. 8h , the user may touch the icon 813 representing the third application C, and drag the touched icon 813 to the right of the first window 820 as shown in FIG. 8i . The controller may control the icon 813 to be displayed at the dragged point. In addition, the controller may control the double view view 827 to be displayed at the dragged point. As previously described, since the two windows 820 and 830 have been displayed on the touch screen, the controller may control the display of the ghost view 827 in a size and shape corresponding to half of the first window 820 . Although not shown, if the user 10 drags the touched icon 813 to the left of the first window 820 , the controller controls to display a double view 827 in the left half of the first screen 820 . Displaying the double view 827 in the right half of the first window 820 is just an example of displaying the double view, and therefore, the controller may divide the first window 820 into an upper half and a lower half and may control to display the double view 827 in one of the upper half and the lower half of the first screen 820. Displaying a ghost view 827 in half of the first window 820 is another example of displaying a ghost view. The controller may determine the size and shape of the ghost view 827 relative to the center button 825 and display the ghost view 827 accordingly.

If the user finishes dragging in the right part of the first window 820 as shown in FIG. 8i, the controller determines that a new application execution command has been received. As shown in FIG. 8j , the controller controls to display a third window 840 in the right half of the first screen 820 , consistent with the double view view 827 shown in FIG. 8i . Alternatively, in line with the position of the center button 825, the controller may control the third window 840 to be displayed. Thus, as more applications are selected to run, portions of the screen may gradually be subdivided to assign each running application a respective portion of the screen.

In addition, the controller reduces the size and shape of the first window 820 in line with the creation of the third window 840 . For example, the controller may control the first window 820 to be displayed in an area other than the display area of the third window 840 .

The user 10 may operate the display device 800 to additionally execute the fourth application D. FIG. For example, as shown in FIG. 8k , the user may touch the icon 814 representing the fourth application D, and drag the touched icon 814 to the right of the second window 830 as shown in FIG. 81 . The controller may control the icon 814 to be displayed at the dragged point. In addition, the controller may control the double view view 831 to be displayed at the dragged point. As previously described, since the three windows 820 , 830 and 840 have been displayed on the touch screen, the controller may control the display of the ghost view 831 in a size and shape corresponding to half of the second window 830 . Although not shown, if the user 10 drags the touched icon 814 to the left of the second window 830 , the controller controls the display of the double view view 831 in the left half of the second screen 830 . Displaying the double view 831 in the right half of the second window is just an example of displaying the double view, and thus, the controller may divide the second window 830 into upper and lower halves and may control to display the double view 831 in one of the upper and lower halves of the second screen 830. Displaying the double view 831 in half of the second window 830 is another example of displaying the double view. The controller may determine the size and shape of the ghost view 831 relative to the center button 825 and display the ghost view 831 accordingly.

If the user finishes dragging in the right portion of the second window 830 as shown in FIG. 81 , the controller determines that a new application execution command has been received. As shown in FIG. 8j , consistent with the double view view 831 shown in FIG. 8l , the controller controls to display a fourth window 850 in the right half of the second screen 830 . Alternatively, consistent with the position of the center button 825, the controller may control the fourth window 850 to be displayed.

In addition, the controller reduces the size and shape of the second window 830 in line with the creation of the fourth window 850 .

As described above, the display device may control the window to be displayed in the window display area where the drag gesture ends. In Fig. 8a, Fig. 8b, Fig. 8c, Fig. 8d, Fig. 8e, Fig. 8f, Fig. 8g, Fig. 8h, Fig. 8i, Fig. 8j, Fig. 8k, Fig. 8l and Fig. 8m, the windows are displayed at different positions with the same size. 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, 15 b. Fig. 15c, Fig. 16a, Fig. 16b, Fig. 16c, Fig. 16d and Fig. 17, various embodiments of disposing windows at different positions with different sizes will be described below.

Figures 9a, 9b, 9c, 9d, 9e, 9f, 9g and 9h illustrate layouts according to embodiments of the disclosure.

Fig. 9a shows a full screen layout for the case where no split mode is set. In FIG. 9a, the display device defines a first window display area 901 throughout the entire screen.

FIG. 9 b shows an input area 902 corresponding to the first window display area 901 .

Figure 9c shows the screen layout in 2 up/down area split mode. In FIG. 9c, the display device may divide the screen into an upper area and a lower area and define a first window display area 911 and a second window display area 912 in the upper area and the lower area, respectively.

Figure 9d shows the input area in 2 upper/lower area split mode. The first input area 913 may correspond to the first window display area 911 and the third input area 915 may correspond to the second window display area 912 . The second input area 914 may correspond to a boundary between the first window display area 911 and the second window display area 912 . For example, when the user makes a drag gesture of dragging an icon toward the first input area 913, the display device may display a window in the first window display area 911 shown in FIG. 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 shown in FIG. 9c. For example, when the user drags an icon to the second input area 912, the display device may display windows throughout the entire first window display area 911 and the second window display area 912 shown in FIG. 9c.

Figure 9e shows the screen layout in 2 left/right area split mode. In FIG. 9e, the display device may divide the screen into left and right regions and define a first window display region 921 and a second window display region 922 in the left and right regions, respectively.

Figure 9f shows the input area in 2 left/right area split mode. The first input area 923 may correspond to the first window display area 921 and the third input area 925 may correspond to the second window display area 922 . The second input area 924 may correspond to a boundary between the first window display area 921 and the second window display area 922 . For example, when the user makes a drag gesture of dragging an icon toward the first input area 923, the display device may display a window in the first window display area 921 shown in FIG. 9e. 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 shown in FIG. 9e. For example, when the user drags an icon to the second input area 924, the display device may display windows throughout the entire first window display area 921 and the second window display area 922 shown in FIG. 9e.

FIG. 9g shows a layout in a 4-area split mode according to an embodiment of the present disclosure, and FIG. 9h shows an input area defined according to the layout in a 4-area split mode shown in FIG. 9g.

Referring to FIGS. 9g and 9h , the display device defines first to fourth window display areas 931 , 932 , 933 and 934 . Accordingly, a user may operate the display device to execute a window in any one of the first to fourth window display areas 941 , 942 , 943 and 944 . For example, when the user drags an icon representing an application to the third input area 932 , the display device may arrange and display windows in the second window display area 932 . If the user completes the drag gesture at the boundary between the first display area 931 and the second display area 932 , the display device may display windows throughout the first window display area 931 and the second window display area 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 window display area 932 . The display device may further define a fifth input area 945 at a boundary between the first window display area 931 and the second window display area 932 . Similarly, the display device may define a third input area 943 and a fourth input area 944 corresponding to the third window display area 933 and the fourth window display area 934, respectively. The display device may further define a sixth input area 946 at the boundary between the first window display area and the third window display area 933, a seventh input area 947 at the boundary between the second window display area 932 and the fourth window display area 934, and an eighth input area 948 at the boundary between the third window display area 933 and the fourth window display area 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 for displaying the window based on the mapping relationship shown in Table 2.

[Table 2]

As described above, the display device may define an input area for determining the application display area in which the drag gesture ends. More specifically, the display device may define an input area corresponding to a boundary between a plurality of window display areas or an input area corresponding to a cross point where a plurality of window display areas meet. When the drag gesture ends in an input area corresponding to a boundary between window display areas, the display device may display windows throughout all of these window display areas. When the drag gesture ends in the input area corresponding to the intersection where multiple window display areas meet, the display device may display the window across all of the window display areas. A display device can display windows in different sizes and at different positions. 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 configuration in which windows are displayed at different positions in different sizes is described in detail. More specifically, 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 1 7 shows the layout in 4 area split mode. Therefore, Figures 9g and 9h will also refer to the following description.

10a, 10b, 10c, and 10d illustrate screens of a display device according to an embodiment of the present disclosure.

10a, 10b, 10c, and 10d, the controller controls to display a window display area 1000 and a tray 1010 accommodating available icons 1011, 1012, 1013, 1014, 1015, 1016, and 1017 representing applications. The controller may display the tray 1010 at all times. Alternatively, the controller may display the tray 1010 only when a tray calling command is received. A tray call command may be generated in response to an edge flick received from the left side of the touch screen. Those skilled in the art will readily understand that the present disclosure is not limited to the type of input that triggers the tray call command. Assume that the display device is displaying a first window in which application A is running in window display area 1000 .

Referring to FIG. 10 b , the user 10 may make a drag gesture 1021 of dragging the icon 1016 representing the application F toward the first point 1027 in the lower half of the window display area 1000 . In FIG. 10c, the controller may determine a window display area. In case of a 4-area layout, the controller may 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 FIG. 9h, the controller may determine to display the F window 1024 throughout the third window display area 933 and the fourth window display area 934 as shown in Table 2. Afterwards, the controller may display a double view view 1023 in the determined area.

The user 10 can determine whether the window will be displayed at the desired position by viewing the double view view 1023 . The user 10 may release the drag gesture 1021, and the F-window 1024 may be displayed over the entirety of the third window display area 933 and the fourth window display area 934 as shown in FIG. 10d. Since the F window 1024 is displayed, the controller may reduce the size of the A window 1000 to half and display the shrunk A window 1000 . The controller may scale down the A-window 1000 at the same horizontal-to-vertical ratio or at a new horizontal-to-vertical ratio.

11a, 11b, and 11c illustrate screens of a display device according to an embodiment of the present disclosure. More specifically, Figures 11a, 11b, and 11c illustrate subsequent operations for the operations of Figures 10a, 10b, 10c, and 1Od.

Referring to FIG. 11a, the display device displays an A window 1000 and an F window 1024 in the upper half and the lower half of the screen, respectively, in a split mode. The user 10 can operate the display device 800 to additionally execute the application E. FIG. The user 10 may make a drag gesture 1032 by dragging the icon 1015 representing the application E towards the second point 1033 .

Referring to FIGS. 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 shown in FIG. Accordingly, the controller may display the determined window display area as a ghost view 1031 .

The user 10 can determine whether a window will be displayed at a desired position by viewing the double view view 1031 . User 10 may release drag gesture 1032 . The E window 1034 may be displayed over the entirety of the third window display area 933 and the fourth window display area 934 .

12a, 12b, and 12c illustrate screens of a display device according to an embodiment of the present disclosure. More specifically, Figures 12a, 12b, and 12c illustrate subsequent operations to the operations of Figures 11a, 11b, and 11c.

Referring to FIG. 12a, the display device displays an A window 1000 and an E window 1034 in the upper half and the lower half of the screen, respectively, in a split mode. The user 10 can operate the display device to additionally run the application G. The user 10 may make a drag gesture 1041 of dragging the icon 1017 representing the application G toward the third point 1042 .

Referring to FIGS. 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 shown in FIG. Accordingly, the controller may display the determined window display area as a ghost view 1043 .

The user 10 can determine whether the window will be displayed at the desired position by viewing the double view view 1043 . User 10 may release drag gesture 1042 . The G-window 1044 can be displayed in full screen, as shown in FIG. 12c.

13a, 13b, and 13c illustrate screens of a display device according to an embodiment of the present disclosure. More specifically, Figures 13a, 13b, and 13c illustrate subsequent operations for the operations of Figures 12a, 12b, and 12c.

Referring to FIGS. 13a , 13b and 13c , the display device is displaying a G window 1044 . The user 10 may make a drag gesture 1051 of dragging the icon 1012 representing the application B towards the fourth point 1052 in the lower half of the G window 1044 in FIG. 13b. When the controller determines that the fourth point 1052 corresponds to the eighth input area 948 shown in FIG. Accordingly, the controller may display the determined window display area as a ghost view 1053 .

The user 10 can determine whether the window will be displayed at the desired position by viewing the double view view 1053 . User 10 may release drag gesture 1052 . The B window 1054 may be displayed over the entirety of the third window display area 933 and the fourth window display area 934 as shown in FIG. 13c. Since the B window 1054 is displayed, the controller may shrink the G window 1044 to half of the screen and display the shrunk G window 1044 in the upper half of the screen.

14a, 14b, and 14c illustrate screens of a display device according to an embodiment of the present disclosure. More specifically, Figures 14a, 14b, and 14c illustrate subsequent operations for the operations of Figures 13a, 13b, and 13c.

Referring to FIG. 14a, the display device displays a G window 1044 and a B window 1054 in the upper half and the lower half of the screen, respectively, in a split mode. The user 10 can operate the display device to additionally run the application G. The user 10 may make a drag gesture 1061 of dragging the icon 1013 representing the application B toward the fifth point 1062 .

Referring to FIGS. 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 shown in FIG. Accordingly, the controller may display the determined window display area as a ghost view 1063 .

The user 10 can determine whether the window will be displayed at the desired position by viewing the double view view 1063 . User 10 may release drag gesture 1061 . A C window 1064 may be displayed in the second window display area 932, as shown in FIG. 14c.

15a, 15b, and 15c illustrate screens of a display device according to an embodiment of the present disclosure. More specifically, Figures 15a, 15b, and 15c illustrate subsequent operations for the operations of Figures 14a, 14b, and 14c.

Referring to FIG. 15a, the display device displays a G window 1044, a B window 1054, and a C window 1064 in a 3-region split mode. The user 10 can operate the display device to additionally execute the application D. The user 10 may make a drag gesture 1071 of dragging the icon 1014 representing the application D towards the sixth point 1072 .

Referring to FIGS. 15 b and 15 c , 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 shown in FIG. Accordingly, the controller may display the determined window display area as a ghost view 1073 .

The user 10 can determine whether the window will be displayed at the desired location by viewing the double view view 1073 . User 10 may release drag gesture 1071 . A D window 1074 may be displayed in the fourth window display area 934, as shown in FIG. 15c.

16a, 16b, 16c, and 16d illustrate screens of a display device according to an embodiment of the present disclosure.

FIG. 16a illustrates a screen of a display device according to an embodiment of the present disclosure. More specifically, Fig. 16a illustrates subsequent operations for the operations of Figs. 15a, 15b, and 15c.

Referring to FIG. 16a, the display device displays a G window 1044, a B window 1054, a C window 1064, and a D window 1074 in a 4-region split mode. The user 10 can operate the display device to additionally run the application H. The user 10 may make a drag gesture of dragging the icon 1018 representing the application H toward the seventh point 1081 .

Referring to FIG. 16a, the controller may determine an input area corresponding to the seventh point 1081. Referring to FIG. If the controller determines that the seventh point 1081 corresponds to the fifth input area 945 shown in FIG. Accordingly, the controller may display the determined window display area as a ghost view 1082 . Icons 1015 , 1016 , 1017 , 1018 , 1019 , 1020 , and 1021 representing applications E to K may be arranged in the tray 1010 . For example, user 10 may input an upward drag gesture across tray 1010 so that hidden icons 1018 , 1019 , 1020 , and 1021 representing applications H through K may be revealed in tray 1010 .

The user 10 can determine whether the window will be displayed at the desired location by viewing the ghost view 1082 . User 10 may release the drag gesture. The H window 1083 may be displayed in the first window display area 931 and the second window display area 932, as shown in FIG. 16a.

FIG. 16b illustrates a screen of a display device according to an embodiment of the present disclosure. More specifically, Figure 16b illustrates a subsequent operation for the operations of Figures 15a, 15b, and 15c.

Referring to FIG. 16b, the display device displays a G window 1044, a B window 1054, a C window 1064, and a D window 1074 in a 4-region split mode. The user 10 can operate the display device to additionally run the application H. The user 10 may make a drag gesture by dragging the icon 1018 representing application H towards the eighth point 1084 .

Referring to FIG. 16b , the controller may determine an input zone corresponding to the eighth point 1084 . If the controller determines that the eighth point 1084 corresponds to the sixth input area 946 shown in FIG. Accordingly, the controller may display the determined window display area as a ghost view 1085 .

The user 10 can determine whether the window will be displayed at the desired location by viewing the ghost view 1085 . User 10 may release the drag gesture. The H window 1086 may be displayed in the first window display area 931 and the third window display area 933, as shown in FIG. 16b.

FIG. 16c illustrates a screen of a display device according to an embodiment of the present disclosure. More specifically, FIG. 16c illustrates subsequent operations for the operations of FIGS. 15a, 15b, and 15c.

Referring to FIG. 16c, the display device displays a G window 1044, a B window 1054, a C window 1064, and a D window 1074 in a 4-region split mode. The user 10 can operate the display device to additionally run the application H. The user 10 may make a drag gesture of dragging the icon 1018 representing the application H towards the ninth point 1087 .

Referring to FIG. 16c, the controller may determine an input area corresponding to the ninth point 1087. Referring to FIG. If the controller determines that the ninth point 1087 corresponds to the eighth input area 948 shown in FIG. Accordingly, the controller may display the determined window display area as a ghost view 1088 .

The user 10 can determine whether the window will be displayed at the desired location by viewing the ghost view 1088 . User 10 may release the drag gesture. The H window 1089 may be displayed in the third window display area 933 and the fourth window display area 934, as shown in FIG. 16c.

FIG. 16d illustrates a screen of a display device according to an embodiment of the present disclosure. More specifically, Figure 16d illustrates subsequent operations for the operations of Figures 15a, 15b, and 15c.

Referring to FIG. 16d, the display device displays a G window 1044, a B window 1054, a C window 1064, and a D window 1074 in a 4-region split mode. The user 10 can operate the display device to additionally run the application H. The user 10 may make a drag gesture of dragging the icon 1018 representing the application H towards the tenth point 1090 .

Referring to FIG. 16d, the controller may determine an input zone corresponding to a tenth point 1090. Referring to FIG. If the controller determines that the tenth point 1090 corresponds to the seventh input area 947 shown in FIG. Accordingly, the controller may display the determined window display area as a ghost view 1091 .

The user 10 can determine whether the window will be displayed at the desired position by viewing the double view view 1091 . User 10 may release the drag gesture. The H window 1092 may be displayed in the second window display area 932 and the fourth window display area 934, as shown in FIG. 16d.

FIG. 17 illustrates a screen of a display device according to an embodiment of the present disclosure. More specifically, Figure 17 illustrates subsequent operations for the operations of Figures 15a, 15b, and 15c.

Referring to FIG. 17, the display device displays a G window 1044, a B window 1054, a C window 1064, and a D window 1074 in a 4-region split mode. The user 10 can operate the display device to additionally run the application H. The user 10 may make a drag gesture of dragging the icon 1018 representing the application H towards the eleventh point 1093 .

Referring to FIG. 17 , the controller may determine an input area corresponding to an eleventh point 1093 . If the controller determines that the eleventh point 1093 corresponds to the ninth input area 949 shown in FIG. Accordingly, the controller may display the determined window display area as a ghost view 1094 .

The user 10 can determine whether the window will be displayed at the desired location by viewing the ghost view 1094 . User 10 may release the drag gesture. The H window 1095 can be displayed in full screen.

As described above, the display device may provide windows in different sizes at different positions according to the end point of the drag gesture. Although 4 region split modes have been described above, the above description can be extended to 9 region split modes and so on.

Figures 18a and 18b illustrate a 9-region split mode according to an embodiment of the disclosure.

Referring to FIGS. 18a and 18b, the display device may define 9 split window display areas. In addition, the display device may define input areas A, C, E, K, M, O, U, W, and Y corresponding to 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 G, I, Q, and S corresponding to intersection points where the window display areas meet. When the end point of the drag gesture is located in the input area corresponding to the boundary between the display areas, the display device may display the window over the entirety of the window display area. When the end point of the drag gesture is located in the input area corresponding to the intersection where the window display areas meet, the display device may display the window across the entirety of the window display area. In this way, the display device can display the window in different sizes at different positions according to the end point of the drag gesture.

FIG. 19 is a flowchart illustrating a method for controlling a display device according to an embodiment of the present invention.

Referring to FIG. 19 , in operation S1901, the display device may display at least one icon representing an application. In operation S1903, the display device may receive a drag gesture of dragging the icon toward the first point. In operation S1905, the display device may determine a position of the end of the drag gesture on the layout.

In operation S1907, the display device may determine whether the drag gesture ends at a boundary between window display areas. If the drag gesture ends at the boundary between the window display areas, the display device may display the window over the entirety of the window display areas in operation S1909.

In operation S1911, the display device may determine whether the drag gesture ends at an intersection where window display areas meet. If the drag gesture ends at an intersection where the window display areas meet, the display device may display the window over the entirety of the window display area in operation S1913.

In operation S1915, the display device may determine whether the drag gesture ends in the window display area. If the drag gesture ends in the window display area, the display device may display the window in the window display area in operation S1917.

FIG. 20 is a flowchart illustrating a method for controlling a display device according to an embodiment of the present invention.

Referring to FIG. 20 , in operation S2001, the controller may set a layout in a split mode. In operation S2003, the controller may define a plurality of window display areas according to the split mode. Also, the controller may assign a plurality of windows to the window display area in operation S2005. More specifically, the controller can assign a plurality of windows to one window display area.

In operation S2007, the controller may control a window having the highest Z-order among windows allocated to the window display area to be displayed in each window display area. For example, if a plurality of windows are allocated to the first window display area, the controller may control to display a window having the highest Z-order among the allocated windows.

In operation S2009, the controller may determine whether a Z-order change command has been received through the touch screen. The Z-order change command is a command to request to change the Z-order of windows. For example, a Z-order change command can be triggered by a flick gesture on the touch screen. When the Z-order change command is received in operation S2009, the controller may change at least one Z-order and display a window based on the changed Z-order in operation S2011.

21a, 21b, and 21c illustrate screens of a display device according to an embodiment of the present disclosure.

21a, the display device 2100 displays a first window 2101 for running application A in a first area, a second window 2102 for running application B in a second area, a third window 2103 for running application C in a third area, and a fourth window 2104 for running application D in a fourth area. The display device 2100 further displays a center button 2110 .

FIG. 22 illustrates an action stack according to an embodiment of the disclosure.

Referring to FIG. 22, a controller (not shown) may manage an action stack on the left. The controller may manage the Z-order of the windows in the order of applying C, F, G, A, D, B, J, K, H, M, L, and I. The controller assigns windows for applications C, F, and G to the third region, assigns windows for applications A, J, and L to the first region, assigns windows for applications D, H, and M to the fourth region, and assigns windows for applications B, K, and I to the second region.

The controller detects applications assumed to be running in the first zone and compares the Z-orders of the detected applications. The controller may determine that application A has the highest Z-rank in the first region. Accordingly, the controller controls to display the first window 2101 in which the application A is running in the first area. The controller detects applications assumed to be running in the second zone and compares the Z-orders of the detected applications. The controller may determine that application B has the highest Z-rank in the second region. Accordingly, the controller controls to display the second window 2102 in which the application B is running in the second area. The controller detects applications assumed to be running in the third region and compares the Z-orders of the detected applications. The controller may determine that application C has the highest Z-rank in the third region. Accordingly, the controller controls to display the third window 2103 in which the application B is running in the third area. The controller detects applications assumed to be running in the fourth region and compares the Z-orders of the detected applications. The controller may determine that application D has the highest Z-rank in the fourth region. Accordingly, the controller controls to display a fourth window 2104 in which the application B is running in the fourth area.

Continuing to refer to FIG. 21a, the user 1 may input a Z-order change command to the third area. For example, User 1 may make a right flick gesture 2120 across the third area. The controller may recognize the right flick gesture 2120 as a Z-order change command. The right flick gesture 2120 may be configured to assign the highest Z-order command to the application with the lowest Z-order in the window display area. The Z-order change is reflected in the action stack on the right shown in FIG. 22 . Note from the action stack on the right shown in FIG. 22 that application G is at the top of the action stack. The right flick gesture 2120 is an example of assigning the Z order in the window display area, and thus, those skilled in the art will easily understand that the Z order change command may be defined by a gesture made in a direction other than right. For example, a Z-order change command may be defined by various gestures, such as a left flick gesture, a downward flick gesture, an upward flick gesture, and so on. Furthermore, many other gestures besides flick gestures, including tilting, dragging, shaking, etc., may be defined as Z-order changing commands, which shall not be construed as limiting the present disclosure. Herein, the rightward direction may be referred to as a first direction, and the first direction is not limited to the rightward direction.

Referring to FIGS. 21b and 21c , the controller may control to display a fifth window 2113 in the third area in order to execute the application G. Referring to FIG. When a Z-order change command is received through a rightward flick gesture across the third area, the controller may determine that application F has the lowest Z-order in the third area, as shown in FIG. 21c. The controller may control a sixth window 2123 to be displayed in the third area in order to execute the application F.

23a and 23b illustrate screens of a display device describing a Z-order change according to an embodiment of the present disclosure. FIG. 24 illustrates an action stack according to an embodiment of the disclosure. Figure 23a may be substantially the same as Figure 21c, and the action stack on the left shown in Figure 24 may describe the Z-order of the windows displayed in Figure 23a.

Referring to FIG. 23a, the user 1 may input a Z-order change command to the first area by making a rightward flick gesture 2121 across the first area. A controller (not shown) may determine that the application L has the lowest Z-order in the th region. The controller can assign the highest Z-order to application L, as shown in the right-hand action stack shown in FIG. 24 .

Referring to FIG. 23b, the controller may control a seventh window 2131 to be displayed in the first area in order to execute the application L. Referring to FIG.

25a and 25b illustrate screens of a display device describing a Z-order change according to an embodiment of the present disclosure. FIG. 26 illustrates an action stack according to an embodiment of the disclosure.

Referring to FIGS. 25 a and 25 b , the user may input a Z-order change command to the second area by making a leftward flick gesture 2130 across the second area. A controller (not shown) may recognize a flick gesture to the left as a Z-order change command. A flick gesture to the left may be configured as a command to assign the lowest Z-order to the application with the highest Z-order in the window display area. The leftward direction may be referred to as a second direction.

Accordingly, the controller may assign the lowest Z-order to the application with the highest Z-order in the second region, as shown in the right-hand action stack shown in FIG. 26 . Since application B is assigned the lowest Z-rank, the controller may control application K in the second region to be assigned the highest Z-rank.

Accordingly, the controller may display an eighth window 2142 in the second area to execute the application K, as shown in FIG. 25b. The resulting action stack changes are shown in FIG. 26 .

As previously described, the controller may recognize the flick gesture to the left as a command to assign the highest Z-order to the application having the lowest Z-order in the window display area. Also, the controller may recognize the flick gesture to the right as a command to assign the lowest Z-order to the application having the second highest Z-order in the window display area. Therefore, the user can easily switch to the screen with the lowest or highest Z-order application.

27a and 27b illustrate screens of a display device describing a Z-order change command according to an embodiment of the present disclosure. FIG. 28 illustrates an action stack according to an embodiment of the disclosure.

27a and 27b, the display device 2100 displays a first window 2101 in a first area to run application A, displays a second window 2102 in a second area to run application B, displays a third window 2103 in a third area to run application C, and displays a fourth window 2104 in a fourth area to run application D. The display device 2100 may manage an action stack as shown in FIG. 28 . User 1 can input a Z-order change command to the third area. For example, the user 1 may make a tilt gesture 2700 to the right when touching a third area as indicated by reference numeral 2701 . The controller may recognize touch and tilt gestures to the right as Z-order change commands.

The controller may change the Z order in the action stack shown in FIG. 28 based on the Z order change command, which has been previously described with reference to FIG. 22 and thus will not be described too much. The controller may control to display a fifth window 2113 in the third area in order to execute the application G, as shown in FIG. 27b.

29a and 29b illustrate screens of a display device describing a Z-order change command according to an embodiment of the present disclosure.

29a and 29b, the display device 2100 displays a first window 2101 in the first area to run application A, displays a second window 2102 in the second area to run application B, displays a third window 2103 in the third area to run application C, and displays a fourth window 2104 in the fourth area to run application D. The display device 2100 may manage an action stack as shown in FIG. 30 . User 1 can input a Z-order change command to the second area. For example, when touching the second area as indicated by reference numeral 2901 , the user 1 may make a tilt gesture 2900 to the left. The controller may recognize touch and tilt gestures to the left as Z-order change commands.

The controller may change the Z order in the action stack shown in FIG. 30 based on the Z order change command, which has been previously described with reference to FIG. 26 and thus will not be described too much. The controller may control to display an eighth window 2142 in the second area in order to execute the application K, as shown in FIG. 29b.

31a and 31b illustrate screens of a display device describing a Z-order change command according to an embodiment of the present disclosure. FIG. 32 illustrates an action stack according to an embodiment of the disclosure.

31a, 31b and 32, the display device 2100 displays a first window 2101 in a first area to run application A, displays a second window 2102 in a second area to run application B, displays a third window 2103 in a third area to run application C, and displays a fourth window 2104 in a fourth area to run application D. The display device 2100 may manage an action stack as shown in FIG. 32 . User 1 can input a Z-order change command to the third area. For example, User 1 may touch a point 3100 in the third area and make a flick gesture 3101 to the right edge in the third area. The controller may recognize a flick gesture to the right edge as a Z-order change command.

The controller can change the Z order in the action stack shown in FIG. 32 based on the Z order change command, which has been previously described with reference to FIG. 22 and thus will not be described too much. The controller may control a fifth window 2113 to be displayed in the third area in order to execute the application G, as shown in FIG. 31b.

33a and 33b illustrate screens of a display device describing a Z-order change command according to an embodiment of the present disclosure. FIG. 34 illustrates an action stack according to an embodiment of the disclosure.

33a, 33b and 34, the display device 2100 displays a first window 2101 in a first area to run application A, displays a second window 2102 in a second area to run application B, displays a third window 2103 in a third area to run application C, and displays a fourth window 2104 in a fourth area to run application D. The display device 2100 may manage an action stack as shown in FIG. 34 .

User 1 can input a Z-order change command to the second area. For example, User 1 may touch a point 3300 in the second area and make an edge flick gesture 3301 to the left in the second area. The controller may recognize a flick gesture to the left edge as a Z-order change command.

The controller can change the Z order in the action stack shown in FIG. 34 based on the Z order change command, which has been previously described with reference to FIG. 26 and thus will not be described too much. The controller may control to display an eighth window 2142 in the second area in order to execute the application K, as shown in FIG. 33b.

The method of changing the Z-order in split mode has been described so far. Now, a description will be given of a method of changing the Z order in the freestyle mode.

FIG. 35 is a flowchart illustrating a method for controlling a display device according to an embodiment of the present invention.

Referring to FIG. 35 , the controller may set a layout in a freestyle mode in operation S3501. The controller may receive an application execution command, and thus, a plurality of windows for executing a plurality of applications may be generated in operation S3503. The controller may determine a Z order of each of the plurality of windows in operation S3505 and may display the windows based on their Z order in operation S3507.

In operation S3509, the controller may determine whether a Z-order change command has been received. When the Z order change command is received, the controller may control overlapping windows to be displayed according to the changed Z order in operation S3511.

36a, 36b, and 36c illustrate screens of a display device describing a Z-order change command according to an embodiment of the present disclosure and FIGS. 37a, 37b, and 37c illustrate action stacks according to an embodiment of the present disclosure.

Referring to FIGS. 36a, 36b, 36c, 37a, 37b, and 37c, the controller may manage the action stack shown in FIG. 37a. For example, the controller may assign the lowest Z-rank to window A running application A, the middle Z-rank to window B running application B, and the highest Z-rank to window C running application C. Accordingly, the controller may display windows in the order of window C 3631 and 3632, window B 3621 and 3622, and window A 3611 and 3612, as shown in FIG. 36a.

User 1 can input a Z-order change command. When a title bar 3631 is touched in window C as indicated by reference numeral 3641, a Z-order change command may be triggered by a leftward pinch-out gesture 3642. A pinch can be a gesture that spreads two touch points. In this case, the Z-order of windows C3631 and 3632 can be reset to the lowest Z-order. As a result, the controller assigns window A the middle Z-order, window B the highest Z-order, and window C the lowest Z-order. For example, the controller may assign window C the lowest Z-order while increasing the Z-orders of other windows by one. Accordingly, the controller may control the windows to be displayed in the order of windows B 3621 and 3622, windows A 3611 and 3612, and windows C 3631 and 3632. Pinch is a Z-order change command, and therefore, those skilled in the art easily understand that the Z-order change command can be triggered by various gestures including flick, drag, edge flick, touch and tilt, tilt, and shake.

User 1 can input a Z-order change command. When the application execution screen 3622 is touched in window B as indicated by reference numeral 3651 , a Z order change command may be triggered by a pinch gesture 3652 to the left. In this case, the Z-order of windows B 3621 and 3622 may be reset to the lowest Z-order. As a result, the controller assigns the highest Z-order to window A, the lowest Z-order to window B running application B, and the middle Z-order to window C running application C. For example, the controller may assign window B the lowest Z-order while increasing the Z-orders of other windows by one. Accordingly, the controller may control the windows to be displayed in the order of window A 3611 and 3612 , window C 3631 and 3632 , and window B 3621 and 3622 .

38a, 38b, and 38c illustrate screens of a display device describing a Z-order change command according to an embodiment of the present disclosure and FIGS. 39a, 39b, and 39c illustrate action stacks according to an embodiment of the present disclosure.

Referring to FIGS. 38a, 38b, 38c, 39a, 39b, and 39c, the controller may manage the action stack shown in FIG. 39a. For example, the controller may assign the lowest Z-rank to window A running application A, the middle Z-rank to window B running application B, and the highest Z-rank to window C running application C. Accordingly, the controller may display windows in the order of window C 3631 and 3632, window B 3621 and 3622, and window A 3611 and 3612, as shown in FIG. 38a.

User 1 can input a Z-order change command. When a title bar 3631 is touched in window C as indicated by reference numeral 3841, a Z-order change command may be triggered by a pinch-in gesture 3842 from the left. A pinch can be a gesture that narrows the distance between two touch points. In this case, the Z-orders of windows A 3631 and 3632 with the lowest Z-orders may be reset to the highest Z-orders, while lowering the Z-orders of other windows by one. Thus, the controller may assign the highest Z-order to window A, the lowest Z-order to window B running application B, and the middle Z-order to window C running application C, as shown in Figure 39b.

As shown in FIG. 38b, the controller may control the windows to be displayed in the order of windows A 3611 and 3612, windows C 3631 and 3632, and windows B 3621 and 3622. User 1 can input a Z-order change command. When a title bar 3631 is touched in window C as indicated by reference numeral 3851, a Z order change command may be triggered by a pinch gesture 3852 from the left. In this case, the Z-orders of windows B 3621 and 3622 with the lowest Z-orders may be reset to the highest Z-orders, while reducing the Z-orders of other windows by one. As a result, the controller may assign the middle Z-order to window A running application A, the highest Z-order to window B running application B, and the lowest Z-order to window C running application C, as shown in Figure 39c.

Accordingly, the controller may control the windows to be displayed in the order of windows B 3621 and 3622, windows A 3611 and 3612, and windows C 3631 and 3632.

As described above, when receiving a Z-order change command through a pinch gesture, the controller may assign the lowest Z-order to a window having the highest Z-order. Conversely, when receiving a Z-order change command through a pinch gesture, the controller may assign the highest Z-order to a window having the lowest Z-order. Since the user can change the Z order of the windows by simple manipulation, the desired window appears on top of the screen. Therefore, user convenience can be improved.

40a, 40b, 40c, 40d, 40e, 40f, 40g, 40h, 40i, 40j and 40k illustrate a method for displaying an application running window according to an embodiment of the present disclosure.

40a, 40b, 40c, 40d, 40e, 40f, 40g, 40h, 40i, 40j, and 40k, the display device 4200 can define a plurality of areas 4201, 4202, 4203, and 4204 on the touch screen. For convenience in describing FIG. 40a and subsequent figures, the plurality of regions 4201, 4202, 4203, and 4204 are referred to as a first region 4201, a second region 4202, a third region 4203, and a fourth region 4204 (region 1, region 2, region 3, and region 4), respectively. Both the first region 4201 and the third region 4203 form a fifth region (region 5, not shown) and both the second region 4202 and the fourth region 4204 form a sixth region (region 6, not shown). Both the first region 4201 and the second region 4202 form a seventh region (region 7, not shown) and both the third region 4203 and the fourth region 4204 form an eighth region (region 8, not shown). The first to fourth regions 4201, 4202, 4203 and 4204 form a region F. The first boundary 4211 may be set between the first area 4201 and the second area 4202, the second boundary 4212 may be set between the third area 4203 and the fourth area 4204, the third boundary 4213 may be set between the first area 4201 and the third area 4203, and the fourth boundary 4214 may be set between the second area 4202 and the fourth area 4204. The first boundary 4211 and the second boundary 4212 may form a single line, and the third boundary 4213 and the fourth boundary 4214 may form a single line. The first to fourth boundaries 4211 to 4214 are not necessarily displayed explicitly. Instead, the first to fourth boundaries 4211 to 4214 may be dotted lines. A controller (not shown) may configure the first to fourth areas 4201, 4202, 4203, and 4204 in such a manner that the first to fourth areas 4201, 4202, 4203, and 4204 do not overlap. For example, as shown in FIG. 40a, the controller may configure a first area 4201 at the upper left corner, a second area 4202 at the upper right corner, a third area 4203 at the lower left corner, and a fourth area 4204 at the lower right corner. The controller may divide the screen into left and right parts by a first boundary 4211 and a second boundary 4212 , and divide the screen into upper and lower parts by a third boundary 4213 and a fourth boundary 4214 .

The touch screen may display a center button 4220 at an intersection where the first to fourth boundaries 4211 to 4214 meet. The center button 4220 may be a function key to change the size of an area in which the application execution window is displayed or to set an operation mode controlling the execution window.

The controller may control the touch screen in such a manner that the application execution window is displayed in each of the plurality of areas. For example, the controller may control the touch screen so that a window for running an application is displayed, that is, the application running window is displayed in each of areas 4201, 4202, 4203, and 4204, as shown in FIGS.

Objects related to the application may be displayed on the running screen of the application. Objects can take many forms, such as text, graphics, icons, buttons, checkboxes, photos, videos, web pages, maps, and more. When a user touches an object, a function or event corresponding to the touched object may run in the application. Objects can be called views according to OS. For example, at least one of a capture button that captures the execution window to control display of the execution window, a minimize button that minimizes the size of the execution window, a maximize button that maximizes the size of the execution window, and an exit button that ends the execution window may be displayed.

Referring to FIG. 40b, the controller may control icons 4231, 4232, 4233, 4234, 4235, 4236, and 4237 representing executable applications to be displayed on the touch screen. The display device 4200 may execute application A. As shown in FIG. 40b , in response to the running of the application A, the controller may control the touch screen to display the running window 4230 of the application A in the first area 4201 . In addition, the controller may control icons 4231, 4232, 4233, 4234, 4235, 4236, and 4237 representing executable applications to be displayed at specific positions of the touch screen. When receiving a touch input to one of the icons 4231, 4232, 4233, 4234, 4235, 4236, and 4237, that is, when receiving an input of selecting an icon representing an application to be executed, the display device 4200 may display an execution window of the application corresponding to the selected icon in one of the first to fourth regions 4201, 4202, 4203, and 4204.

The controller may display an indicator 4221 indicating an active area on the displayed center button 4220 . The active area may be an area in which the last executed application or the last application selected by the user is displayed. An application operated by a user may be considered a user-selected application.

The indicator 4221 can be implemented in various ways to indicate the location of the active zone. For example, at least a part of the application execution window displayed in the active area may be displayed in an overlapping area between the application execution window of the active area and the center button 4220 . Alternatively, an arrow indicating the direction of the active area may be displayed on the center button 4220 .

The active area can be determined based on the action stack. The last running application or the last user selected application may be at the top of the action stack. The display device 4200 may determine an area in which an execution window of an application on top of an action stack is displayed as an active area. The active area may be referred to as a focal area. For example, in FIG. 40b , the indicator 4221 may indicate the first region 4201 .

Figures 41a, 41b, 41c, 41d, 41e and 41f illustrate action stacks according to various embodiments of the present disclosure.

Referring to FIG. 41a, an action stack managed by the display device 4200 is shown. The controller may generate and manage an action 4301 for the application A in an action stack in response to the execution of the application A.

Referring to FIG. 40c, user 1 may touch an icon 4232 representing application B. Referring to FIG. When the icon 4232 representing the application B is touched, the controller controls the execution window 4240 of the application B to be displayed in the second area 4202, as shown in FIG. 40d. The controller may determine an area in which the execution windows are displayed according to a certain order. For example, the controller may control to display new execution windows in the order of the second area 4202 , the third area 4203 and the fourth area 4204 . The above-described display order of execution windows is just an example, and thus the order in which new execution windows are displayed in areas 4201, 4202, 4203, and 4204 may be changed according to various embodiments of the present disclosure.

Since the execution window 4240 of the application B is displayed in the second area 4202, the indicator 4221 may indicate the second area 4202 in FIG. 40d.

Referring to Figure 41b, there is shown an action stack corresponding to Figure 4Od. The controller generates an action 4301 for application B in the action stack in response to application B running. The controller may place the action 4302 of the last executed application B on top of the action 4301 of the application A.

Referring to FIG. 40e, a user 1 may touch an icon 4233 corresponding to application C. Referring to FIG. When the icon 4233 representing the application C is touched, the controller controls to display the execution window 4250 of the application C in the fourth area 4204, as shown in FIG. 40f. Along with the display of the execution window 4250 of the application C in the fourth area 4204 , the indicator 4221 may indicate the fourth area 4204 .

Figure 41c shows the action stack corresponding to Figure 40f. The controller generates an action 4303 for application C in the action stack in response to application C running. The controller places the action 4303 of the last running application C at the top of the action stack.

Referring to FIG. 40g, user 1 may touch an icon 4234 representing application D. Referring to FIG. When the icon 4234 representing the application D is touched, the controller controls to display the execution window 4260 of the application D in the third area 4203, as shown in FIG. 40h. Since the execution window 4260 of the application D is displayed in the third area 4203 , the indicator 4221 on the center button 4220 may indicate the third area 4203 .

Figure 41d shows the action stack corresponding to Figure 40h. The controller generates an action 4304 for application D in the action stack in response to application D running. The controller places the action 4304 of the last running application D on top of the action stack.

Referring to FIG. 40i , user 1 can operate application B. Referring to FIG. Figure 41e shows the action stack corresponding to Figure 40i. The controller moves application B's action 4302 to the top of the action stack in response to user input to application B's run window 4240 .

When receiving a user input for the execution window 4240 of the application B, the controller may determine the second area 4202 as the active area, as shown in FIG. 40i. Accordingly, the indicator 4221 on the center button 4220 may indicate the second area 4202 .

Referring to FIG. 40j, user 1 may touch an icon 4235 representing application E. Referring to FIG. When the icon 4235 representing the application E is touched, the controller controls the execution window 4270 of the application E to be displayed in the fourth area 4204 on the touch screen, as shown in FIG. 40k. In case there is no empty area, the controller can refer to the action stack shown in Fig. 41e. The controller may select the lowest application action from the action stack, and may display the application E in the fourth area 4204 instead of the execution window 4270 corresponding to the application C.

Figure 41f shows the action stack corresponding to Figure 40k. The controller generates an action 4305 for the application E in the action stack in response to the execution of the application E. The controller places the action 4305 of the last running application E on top of the action stack.

FIG. 42 is a flowchart illustrating a method for executing an application in a display device according to an embodiment of the present invention.

Referring to FIG. 42, in operation S4410, the display device may execute a plurality of applications. For example, a display device may execute an application in response to receipt of user input on an icon representing the application.

In operation S4420, the display device may determine a layout for arranging execution windows of applications. A layout defines the area in which running windows can be arranged. For example, various layouts are available, including 2 top/bottom area split layouts, 2 left/right area split layouts, 3 area split layouts, 4 area split layouts, and the like.

In operation S4430, the display device may determine a window position in the layout. In case of defining 2 left/right area split layouts of the fifth area and the sixth area, the display device may allocate the execution windows of the web browser and the phonebook application to the fifth area and allocate the execution window of the video play application to the sixth area.

In operation S4440, the display device may display a plurality of execution windows according to the priority levels of the applications. For example, if execution windows of a web browser and a phonebook application are assigned to the fifth area, an execution window of an application having a higher priority between the web browser and the phonebook application may be displayed in the fifth area.

43a and 43b illustrate a method for controlling a display area of an application execution window using a center button according to an embodiment of the present disclosure.

43a, a display device 4500 may define a first area 4501, a second area 4502, a third area 4503, a fourth area 4504, a first border 4505, a second border 4507, a third border 4506, and a fourth border 4508, which will not be construed as limiting the present disclosure. Accordingly, the display device 4500 can define regions and boundaries in various ways.

The display device 4500 may display a center button 4220 on at least one border. For example, if a first border 4505, a second border 4507, a third border 4506, and a fourth border 4508 are defined, the display device 4500 may display the center button 4220 at the intersection where the first border 4505, the second border 4507, the third border 4506, and the fourth border 4508 meet, as shown in FIG. 43a. In another example, if the display device 4500 defines fifth and sixth regions (not shown) and the first border 4505 and the second border 4507, the display device 4500 may display the center button 4220 on the first border 4505 or the second border 4507.

Referring to FIG. 43b, if the user 10 touches the center button 4220 and drags the touched center button 4220, the display device 4500 may move the center button 4220 to the dragged position. As the center button 4220 moves, the display device 4500 may change the size and position of an area in which an application execution window and a border are displayed.

Figure 44a, Figure 44b, Figure 44c, Figure 44d, Figure 44e, Figure 44f, Figure 44g, Figure 44h, Figure 44i, Figure 44j, Figure 44k, Figure 44l, Figure 44m, Figure 44n, Figure 44o, Figure 44p, Figure 44q, Figure 44r, Figure 44s, Figure 44t, Figure 44u, Figure 44v and Figure 44w illustrate the Method for running multiple applications.

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

Figures 45a, 45b, 45c, 45d, 45e, 45f, 45g, 45h, 45i and 45j illustrate action stacks according to embodiments of the disclosure.

Referring to Figure 45a, there is shown an action stack corresponding to Figure 44a. Since the execution window of the application A is displayed in the area F occupying the entire screen, a controller (not shown) generates an action for the application A as shown in FIG. 45a.

The user 10 can operate the display device 4600 to additionally execute the application B. For example, as shown in FIG. 45b, the user 10 may touch the icon 4612 representing the second application B, and drag the touched icon 4612 toward the sixth area 4623 as shown in FIG. 45c.

If the drag input ends in the sixth area 4623 , the display device 4600 executes the application B corresponding to the selected icon 4612 . Also, the display device 4600 moves the application A displayed in the area F to the fifth area 4619 when the application B is displayed in the sixth area 4623 .

Finally, the running window 4620 of application A is displayed in the fifth area 4619 , and the running window 4630 of application B is displayed in the sixth area 4623 .

The display device 4600 may display a center button 4622 on a boundary between the fifth area 4619 and the sixth area 4623 . The display device 4600 may also display an indicator 4621 indicating an execution window 4630 of the last executed application B on the center button 4622 . The indicator 4621 may display an area in which the running window of the application placed on top of the action stack is displayed.

Figure 45b shows the action stack corresponding to Figure 44d. The action of the application A displayed in the area F is changed so that the application A can be displayed in the fifth area 4619 . Since the application B is executed, an action for the application B is generated and the application B is arranged in the sixth area 4623 . Application B's actions are placed on top of the action stack.

Referring to FIG. 44e, the user 10 may move the displayed center button 4622. Referring to FIG. As shown in FIGS. 43a and 43b, along with the movement of the center button 4622, the size of the area in which the execution window of the application is displayed may be changed.

Subsequently, as shown in FIG. 44f , the user 10 may touch the icon 4613 representing the application C, and drag the touched icon 4613 toward the fourth area 4627 as shown in FIG. 44g . The size of the fourth area 4627 may be determined according to the position of the center button 4622 . When the dragging of the icon 4613 representing the application C ends in the fourth region 4627 , the display device 4600 may execute the application C. As shown in FIG. 44h , the display device 4600 may display the running window 4640 of the application C in the fourth area 4627 . The display device 4600 may display an indicator 4621 indicating an active area where the execution window 4640 of the application C is displayed on the center button 4622 .

Figure 45c shows the action stack corresponding to Figure 44h. A controller (not shown) generates actions for application C in response to application C running. Application C is arranged in the fourth area 4627 . Since the area displaying the execution window 4630 of the application B is split, the application B is assigned to the second area in FIG. 44e.

Referring to FIG. 44i , the user 10 may control the size of an area where execution windows 4620 to 4640 of applications are displayed by applying an input of a mobile center button 4622 .

As shown in FIG. 44j , the user 10 may touch the icon 4614 representing application D, and drag the touched icon 4614 toward the third area 4631 as shown in FIG. 44k .

If the dragging of the touched icon 4614 representing the application D ends in the third area 4631 , the display device 4600 may execute the application D. Referring to FIG. As shown in FIG. 441 , the display device 4600 may display the execution window 4650 of the application D in the third area 4631 . The display device 4600 may display an indicator 4621 indicating an active area where the execution window 4650 of the application D is displayed on the button 4622 .

Figure 45d shows the action stack corresponding to Figure 44l. The controller generates actions for application D in response to application D running. Application D is allocated to the third area 4631 . Since the area displaying the execution window 4620 of the application A is split, the application A is allocated to the first area in FIG. 44i.

The user 10 may touch the icon 4615 representing application E and drag the touched icon 4615 to the border area 4659, as shown in FIG. 44m. Display device 4600 defines border area 4659 to include border 4685 .

If the dragging of the touched icon 4615 representing the application E ends in the border area 4659 , the display device 4600 may execute the application E. Referring to FIG. The display device 4600 may arrange the execution window 4660 of the application E in a seventh area including the first area and the second area adjacent to the border 4685 included in the border area 4659, as shown in FIG. 44n. The display device 4600 may display an indicator 4621 indicating an active area where the execution window 4660 of the application E is displayed on the button 4622 .

Figure 45e shows the action stack corresponding to Figure 44n. The controller generates actions for the application E in response to the execution of the application E. The application E is assigned to the seventh area, and the applications A and B displayed in the first area and the second area included in the seventh area are placed in the seventh area.

The user 10 may touch the icon 4616 representing application F and drag the touched icon 4616 to this second area 4661, as shown in Fig. 44o.

If the dragging of the touched icon 4616 representing the application F ends in the second area 4661 , the display device 4600 may execute the application F. Referring to FIG. As shown in FIG. 44p , the display device 4600 may display an execution window 4670 of the application F in the second area 4661 .

Referring to FIG. 45f, the controller may generate an action for the application F arranged in the second area. As the seventh area is split, the application A, application B, and application E displayed in the seventh area may be arranged in the first area.

The touch screen may receive an input of selecting the execution window 4660 of the application E from the user 10, as shown in FIG. 44p.

Referring to FIG. 45g, in response to the selection of the execution window 4660 of the application E, the controller may move the action of the application E to the top of the action stack. The display device 4600 may display an indicator 4621 indicating the location of the execution window 4660 on the button 4622 .

Referring to FIG. 44q, the display device 4600 may receive an input of selecting an execution window 4660 of the application E from the user 10. Referring to FIG. For example, user 10 may touch button 4622. In response to receiving an input of a selection button 4622, the display device 4600 may display a list of applications 4611, 4612, and 4615 displayed in the first area active at the moment. For example, the display device 4600 may display icons representing application A, application B, and application E assigned to the first area in the first area with reference to the action stack shown in FIG. 45g.

In response to receiving an input of the selection button 4622, the display device 4600 may further display display icons 4691, 4692, and 4693 representing operations related to the execution window of the application displayed in the first area.

When receiving an input of an icon 4611 representing an application among icons displayed in the first area, the display device 4600 may display an execution window 4620 of the application A in the first area, as shown in FIG. 44s.

Figure 45h shows the action stack corresponding to Figure 44s. In response to receiving an input of selecting an icon 4611 representing application A, the controller may move the action of application A to the top of the action stack.

Referring to FIG. 44t, when an input of selecting a center button 4622 is received, a list of applications 4611, 4612, and 4615 assigned to a first area that is an active area may be displayed. Also, a drag input of dragging the icon 4612 representing the application B to the area where the execution window 4640 of the application C is displayed may be received from the user 10 . As the drag input is completed, the display device 4600 may display the execution window 4630 of the application B in the fourth area, as shown in FIG. 44u. The display device 4600 may display an indicator 4621 indicating the location of the execution window 4630 of the application B on the button 4622 .

Figure 45i shows the action stack corresponding to Figure 44u. Since the execution window 4630 of the application B is displayed in the fourth area, the controller updates the area to which the application B is allocated to the fourth area, and moves the action of the application B to the top of the action stack.

Referring to FIG. 44v, when an input of selecting the center button 4622 is received, icons 4691, 4692, and 4693 representing operations related to the running window of the application displayed in the first area as the active area may be further displayed. As far as the execution window of the application is concerned, operations related to the execution window of the application can perform various additional functions. For example, icons representing operations related to the application execution window may include at least one of an exit button 4691 to end the execution window, a maximize button 4692 to display the execution window in full screen, and a capture button 4693 to capture the execution window, which will not be construed as limiting the present disclosure. When receiving an input of selecting an exit button 4691 from the user 10, the controller may end the execution window of the application A, as shown in (b) of FIG. 44v.

Figure 45j shows the action stack corresponding to Figure 44v. When the running window of application A is terminated, the action of application A may be removed from the action stack.

Referring to FIG. 44w, when an input of selecting a maximize button 46921 is received from the user 10, the display device 4600 may display the execution window 4660 of the application A displayed in the active area in full screen on the touch screen.

When an input of selecting a capture button 4693 is received from the user 10 , the display device 4600 may capture the active execution window 4660 .

FIG. 46 is a diagram illustrating a method for providing a user interface on which an application is executed in a display device according to an embodiment of the present invention.

Referring to FIG. 46 , in operation S4810, the display device may display an execution window of an application in a plurality of regions defined on the touch screen. In operation S4820, the display device may also display buttons on at least one boundary between the plurality of regions.

The display device may display indicators on the buttons to indicate the active area. The active area may refer to the last area selected from a plurality of areas. Also, the active area means an area in which the running window is in a state controllable by user input.

In operation S4830, the display device may receive an input of selecting a button. When an input of selecting a button is received, the display device may display a list of applications in a specific area in operation S4840. Herein, a specific area may be an active area.

The application list may list at least one icon representing at least one application. When an input of selecting at least one of the applications included in the application list is received, the display device may display an execution window of the selected application in a specific area. When a drag input of dragging an icon included in the application list is received, the display device may display an execution window of an application corresponding to the dragged icon in the dragged area.

The display device may further display icons of operations related to the execution windows of the applications displayed in the specific area. The icons representing operations related to the execution window of the application may include at least one of a capture button to capture the execution window to control display of the execution window, a minimize button to minimize the size of the execution window, a maximize button to maximize the size of the execution window, and an exit button to end the execution window.

FIG. 47 is a flowchart illustrating a method for executing an application in a display device according to an embodiment of the present invention.

Referring to FIG. 47 , in operation S4910, the display device may display an execution window of an application in a plurality of regions defined on the touch screen. In operation S4920, the display device may also display buttons on at least one boundary between the plurality of regions.

In operation S4930, the display device may display a list of at least one application execution icon in a partial area of the touch screen.

In operation S4940, the display device may determine an area in which the new application is executed based on the location to which the application execution icon is dragged and the location of the button. The execution area of the new application is an area in which the execution window of the additionally executed application will be displayed.

If the dragged position falls within a boundary area including at least one boundary, the execution area of the new application may be determined to include an area adjacent to the at least one boundary.

Subsequently, in operation S4950, the display device may display the execution window of the application in the determined area.

FIG. 48 is a block diagram of a display device according to an embodiment of the present disclosure.

Referring to FIG. 48 , the display device 5000 may include: a touchscreen 5010 configured to display an execution window of an application in a plurality of regions, display a button on at least one border between the plurality of regions, and receive an input of a selection button; and a controller 5020 configured to control the touchscreen 5010 to display in a specific region a list of at least one application running in a specific region selected from among the plurality of regions based on the received input.

Specific areas include active areas that can be controlled by user input. The active area may be the last area selected from among the plurality of areas.

In addition, the controller 5020 may control the touch screen 5010 to display an indicator indicating an active area on the button.

49a, 49b, 49c, and 49d are diagrams illustrating a method for displaying a button according to an embodiment of the present disclosure.

Referring to FIG. 49A , the display device 5100 may display a button 5122 on a boundary separating an area in which execution windows of a plurality of applications are displayed. Also, the display device 5100 may define an arrangement line 5120 according to the layout of application execution windows. The arrangement line 5120 may include a dotted line and an outline of the touch screen.

The display device 5100 may further define an arrangement area 5110 . An alignment line 5120 may be included in the alignment area 5110 .

As shown in FIG. 49a, an arrangement line 5120 and an arrangement area 5110 may be determined according to the number and positions of execution windows of applications displayed on the touch screen. For example, if the layout is a 2 top/bottom area split layout, a 2 left/right area split layout, a 3 area split layout, or a 4 area split layout, the alignment line 5120 and the alignment area 5110 may be defined according to the layout.

Referring to FIG. 49b, when an input of moving the button 5122 to the arrangement area 5110 on the touch screen is received, the display device 5100 may move the button 5122 to the part of the arrangement line 5120 closest to the last position of the button 5122.

The display device 5100 may determine an area in which the execution window of the application is displayed based on the position of the button 5122 on the arrangement line 5120 . Accordingly, the display device 5100 may arrange display areas of application execution windows.

Referring to FIG. 49c , the display device 5100 may define an arrangement point 5130 at a specific position of the arrangement line 5120 . When receiving an input to the button 5122 (for example, two consecutive touches on the button 5122 ), the display device 5100 may move the button 5122 to an arrangement point 5130 .

Referring to Figure 49d, if the button 5122 is moved in the manner shown in Figures 49a, 49b and 49c, the movement may act according to the function shown in Figure 49d. For example, when the center button 5122 moves to the alignment line 5120 or the alignment point 5130 , the button 5122 may pass through the alignment line 5120 or the alignment point 5130 and return to the alignment line 5120 or the alignment point 5130 .

Embodiments of the present disclosure provide a display device that can easily switch from one window to another low-priority window after running a plurality of windows on a single display, and a method for controlling the display device. Therefore, users can use multiple applications in multiple windows at the same time. Furthermore, if a plurality of windows are displayed overlapping, the currently displayed window is easily switched to another low priority window. Therefore, in an environment where a plurality of windows are displayed on the screen, the user can execute a desired-sized window at a desired position with improved convenience.

It will be appreciated that various embodiments of the present disclosure may be implemented in hardware, software or a combination thereof. Software may be stored in volatile or non-volatile storage devices such as ROM whether the data is erasable or rewritable, in memory such as RAM, in memory chips, devices, integrated circuits, storage media such as compact discs (CDs), digital video discs (DVDs), from which data can be recorded optically or magnetically and read by a machine (e.g., a computer), on magnetic disks, magnetic tapes, and the like. Furthermore, the embodiments of the present disclosure can be implemented in a computer or a portable terminal having a controller and a memory such as a memory adapted to store a program or programs including commands for realizing the embodiments of the present disclosure. Therefore, the present disclosure includes a program having codes for realizing means or methods defined by claims and a storage medium storing the program readable by a machine. Programs may be transferred electronically through media such as communication signals transferred via wired or wireless connections, where media and their equivalents are included in this disclosure.

The device can receive the program from the program providing device through a wired or wireless connection and store the program. The program providing device may include a program including commands for implementing an embodiment of the present disclosure, a memory for storing information used for an embodiment of the present disclosure, a communication module for communicating with a mobile device through a wired or wireless connection, and a controller for transmitting the program to the mobile device automatically or upon request.

While the present disclosure has been shown and described in detail with reference to certain disclosed exemplary embodiments, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the claims and their equivalents.

Claims (12)

1. An electronic device, comprising:

a touch screen display; and

at least one processor configured to:

controlling the touch screen display in a split mode;

running the first application, controlling the touch screen display to display a running screen of the first application,

after the first application is run, detecting by the touch screen display a first user input for running a second application,

in response to detecting the first user input, controlling the touch screen display to display a running screen of the second application in a display area of the first application on the touch screen display,

while the running screen of the second application is displayed on the touch screen display, detecting, by the touch screen display, a second user input, wherein the second user input starts from a point on at least one edge of the touch screen display corresponding to a display area displaying the first application, and

in response to detecting the second user input, controlling the touch screen display to display a running screen of the first application, wherein the running screen of the second application is replaced by the running screen of the first application according to the second user input.

2. The electronic device of claim 1, wherein the second user input comprises a drag gesture or a flick gesture.

3. The electronic device of claim 1, wherein the second user input comprises a right hand gesture or a left hand gesture.

4. The electronic device of claim 1, wherein the second user input comprises a command to change a z-order, the z-order being a display order of the window.

5. The electronic device according to claim 1,

wherein the first application is running at a first time and the second application is running at a second time, an

Wherein the first time is earlier than the second time.

6. The electronic device according to claim 1,

wherein the at least one processor is further configured to:

detecting, by the touch screen display, a third user input on a running screen of the second application, and

in response to detecting the third user input, a function of the second application is executed.

7. A method for controlling an electronic device, comprising:

controlling a touch screen display of the electronic device in a split mode;

running the first application and displaying a running screen of the first application on the touch screen display;

detecting, by the touch screen display, a first user input for running a second application after the first application is run;

In response to detecting the first user input, displaying a running screen of the second application in a display area of the first application on the touch screen display;

detecting, by the touch screen display, a second user input while the running screen of the second application is displayed on the touch screen display, wherein the second user input begins at a point on at least one edge of the touch screen display corresponding to a display area displaying the first application; and

in response to detecting the second user input, a running screen of the first application is displayed, wherein the running screen of the second application is replaced by the running screen of the first application according to the second user input.

8. The method of claim 7, wherein the second user input comprises a drag gesture or a flick gesture.

9. The method of claim 7, wherein the second user input comprises a right hand gesture or a left hand gesture.

10. The method of claim 7, wherein the second user input includes a command to change a z-order, the z-order being a display order of the window.

11. The method according to claim 7,

wherein the first application is running at a first time and the second application is running at a second time, and

Wherein the first time is earlier than the second time.

12. The method of claim 7, further comprising:

detecting, by the touch screen display, a third user input on a running screen of the second application; and

in response to detecting the third user input, a function of the second application is executed.