The present invention relates to a display control apparatus and a display control method for implementing multi-display.
Multi-display systems for displaying a plurality of windows (a multi-window) of a plurality of different applications (a multi-application) on a plurality of displays have conventionally been known. For example, Patent Document 1 discloses a system that displays a window for displaying, on a built-in monitor, details displayed on an external monitor upon detection of disconnection of the external monitor during use of an extended desktop function, which enables prevention of a non-operable state.
However, operating systems (OSs) for smartphones typically do not support multi-display. Such OSs have a problem with not being able to implement multi-display when used.
In view of the problem, the present invention has an object of implementing multi-display using an OS for smartphones that does not support multi-display.
The display control apparatus according to the present invention is a display control apparatus using an operating system for smartphones, and includes: a window creator that creates, for each of displays, a window that is a display area; a window allocator that allocates, to a plurality of applications, the windows created by the window creator; and a display controller that obtains respective display information items from the plurality of applications, and causes the displays to display the display information items according to the allocation of the windows. The plurality of applications include first applications defined by a specification of the operating system as applications for controlling display, and second applications defined by the specification of the operating system as applications for not controlling display. The window allocator can allocate only one window to at least the first application that does not mainly operate among the first applications.
The display control apparatus according to the present invention is a display control apparatus using an operating system for smartphones, and includes: a window creator that creates, for each of displays, a window that is a display area; a window allocator that allocates, to a plurality of applications, the windows created by the window creator; and a display controller that obtains respective display information items from the plurality of applications, and causes the displays to display the display information items according to the allocation of the windows. The plurality of applications include first applications defined by a specification of the operating system as applications for controlling display, and second applications defined by the specification of the operating system as applications for not controlling display. The window allocator can allocate only one window to at least the first application that does not mainly operate among the first applications. Thus, multi-display can be implemented using the OS for smartphones that does not support the multi-display.
The objects, features, aspects and advantages of the present invention will become more apparent from the following detailed description and the accompanying drawings.
[A-1. OS for PCs]
The applications A1, A2, and A3 include respective display information items for the user. These applications provide the user with information. Alternatively, the applications are operated upon receipt of an instruction from the user. Simultaneous operations of the applications A1, A2, and A3 realize a multi-application.
However, mere use of a multi-application does not allow a multi-window, that is, a plurality of displays to display the display information items of the respective applications.
The window manager WM1 manages and controls windows that are areas for writing the display information items of the applications A1, A2, and A3 to cause the plurality of displays D1 and D2 to display the display information items of the respective applications A1, A2, and A3. The window manager WM1 obtains information on, for example, the screen size from each of the displays D1 and D2, and generates a window W1 for the display D1 and a window W2 for the display D2. Then, the windows W1 and W2 are provided to the applications A1, A2, and A3.
The applications A1, A2, and A3 present the respective display information items to the windows W1 and W2 obtained from the window manager WM1.
Suppose a case where the application A1 presents a display information item to the window W1, the application A3 presents a display information item to the window W2, and the application A2 presents a display information item to the windows W1 and W2. Here, the display information item of the application A2 is located higher with respect to a Z axis of the screen, that is, located more frontward than the display information items of the applications A1 and A3.
The display information item V2 is disposed not only in the window W1 but also in the window W2. The window manager WM1 defines which portion of the display information item V2 is clipped by the window W2.
The display information item V1 illustrated in
The display information item V3 illustrated in
Since the window manager WM1 of the OS for PCs can allocate a window of a different display to a different application, multi-display with a multi-application can be implemented.
[A-2. Android (Registered Trademark)]
In the display control apparatus of
The presentation P1 is an extended window manager under Android (registered trademark), and allocates windows W2 and W3 of the displays D2 and D3 to the activity application AA1 that is the main activity application among the activity applications AA1, AA2, and AA3. Specifically, the window manager WM2 sends the windows W2 and W3 to the presentation P1, and the presentation P1 sends the windows W2 and W3 to the activity application AA1. Then, the presentation P1 obtains the display information items for the windows W2 and W3 from the activity application AA1, and sends the display information items to the window manager WM2. Thus, the display information items of the activity application AA1 are displayed on the displays D2 and D3.
The window manager WM2 also defines which portion of the display information item VA1 is clipped by the window W2.
Consequently, the display information item of the activity application AA1 is displayed on the displays D1, D2, and D3 to implement multi-display. However, the window manager WM2 has a constraint of being unable to allocate only one window to one activity application, unlike the window manager WM1 of the OS for PCs. As described above, although the presentation P1 can allocate the windows W2 and W3 to the activity application AA1, the presentation P1 cannot allocate the windows W2 and W3 to the activity applications AA2 and AA3 that are not the main activity applications. Thus, the display information items of the activity applications AA2 and AA3 cannot be displayed on the displays D2 and D3. Switching the main activity application from the activity application AA1 to the activity applications AA2 and AA3 creates inconveniences of failing to cause the displays D2 and D3 to display the display information item of the activity application AA1. Thus, the display information items of a plurality of activity applications cannot be displayed on a plurality of displays.
[B-1. Configuration]
The display control apparatus according to Embodiment 1 includes the window manager WM2, displays D1, D2, and D3, the presentation P1, an activity application AA1, and a service application SA1.
The window manager WM2 and the presentation P1 are functions prepared for Android. Applications under Android are classified into activity applications (first applications) that are applications for controlling display, and service applications (second applications) that are applications for not controlling display. The activity applications are launched (a create state), and start an operation (a start state). The activity applications are in a resume state when coming to the foreground of a window. Once coming out of the foreground, the activity applications pause (a pause state). When there is no necessity of operations as applications, the activity applications come to a stop state. When the activity applications are resumed from the stop state (a restart state), they switch from the start state to the resume state. When the activity applications completely finish the operations, they switch from the stop state to a destroy state. In other words, the activity applications change its application state according to a state of display. In contrast, the service applications (not originally generating any display information item) for not controlling display are the same as the activity applications in launching (the create state) and starting an operation (the start state). However, the service applications do not change its application state according to a state of display. During operations, the service applications continue to operate and never come to the pause state or the stop state. Thus, the service applications never come to the restart state or the resume state, either.
The window manager WM2 creates, for each of the displays D1, D2, and D3, a window that is a display area, and allocates the windows to the activity application AA1 and the service application SA1. Then, the window manager WM2 obtains the display information items from the activity application AA1 and the service application SA1, and causes the displays D1, D2, and D3 corresponding to the respective windows to display the display information items according to the allocation of the windows. In other words, the window manager WM2 functions as: a window creator that creates a window for each of the displays D1, D2, and D3; a window allocator that allocates the windows to a plurality of applications; and a display controller that causes the displays to display the display information items according to the allocation of the windows.
The characteristic herein is that the window manager WM2 allocates windows not only to the activity application AA1 but also to the service application SA1. Specifically, the window manager WM2 allocates the window W1 to the activity application AA1, and the window W3 to the service application SA1. The window manager WM2 also allocates the window W2 to the activity application AA1 through the presentation P1. Since the service application SA1 obtains the window W3 directly from the window manager WM2 without through the presentation P1, the service application SA1 can obtain the window W3 without being constrained by the presentation P1. There is no need to change the configuration of the window manager WM2 and the presentation P1 in the display control apparatus of
The window manager WM2 (the window creator, the window allocator, and the display controller), the presentation P1, the activity application AA1, and the service application SA1 that are included in the configuration of the display control apparatus illustrated in
[B-2. Operations]
As described in
The window manager WM2 provides the display list to the service application SA1 in response to this obtainment request (Step S2). Here, the display list includes lists of the displays D1, D2, and D3. Upon receipt of the display list, the service application SA1 requests the window manager WM2 to obtain information on the display D3 (Step S3).
The window manager WM2 provides the information on the display D3 to the service application SA1 in response to this obtainment request (Step S4). Upon receipt of the information on the display D3, the service application SA1 requests the window manager WM2 to obtain the window W3 (Step S5).
The window manager WM2 provides the window W3 to the service application SA1 in response to this obtainment request (Step S6). The window W3 is allocated to the service application SA1 accordingly. Upon receipt of the window W3, the service application SA1 requests the window manager WM2 to specify a display layer (Step S7).
The window manager WM2 responds to the service application SA1 with acknowledgment, in response to this specification request (Step S8). The display layer of the service application SA1 is determined accordingly. Then, the service application SA1 calls the view function, and arranges display components (views) to generate a display information item. This display information item is sent to the window manager WM2, and the window manager WM2 causes the display D3 to display the display information item.
The window manager WM2 defines which portion of the display information VA1 is clipped by the window W2.
In other words, the display control method using an operating system for smartphones according to Embodiment 1 includes: creating, for each of displays, a window that is a display area; allocating the windows to a plurality of applications including first applications defined by a specification of the operating system as applications for controlling display, and second applications defined by the specification of the operating system as applications for not controlling display; causing the plurality of applications to prepare respective display information items; and obtaining the display information items from the plurality of applications, and causing the displays to display the display information items according to the allocating, the displays corresponding to the respective windows. The first applications include an application capable of allocating only one window. Thus, multi-display with a multi-application using the first applications and the second applications can be implemented.
[B-3. Modifications]
Although Android (registered trademark) is exemplified as an operating system for smartphones in the description above, the other operating systems for smartphones are also applicable to the present invention.
It is described that the window manager WM2 sends, for example, the window W1 to the activity application AA1 and that in response to this, the activity application prepares a display information item. However, the window manager WM2 has only to allocate the window W1 to the activity application AA1 and may not send the window W1 itself. Here, the window manager WM2 disposes the display information item obtained from the activity application AA1 in the window W1.
The embodiments of the present invention can be appropriately modified or omitted within the scope of the present invention.
Although this invention has been described in detail, the description is in all aspects illustrative and does not restrict the invention. Therefore, numerous modifications that have yet been exemplified will be devised without departing from the scope of this invention.
11 user interface, 12 memory, 13 CPU, 14 bus, 21, 22, 23 output terminal, A1, A2, A3 application, AA1, AA2, AA3 activity application, D1, D2, D3 display, P1 presentation, WM1, WM2 window manager.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/JP2015/074568 | 8/31/2015 | WO | 00 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2017/037814 | 3/9/2017 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
9134756 | de Paz | Sep 2015 | B2 |
20100293504 | Hachiya | Nov 2010 | A1 |
20130024812 | Reeves | Jan 2013 | A1 |
20130305184 | Kim | Nov 2013 | A1 |
20140310643 | Karmanenko et al. | Oct 2014 | A1 |
Number | Date | Country |
---|---|---|
2006-350755 | Dec 2006 | JP |
2010-267142 | Nov 2010 | JP |
4676011 | Apr 2011 | JP |
2014-503891 | Feb 2014 | JP |
2014-149699 | Aug 2014 | JP |
WO 2012078079 | Jun 2012 | WO |
Entry |
---|
Office Action dated May 8, 2018 in counterpart Japanese Application No. 2017-537080 with an English Translation. |
Juggly, juggly.cn, Ixonos, Android Tanmatsu o Multi Window-ka, Multi Monitor-ka suru Software no Demo o Hiro, [online], Sep. 25, 2013, [retrieval date Nov. 9, 2015], Internet: <URL: http://juggly.cn/archives/95639.html>, 2 pages. |
Kseto, TechBooster, Android Gamen-jo ni Apuri no Joho o Joji Hyoji suru Hobo, [online], Feb. 5, 2012, [retrieval date Nov. 9, 2015], Internet: <URL: http://techbooster.org/android/ui/13182/>, 7 pages. |
Number | Date | Country | |
---|---|---|---|
20180129358 A1 | May 2018 | US |