Patent Description:
The present disclosure relates to a display control device, a display control method, and a program.

Recently, client devices equipped with a touchscreen display are rapidly proliferating. In such devices, content displayed on the display is scrolled, as described in PTL <NUM>, for example. With scrolling, content that does not fully fit on the display may be partially displayed on the display, and the entire content may be expressed by scrolling the portion to display, for example. PTL <NUM> discloses a computer-implemented user notification method including displaying, in a status area near a perimeter of a graphical interface, a notification of a recent alert event for a mobile device, receiving a user selection in the status area, and in response to the receipt of the user selection, displaying, in a central zone of the graphical interface, detail regarding a plurality of recent messaging events for the mobile device. PTL <NUM> relates to devices with touch-screen displays, and more particularly to scrolling lists and to translating, rotating, and scaling electronic documents on devices with touch-screen displays. PTL <NUM> provides a method for scaling the display interface of the touch screen of an electronic device by operating the touch screen with one hand. PTL <NUM> discloses systems and methods for displaying notifications received from multiple applications.

Scrolling on a touchscreen display as above may realize a function of moving a portion of content to display on the display, and in addition, a function of moving an operable item displayed on the display. For example, an interface element such as a link or button included in content on a web page may be moved by scrolling to a position easily reached by a user's finger. The utility of such an operation is increasing as the displays in recent mobile client devices become larger, for example.

However, since the original purpose of scrolling is to display content on a display, a function of moving an operable item to a position easily reached by a finger as above may not necessarily be realized. For example, it is difficult to move an interface element to a user-desired position in the case in which the interface element that the user wants to operate is positioned at the edge of content, since scrolling ends at the edge of the content.

Accordingly, the present disclosure proposes a new and improved display control device, display control method, and program enabling further improvement in the usability of a touchscreen display using scrolling movement.

According to the present invention, there is provided an information processing device as defined in the appended claim <NUM>.

According to an embodiment of the present disclosure as described above, the usability of a touchscreen display using scrolling movement may be further improved.

Hereinafter, preferred embodiments of the present disclosure will be described in detail and with reference to the attached drawings.

Hereinafter, the description will proceed in the following order.

<FIG> is a block diagram illustrating a schematic functional configuration of a client device according to the first embodiment of the present disclosure. Referring to <FIG>, a client device <NUM> includes a touchscreen display <NUM>, a controller <NUM>, a storage unit <NUM>, and a communication unit <NUM>. This functional configuration may be realized by the hardware configuration of an information processing device discussed later, for example.

For the sake of brevity, the present advancements are described herein using a client device <NUM> that is operated using a touchscreen display, such as a smartphone, tablet, portable game console, or media player, for example. However, as one of ordinary skill in the art would recognize, the present advancements may be on other devices using other input methods. For example, the present advancements may be used in conjunction with a user interface that projects a graphical user interface onto a surface and which receives user input by recognizing user movement in a captured image of the surface. The present advancements can also be used in conjunction with a user interface that receives user input based on a user's proximity thereto rather than based on a user touch of the interface. Thus, the following descriptions are merely exemplary and not limiting upon the scope of the advancements presented herein.

The touchscreen display <NUM> includes a display unit <NUM> and an operating unit <NUM>. The display unit <NUM> is a display device such as a liquid crystal display (LCD) or an organic electroluminescent (EL) display, for example, that displays and presents various images to a user under control by the controller <NUM>. The operating unit <NUM> is a touch sensor of various types, for example, that detects and provides user-given contact with the screen of the display unit <NUM> to the controller <NUM> as operating input.

Herein, the client device <NUM> is capable of providing a user with, for example, web pages and content such as images, video, and music by displaying images with the display unit <NUM> and/or outputting audio with a speaker (not illustrated). The display unit <NUM> may also display a content list in which are arranged character strings, thumbnail images, icons, or the like that indicate such content. Furthermore, the display unit <NUM> may also display an interface element in an image. An interface element is a graphical user interface (GUI) component that is displayed together with content and is capable of receiving an operation on the content such as play, stop, or move, or a component that is displayed together with a content list and is capable of receiving an operation on respective content such as play, delete, or move, for example.

Also, in some cases content or a content list is displayed while being scrolled on the display unit <NUM>. More specifically, in the case in which the entirety of a web page does not fit within the size of the display unit <NUM>, a portion of the web page is displayed on the display unit <NUM>, and the displayed portion is moved as a result of a user's drag operation, flick operation, or the like. As another example, in the case in which a content list displaying all content does not fit within the size of the display unit <NUM>, a portion of the content list is displayed on the display unit <NUM>, and the range of content displayed on the content list moves as a result of a user's drag operation, flick operation, or the like.

The controller <NUM> is a processor such as a central processing unit (CPU) that controls respective components of the client device <NUM> by operating according to a program stored in the storage unit <NUM>. For example, the controller <NUM> controls the display on the touchscreen display <NUM>. More specifically, the controller <NUM>, according to operating input acquired by the operating unit <NUM>, controls the display of content or a content list acquired from the storage unit <NUM> or the communication unit <NUM> discussed later on the display unit <NUM>. In addition, the controller <NUM> may also generate a content list on the basis of information acquired from the storage unit <NUM> or the communication unit <NUM>, and cause the generated content list to be displayed on the display unit <NUM>. Furthermore, the controller <NUM>, according to operating input acquired by the operating unit <NUM>, may perform operations on the data of content stored in the storage unit <NUM>, or perform operations on the data of content on a network via the communication unit <NUM>.

Herein, the controller <NUM> executes a first scrolling control that scrolls a document displayed on the touchscreen display <NUM> within a display region that includes the document. In addition, the controller <NUM> executes a second scrolling control that causes scrolling movement of the display region itself. Herein, the second scrolling control may be a control that causes temporary scrolling movement of the display region. In the second scrolling control, a spacer that differs from a document may be displayed in a blank display part produced by the scrolling movement of the display region. Note that in the second scrolling control, at least some of the interface elements included in the display region remain operable. Each of the above scrolling controls will be discussed in further detail later.

The storage unit <NUM> is semiconductor memory, a hard disk drive (HDD), or the like, for example, and stores various data used by the client device <NUM>. Furthermore, the storage unit <NUM> may also include a removable recording medium connected to the client device <NUM>. The storage unit <NUM> stores a program by which a processor functions as the controller <NUM>, for example. The storage unit <NUM> may also store the data of content to be played back by the controller <NUM> and output from the display unit <NUM> and/or an audio output unit.

The communication unit <NUM> is a communication device connected to a network by various wired or wireless communication schemes. For example, the communication unit <NUM> downloads the data of content to be output from the display unit <NUM> and/or an audio output unit from another device on the network. The communication unit <NUM> may also add another operation, such as delete or move, to content on another device on the network, according to operating input that the controller <NUM> acquires from the operating unit <NUM>. Also, the communication unit <NUM> may download a program by which a processor functions as the controller <NUM> from another device on the network, and provide the program to the storage unit <NUM>.

<FIG> is a diagram illustrating a first display example by a client device according to the first embodiment of the present disclosure. Referring to <FIG>, a status bar <NUM>, a menu bar <NUM>, and a content region <NUM> are included on a screen <NUM> being displayed on the touchscreen display <NUM> of the client device <NUM>. In the example illustrated in the drawing, a web page is being displayed in the content region <NUM>. Content such as a web page is one example of that which is referred to as a document in this specification.

In the state illustrated in <FIG>, a web page is being displayed in the content region <NUM> starting from the first part (Line1). Since later parts of the web page are not being displayed in the content region <NUM> at this time, the user causes these parts to be displayed by scrolling the content upwards inside the content region <NUM> with a drag operation or flick operation on the touchscreen display <NUM>. On the other hand, since the first part (Line1) of the web page is already being displayed in the state illustrated in <FIG>, from the perspective of viewing content, there is no need to scroll the content downwards any farther.

However, in the case in which the user is holding and operating the client device <NUM> with one hand, and the user's finger that operates the touchscreen display <NUM> is positioned at the bottom of the content region <NUM>, for example, it may not be easy in some cases to perform an operation on an interface element at the edge of the web page (near Line1) displayed at the top of the content region <NUM>. For example, in the case of a web page, there may occur operations such as selecting a link displayed among the content, pressing a button, or selecting text input. Such a phenomenon is particularly notable in the case in which the display position of the content region <NUM> on the touchscreen display <NUM> is fixed (that is, does not freely move as a window). Note that although the web page is displayed as Line1, Line2, and so on in the example illustrated in the drawing, this does not mean that the web page contains only text. The web page may also include images as well as interface elements such as links or buttons, which may be displayed in the parts illustrated in the drawing as Line <NUM> and the like.

Accordingly, in the present embodiment, the content region <NUM> itself undergoes scrolling movement under control by the controller <NUM>, as illustrated in <FIG>. In the illustrated example, which is not part of the claimed invention, the content region <NUM> undergoes scrolling movement downward, moving away from the menu bar <NUM> that was being displayed adjacent above. This scrolling movement, although temporary, is not transient. In other words, the state of scrolling movement undergone by the content region <NUM> as illustrated in <FIG> may be maintained until the next operation is given by the user, for example. In this state, interface elements such as links and buttons on the web page included in the content region <NUM> remain operable. Consequently, after causing scrolling movement of the content region <NUM> and moving the first part of the web page (near Line1) to the bottom of the screen <NUM>, it is possible for the user to perform a desired operation on an interface element included in that part. As a result, it is possible to easily operate even an interface element in a part that was not easy to operate before the scrolling movement of the content region <NUM>.

Meanwhile, a spacer <NUM> is displayed in the blank part between the menu bar <NUM> and the content region <NUM> produced by the scrolling movement of the content region <NUM>. The spacer <NUM> is displayed distinguished from the content displayed in the content region <NUM>, for example, and may express that downward scrolling of the content has already ended. For the spacer <NUM>, a simple graphic or other image may be displayed, or separate content such as an advertisement may be displayed, for example. The image or content displayed as the spacer <NUM> may also appear to slide down from above in conjunction with the downward scrolling movement of the content region <NUM>, for example. Alternatively, the image or content displayed as the spacer <NUM> may be positioned behind the content region <NUM>, and displayed as a hidden part that appears as a result of the downward scrolling movement of the content region <NUM>.

The scrolling movement of the content region <NUM> as illustrated in <FIG> (realized with the second scrolling control by the controller <NUM>) may be implemented separately from the scrolling of content displayed in the content region <NUM> (realized with the first scrolling control by the controller <NUM>). For example, the controller <NUM> may execute the second scrolling control that causes scrolling movement of the content region <NUM> in the case in which the operating unit <NUM> of the touchscreen display <NUM> acquires a second user operation that differs from a first user operation for scrolling content. Herein, the above first user operation and second user operation may be mutually different operations. For example, the first user operation and the second user operation may be mutually different touch operations with respect to a display region (for example, the content region <NUM>) on the touchscreen display <NUM>. More specifically, in the case in which the first user operation for scrolling content is a drag operation and/or a flick operation, the second user operation for causing scrolling movement of the content region <NUM> may be, for example, flicking on the second tap of a double tap, performing a long press with the pad of a finger, flicking after performing a long press with the pad of a finger, dragging with the pad of a finger, flicking after moving a finger up and down several times while tapping, operating a touch sensor (additionally) provided on the rear face of the client device <NUM>, operating a touch sensor (additionally) provided on a side face of the client device <NUM> or at the edge of the display, or shaking the client device <NUM> while tapping. Note that although a long press or a drag performed with the pad of a finger may be distinguished from a long press or a drag performed with a fingertip according to differences in contact surface area, for example, in this specification these operations may all be described as touch operations. In the present embodiment, the first user operation may be a simple operation compared to the second user operation, like the several examples above. In addition, a designated operation for the purpose of scrolling movement may also include an operation with respect to a region on the touchscreen display <NUM> other than the content region <NUM>, and may also include an operation with respect to an operating unit disposed on the case surrounding the touchscreen display <NUM> (for example, a touch sensor provided on the rear or side face of the client device <NUM>, or at the edge of the display).

In the case in which scrolling movement of the content region <NUM> starts as a result of a designated operation as above, subsequent drag operations and flick operations may be treated as operations controlling the magnitude of scrolling movement of the content region <NUM>, until a later-discussed operation that reverts the scrolling movement of the content region <NUM> is acquired, for example. In other words, in the case of acquiring the above designated operation, the controller <NUM> may switch the display control mode of the screen <NUM> from a mode that scrolls content inside the content region <NUM> to a mode that causes scrolling movement of the content region <NUM> itself. As a result, it may become easy for the user to place the content region <NUM> at a desired position via scrolling movement.

Alternatively, the controller <NUM> may execute the scrolling of content followed by scrolling movement of the content region <NUM> in response to an operation for scrolling content acquired by the operating unit <NUM>. In this case, scrolling movement of the content region <NUM> may be executed automatically in the case in which the operation for scrolling content, such as a drag operation or a flick operation, for example, is continually acquired even though the content displayed in the content region <NUM> has reached the edge (the top edge at which Line1 is being displayed in the example illustrated in the drawing). In this case, the user does not need to switch operation from the case of scrolling content up to that point in order to cause scrolling movement of the content region <NUM>. At this point, in cases such as when the user did not want to scroll the content region <NUM> as above, it is sufficient for the user to revert the scrolling of the content region <NUM> by executing an operation that scrolls the content in the opposite direction, for example.

A content region <NUM> that has undergone scrolling movement may be reverted in the case in which the user executes the above designated operation one more time or in the opposite direction, or executes an operation with respect to an interface element on the web page displayed while the content region <NUM> has undergone scrolling movement, for example.

<FIG> is a diagram illustrating a second display example by a client device according to the first embodiment of the present disclosure. Referring to <FIG>, a status bar <NUM>, a menu bar <NUM>, and a content list region <NUM> are included on a screen <NUM> being displayed on the touchscreen display <NUM> of the client device <NUM>. In the example illustrated in the drawing, thumbnails of image content are being displayed in the content list region <NUM>. The thumbnails are displayed with scrolling, since the thumbnails do not fit in the content list region <NUM> provided by the display unit <NUM> of the touchscreen display <NUM>. Such a content list is another example of that which is referred to as a document in this specification.

In the state illustrated in <FIG>, the first part of the thumbnails (P1 to P9) are being displayed in the content list region <NUM>. Since later parts of the thumbnails (P10 onwards) are not being displayed in the content list region <NUM> at this time, the user causes these thumbnails to be displayed by scrolling the content list upwards with a drag operation or flick operation on the touchscreen display <NUM>. On the other hand, since the first thumbnail (P1) is being displayed in the state illustrated in <FIG>, from the perspective of viewing thumbnails, there is no need to scroll the content list downwards any farther.

However, in the case in which the user is holding and operating the client device <NUM> with one hand, and the user's finger that operates the touchscreen display <NUM> is positioned at the bottom of the content list region <NUM>, for example, it may not be easy in some cases to perform some kind of operation on a thumbnail (P1 to P3, for example) display at the top of the content list region <NUM>. For example, in the case of thumbnails of image content, there may occur operations such as selecting a thumbnail to display, delete, or tag image content. Also, as another example, if titles or thumbnail images of music content are displayed in a content list region, there may occur operations such as selecting a title or image to play, delete, or tag music content.

Accordingly, in the present embodiment, the content list region <NUM> itself undergoes scrolling movement under control by the controller <NUM>, as illustrated in <FIG>. In the illustrated example, which is not part of the claimed invention, the content list region <NUM> undergoes scrolling movement downward, moving away from the menu bar <NUM> that was being displayed adjacent above. Similarly to the first display example above, this scrolling movement, although temporary, is not transient. In other words, the state of scrolling movement undergone by the content list region <NUM> as illustrated in <FIG> may be maintained until the next operation is given by the user, for example. In this state, thumbnails included in the content list region <NUM> remain operable (since various operations related to image content are possible, thumbnails may be said to be one type of interface element). Consequently, after causing scrolling movement of the content list region <NUM> and moving the first thumbnails (P1 to P3, for example) to the bottom of the screen, it is possible for the user to perform a desired operation on these thumbnails. As a result, it is possible to easily operate even a thumbnail that was not easy to operate before the scrolling movement of the content list region <NUM>.

Meanwhile, a spacer <NUM> is displayed in the blank part between the menu bar <NUM> and the content list region <NUM> produced by the scrolling movement of the content list region <NUM>. The spacer <NUM> is displayed distinguished from the thumbnails displayed in the content list region <NUM>, for example, and may express that downward scrolling of the content list has already ended. For the spacer <NUM>, a simple graphic or other image may be displayed, or separate content such as an advertisement may be displayed, for example. The image or content displayed as the spacer <NUM> may also appear to slide down from above in conjunction with the downward scrolling movement of the content list region <NUM>, for example. Alternatively, the image or content displayed as the spacer <NUM> may be positioned behind the content list region <NUM>, and displayed as a hidden part that appears as a result of the downward scrolling movement of the content list region <NUM>.

Similarly to the first display example above, the scrolling movement of the content list region <NUM> as illustrated in <FIG> may also be executed separately from the scrolling of a content list displayed in the content list region <NUM>. Accordingly, for example, the controller <NUM> may execute scrolling movement of the content list region <NUM> in the case in which the operating unit <NUM> of the touchscreen display <NUM> acquires a designated operation that differs from an operation for scrolling the content list. Since an example of an operation for the scrolling of a content list and an operation for the scrolling movement of a content list region is similar to the example of an operation for the scrolling of content and an operation for the scrolling movement of a content region in the first display example above, duplicate description thereof will be omitted herein.

In the case in which scrolling movement of the content list region <NUM> starts as a result of a designated operation, subsequent drag operations and flick operations may be treated as operations controlling the magnitude of scrolling movement of the content list region <NUM>, until a later-discussed operation that reverts the scrolling movement of the content list region <NUM> is acquired, for example. In other words, in the case of acquiring the above designated operation, the controller <NUM> may switch the display control mode of the screen <NUM> from a mode that scrolls thumbnails or the like inside the content list region <NUM> to a mode that causes scrolling movement of the content list region <NUM> itself. As a result, it may become easy to make adjustments so that the content list region <NUM> moves to a desired position by scrolling movement.

Alternatively, the controller <NUM> may execute the scrolling of a content list followed by scrolling movement of the content list region <NUM> in response to an operation for scrolling a content list acquired by the operating unit <NUM>. In this case, scrolling movement of the content list region <NUM> may be executed automatically in the case in which the operation for scrolling the content list, such as a drag operation or a flick operation, for example, is continually acquired even though the thumbnails displayed in the content list region <NUM> have reached the beginning (P1 in the example illustrated in the drawing). In this case, the user does not need to switch operation from the case of a scrolling content list up to that point in order to cause scrolling movement of the content list region <NUM>. At this point, in cases such as when the user did not want to scroll the content list region <NUM> as above, it is sufficient for the user to revert the scrolling of the content list region <NUM> by executing an operation that scrolls the content list in the opposite direction, for example.

A content list region <NUM> that has undergone scrolling movement may be reverted in the case in which the user executes the above designated operation one more time or in the opposite direction, or executes an operation with respect to a thumbnail displayed while the content list region <NUM> has undergone scrolling movement, for example.

Next, a second embodiment of the present disclosure will be described with reference to <FIG> and <FIG>. The present embodiment differs from the foregoing first embodiment in that a content region or a content list region undergoes scrolling movement together with a menu bar. Note that since all other points are similar to the first embodiment, duplicate description thereof will be omitted. The second embodiment is not part of the claimed invention.

<FIG> is a diagram illustrating a first display example by a client device according to the second embodiment of the present disclosure. Referring to <FIG>, a status bar <NUM>, a menu bar <NUM>, and a content region <NUM> are included on a screen <NUM> being displayed on the touchscreen display <NUM> of the client device <NUM>. In the example illustrated in the drawing, a web page is being displayed in the content region <NUM>.

In the state illustrated in <FIG>, a web page is being displayed in the content region <NUM>. Operations performed on the web page displayed in the content region <NUM>, such as back, forward, reload, stop, and add bookmark, for example, may be acquired by interface elements such as buttons placed on the menu bar <NUM>. In other words, the menu bar <NUM> may be referred to as an interface element placement region in which are placed interface elements that accept operations related to the web page. However, in the case in which the user is holding and operating the client device <NUM> with one hand, and the user's finger that operates the touchscreen display <NUM> is positioned at the bottom of the content region <NUM>, for example, it may not be easy in some cases to perform an operation on an interface element placed on the menu bar <NUM> above.

Accordingly, in the present embodiment, the menu bar <NUM> undergoes scrolling movement together with the content region <NUM> under control by the controller <NUM>, as illustrated in <FIG>. In the illustrated example, the menu bar <NUM> undergoes scrolling movement downward, moving away from the status bar <NUM> that was being displayed adjacent above. This scrolling movement, although temporary, is not transient. In other words, the scrolled state of the menu bar <NUM> as illustrated in <FIG> may be maintained until the next operation is given by the user, for example. In this state, interface elements such as buttons included on the menu bar <NUM> remain operable. Consequently, after moving the menu bar <NUM> to the bottom of the screen <NUM>, it is possible for the user to perform a desired operation on an interface element included on the menu bar <NUM>. In other words, the user is able to easily operate an interface element on the menu bar <NUM> without changing his or her grip on the client device <NUM>, for example.

Meanwhile, a spacer <NUM> is displayed in the blank part between the status bar <NUM> and the menu bar <NUM> produced by the scrolling movement of the menu bar <NUM> and the content region <NUM>. For the spacer <NUM>, a simple graphic or other image may be displayed, or separate content such as an advertisement may be displayed, for example. Alternatively, additional interface elements not included on the menu bar <NUM> may be displayed as the spacer <NUM>. The image, content, or interface elements displayed as the spacer <NUM> may also appear to slide down from above in conjunction with the downward scrolling movement of the menu bar <NUM>, for example. Alternatively, the image, content, or interface elements displayed as the spacer <NUM> may be positioned behind the menu bar <NUM> and the content region <NUM>, and displayed as a hidden part that appears as a result of the downward scrolling movement of the menu bar <NUM>.

The scrolling movement of the menu bar <NUM> as illustrated in <FIG> may also be executed separately from the scrolling of content displayed in the content region <NUM>. For example, the controller <NUM> may execute scrolling movement of the menu bar <NUM> in the case in which the operating unit <NUM> of the touchscreen display <NUM> acquires a designated operation that differs from an operation for scrolling the content. Since an example of an operation for the scrolling of content and an operation for the scrolling movement of a menu bar is similar to the example of an operation for the scrolling of content and an operation for the scrolling movement of a content region in the foregoing first embodiment, duplicate description thereof will be omitted herein.

Furthermore, for the above designated operation, the controller <NUM> may respectively set an operation for causing scrolling movement of the content region <NUM> and an operation for causing scrolling movement of the menu bar <NUM>, and selectively execute scrolling movement of these regions. For example, the controller <NUM> may set an operation of flicking after a double tap as the operation for scrolling movement of the content region <NUM>, and set an operation of flicking after a long press with the pad of a finger as the operation for scrolling movement of the menu bar <NUM>.

In the case in which scrolling movement of the menu bar <NUM> starts as a result of a designated operation, subsequent drag operations and flick operations may be treated as operations controlling the magnitude of scrolling movement of the menu bar <NUM>, until a later-discussed operation that reverts the scrolling movement of the menu bar <NUM> is acquired, for example. In other words, in the case of acquiring the above designated operation, the controller <NUM> may switch the display control mode of the screen <NUM> from a mode that scrolls content inside the content region <NUM> to a mode that causes scrolling movement of the menu bar <NUM> and the content region <NUM>. As a result, it may become easy for the user to place the menu bar <NUM> at a desired position via scrolling movement.

As a result of the user placing the menu bar <NUM> at a desired position with an operation like the above, in some cases the user's next operation may be acquired in a state in which the menu bar <NUM> is displayed at the bottom edge of the screen <NUM>, and the content region <NUM> is no longer displayed, as in <FIG>. Also, the user's next operation may be acquired in a state in which the menu bar <NUM> is displayed in the approximate center of the screen <NUM>, and the content region <NUM> is displayed below, as in <FIG>. At this point, since the user is conceivably executing scrolling movement of the menu bar <NUM> in order to operate the menu bar <NUM>, interface elements being displayed in the content region <NUM> may also be disabled. Alternatively, interface elements displayed in the content region <NUM> may also remain operable in order to raise the user's freedom of operation.

A menu bar <NUM> that has undergone scrolling movement may be reverted together with the content region <NUM> in the case in which the user executes the above designated operation one more time or in the opposite direction, or executes an operation with respect to an interface element included on the menu bar <NUM> while the menu bar <NUM> has undergone scrolling movement, for example.

<FIG> is a diagram illustrating a second display example by a client device according to the second embodiment of the present disclosure. Referring to <FIG>, a status bar <NUM>, a menu bar <NUM>, and a content list region <NUM> are included on a screen <NUM> being displayed on the touchscreen display <NUM> of the client device <NUM>. In the example illustrated in the drawing, thumbnails of image content are being displayed in the content list region <NUM>.

In the state illustrated in <FIG>, the first part of the thumbnails (P1 to P9) are being displayed in the content list region <NUM>. Operations performed on these thumbnails, such as play, delete, and move, for example, may be acquired by interface elements such as buttons displayed on the menu bar <NUM>. However, in the case in which the user is holding and operating the client device <NUM> with one hand, and the user's finger that operates the touchscreen display <NUM> is positioned at the bottom of the content list region <NUM>, for example, it may not be easy in some cases to perform an operation on an interface element placed on the menu bar <NUM> above.

Accordingly, in the present embodiment, the menu bar <NUM> undergoes scrolling movement together with the content list region <NUM> under control by the controller <NUM>, as illustrated in <FIG>. In the illustrated example, the menu bar <NUM> undergoes scrolling movement downward, moving away from the status bar <NUM> that was being displayed adjacent above. Similarly to the first display example above, this scrolling movement, although temporary, is not transient. In other words, the scrolled state of the menu bar <NUM> as illustrated in <FIG> may be maintained until the next operation is given by the user, for example. In this state, interface elements such as buttons displayed on the menu bar <NUM> remain operable. Consequently, after moving the menu bar <NUM> to the bottom of the screen <NUM>, it is possible for the user to perform a desired operation on an interface element included on the menu bar <NUM>. As a result, the user is able to easily operate an interface element on the menu bar <NUM> without changing his or her grip on the client device <NUM>, for example.

Meanwhile, a spacer <NUM> is displayed in the blank part between the status bar <NUM> and the menu bar <NUM> produced by the scrolling movement of the content list region <NUM> and the menu bar <NUM>. For the spacer <NUM>, a simple graphic or other image may be displayed, or separate content such as an advertisement may be displayed, for example. Alternatively, additional interface elements not included on the menu bar <NUM> may be displayed as the spacer <NUM>. The image, content, or interface elements displayed as the spacer <NUM> may also appear to slide down from above in conjunction with the downward scrolling movement of the menu bar <NUM>, for example. Alternatively, the image, content, or interface elements displayed as the spacer <NUM> may be positioned behind the menu bar <NUM> and the content list region <NUM>, and displayed as a hidden part that appears as a result of the downward scrolling movement of the menu bar <NUM>.

Similarly to the first display example above, the scrolling movement of the menu bar <NUM> as illustrated in <FIG> may also be executed separately from the scrolling of a content list displayed in the content list region <NUM>. Accordingly, for example, the controller <NUM> may execute scrolling movement of the menu bar <NUM> in the case in which the operating unit <NUM> of the touchscreen display <NUM> acquires a designated operation that differs from an operation for scrolling the content list. Since an example of an operation for the scrolling of content and an operation for the scrolling movement of a menu bar is similar to the example of an operation for the scrolling of content and an operation for the scrolling movement of a content region in the foregoing first embodiment, duplicate description thereof will be omitted herein.

Furthermore, similarly to the first display example above, the controller <NUM> may respectively set an operation for causing scrolling movement of the content list region <NUM> and an operation for causing scrolling movement of the menu bar <NUM>, and selectively execute scrolling movement of these regions. Also, in the case in which scrolling movement of the menu bar <NUM> starts as a result of a designated operation, subsequent drag operations and flick operations may be treated as operations controlling the magnitude of scrolling movement of the menu bar <NUM>, until a later-discussed operation that reverts the scrolling movement of the menu bar <NUM> is acquired, for example.

As a result of the user placing the menu bar <NUM> at a desired position with an operation like the above, in some cases the user's next operation may be acquired in a state in which the menu bar <NUM> is displayed at the bottom edge of the screen <NUM>, and the content list region <NUM> is no longer displayed, as in <FIG>. Also, the user's next operation may be acquired in a state in which the menu bar <NUM> is displayed in the approximate center of the screen <NUM>, and the content list region <NUM> is displayed below, as in <FIG>. At this point, since the user is conceivably executing scrolling movement of the menu bar <NUM> in order to operate the menu bar <NUM>, operations on thumbnails being displayed in the content list region <NUM> may also be disabled. Alternatively, thumbnails displayed in the content list region <NUM> may also remain operable in order to raise the user's freedom of operation.

A menu bar <NUM> that has undergone scrolling movement may be reverted in the case in which the user executes the above designated operation one more time or in the opposite direction, or executes an operation with respect to an interface element included on the menu bar <NUM> while the menu bar <NUM> has undergone scrolling movement, for example.

Next, a third embodiment of the present disclosure will be described with reference to <FIG> and <FIG>. The present embodiment differs from the foregoing first and second embodiments in that a content region or a content list region undergoes scrolling movement together with a menu bar and a status bar. Note that since all other points are similar to the first or second embodiment, duplicate description thereof will be omitted.

<FIG> is a diagram illustrating a first display by a client device according to the third embodiment of the present disclosure. Referring to <FIG>, a status bar <NUM>, a menu bar <NUM>, and a content region <NUM> are included on a screen <NUM> being displayed on the touchscreen display <NUM> of the client device <NUM>. In the example illustrated in the drawing, a web page is being displayed in the content region <NUM>.

In the state illustrated in <FIG>, a web page is being displayed in the content region <NUM>. Operations performed on the web page displayed in the content region <NUM>, such as back, forward, reload, stop, and add bookmark, for example, may be acquired by interface elements such as buttons placed on the menu bar <NUM>. Also, status notifications indicating received messages, software updates, and the like regarding the overall system of the client device <NUM> are referenced by selecting the status bar <NUM>. However, in the case in which the user is holding and operating the client device <NUM> with one hand, and the user's finger that operates the touchscreen display <NUM> is positioned at the bottom of the content region <NUM>, for example, it may not be easy in some cases to perform an operation on an interface element placed on the menu bar <NUM> above, or select the status bar <NUM> placed even farther above.

Accordingly, in the present embodiment, the status bar <NUM> undergoes scrolling movement together with the menu bar <NUM> and the content region <NUM> under control by the controller <NUM>, as illustrated in <FIG>. In the illustrated example, the status bar <NUM> undergoes scrolling movement downward, moving away from the top edge of the screen <NUM>. This scrolling movement, although temporary, is not transient. In other words, the scrolled state of the status bar <NUM> as illustrated in <FIG> is maintained until the next operation is given by the user. While in this state, the status bar <NUM> remains selectable. In addition, interface elements such as buttons included on the menu bar <NUM> may also remain operable. Consequently, after moving the status bar <NUM> and the menu bar <NUM> to the bottom of the screen <NUM>, it is possible for the user to select the status bar <NUM> to display a notification, or perform a desired operation on an interface element included on the menu bar <NUM>. In other words, the user is able to easily operate an interface element on the menu bar <NUM> or select the status bar <NUM>, without changing his or her grip on the client device <NUM>, for example.

Meanwhile, a spacer <NUM> is displayed in the blank part above the status bar <NUM> produced by the scrolling movement of the status bar <NUM>, the menu bar <NUM>, and the content region <NUM>. For the spacer <NUM>, a simple graphic or other image may be displayed, or separate content such as an advertisement may be displayed, for example. Alternatively, additional interface elements not included on the menu bar <NUM> may be displayed as the spacer <NUM>. The image, content, or interface elements displayed as the spacer <NUM> may also appear to slide down from above in conjunction with the downward scrolling movement of the status bar <NUM>, for example. Alternatively, the image, content, or interface elements displayed as the spacer <NUM> may be positioned behind the status bar <NUM>, the menu bar <NUM>, and the content region <NUM>, and displayed as a hidden part that appears as a result of the downward scrolling movement of the status bar <NUM>.

The scrolling movement of the status bar <NUM> as illustrated in <FIG> is also executed separately from the scrolling of content displayed in the content region <NUM> The controller <NUM> executes scrolling movement of the status bar <NUM> in the case in which the operating unit <NUM> of the touchscreen display <NUM> acquires a designated operation that differs from an operation for scrolling the content. Since an operation for the scrolling of content and an operation for the scrolling movement of a status bar is similar to the example of an operation for the scrolling of content and an operation for the scrolling movement of a content region in the foregoing first embodiment, duplicate description thereof will be omitted herein.

Furthermore, for the above designated operation, the controller <NUM> respectively sets an operation for causing scrolling movement of the content region <NUM> and an operation for causing scrolling movement of the status bar <NUM>, and selectively executes scrolling movement of these regions. For example, the controller <NUM> may set an operation of flicking after a double tap as the operation for scrolling movement of the content region <NUM>, and set an operation of flicking after a long press with the pad of a finger as the operation for scrolling movement of the status bar <NUM>.

In the case in which scrolling movement of the status bar <NUM> starts as a result of a designated operation, subsequent drag operations and flick operations are treated as operations controlling the magnitude of scrolling movement of the status bar <NUM>, until a later-discussed operation that reverts the scrolling movement of the status bar <NUM> is acquired. In other words, in the case of acquiring the above designated operation, the controller <NUM> switches the display control mode of the screen <NUM> from a mode that scrolls content inside the content region <NUM> to a mode that causes scrolling movement of the status bar <NUM>, the menu bar <NUM>, and the content region <NUM>. As a result, it becomes easy for the user to place the status bar <NUM> or the menu bar <NUM> at a desired position via scrolling movement.

As a result of the user placing the status bar <NUM> or the menu bar <NUM> at a desired position with an operation like the above, in some cases the user's next operation may be acquired in a state in which the status bar <NUM> and the menu bar <NUM> are displayed at the bottom edge of the screen <NUM>, and the content region <NUM> is no longer displayed, as in <FIG>. Also, the user's next operation may be acquired in a state in which the status bar <NUM> and the menu bar <NUM> are displayed in the approximate center of the screen <NUM>, and the content region <NUM> is displayed below, as in <FIG>. At this point, since the user is conceivably executing scrolling movement of the status bar <NUM> in order to operate the status bar <NUM> or the menu bar <NUM>, interface elements being displayed in the content region <NUM> may also be disabled. Alternatively, interface elements displayed in the content region <NUM> may also remain operable in order to raise the user's freedom of operation.

A status bar <NUM> and a menu bar <NUM> that have undergone scrolling movement may be reverted together with the content region <NUM> in the case in which the user executes the above designated operation one more time or in the opposite direction, or ends viewing of a notification displayed in the status bar <NUM> or executes an operation with respect to an interface element included on the menu bar <NUM> while the status bar <NUM> and the menu bar <NUM> have undergone scrolling movement, for example.

<FIG> is a diagram illustrating a second display by a client device according to the third embodiment of the present disclosure. Referring to <FIG>, a status bar <NUM>, a menu bar <NUM>, and a content list region <NUM> are included on a screen <NUM> being displayed on the touchscreen display <NUM> of the client device <NUM>. In the example illustrated in the drawing, thumbnails of image content are being displayed in the content list region <NUM>.

In the state illustrated in <FIG>, the first part of the thumbnails (P1 to P9) are being displayed in the content list region <NUM>. Operations performed on these thumbnails, such as play, delete, and move, for example, may be acquired by interface elements such as buttons displayed on the menu bar <NUM>. Also, notifications indicating received messages, software updates, and the like regarding the overall system of the client device <NUM> are referenced by selecting the status bar <NUM>. However, in the case in which the user is holding and operating the client device <NUM> with one hand, and the user's finger that operates the touchscreen display <NUM> is positioned at the bottom of the content list region <NUM>, for example, it may not be easy in some cases to perform an operation on an interface element placed on the menu bar <NUM> above, or select the status bar <NUM> placed even farther above.

Accordingly, in the present embodiment, the status bar <NUM> undergoes scrolling movement together with the menu bar <NUM> and the content list region <NUM> under control by the controller <NUM>, as illustrated in <FIG>. The status bar <NUM> undergoes scrolling movement downward, moving away from the top edge of the screen <NUM>. Similarly to the first display above, this scrolling movement, although temporary, is not transient. In other words, the scrolled state of the status bar <NUM> as illustrated in <FIG> is maintained until the next operation is given by the user, for example. While in this state, the status bar <NUM> remains selectable. In addition, interface elements such as buttons included on the menu bar <NUM> may also remain operable. Consequently, after moving the status bar <NUM> and the menu bar <NUM> to the bottom of the screen <NUM>, it is possible for the user to select the status bar <NUM> to display a notification, or perform a desired operation on an interface element included on the menu bar <NUM>. In other words, the user is able to easily operate an interface element on the menu bar <NUM> or select the status bar <NUM>, without changing his or her grip on the client device <NUM>, for example.

Meanwhile, a spacer <NUM> is displayed in the blank part above the status bar <NUM> produced by the scrolling movement of the status bar <NUM>, the menu bar <NUM>, and the content list region <NUM>. For the spacer <NUM>, a simple graphic or other image may be displayed, or separate content such as an advertisement may be displayed, for example. Alternatively, additional interface elements not included on the menu bar <NUM> may be displayed as the spacer <NUM>. The image, content, or interface elements displayed as the spacer <NUM> may also appear to slide down from above in conjunction with the downward scrolling movement of the status bar <NUM>, for example. Alternatively, the image, content, or interface elements displayed as the spacer <NUM> may be positioned behind the status bar <NUM>, the menu bar <NUM>, and the content list region <NUM>, and displayed as a hidden part that appears as a result of the downward scrolling movement of the status bar <NUM>.

Similarly to the first display above, the scrolling movement of the status bar <NUM> as illustrated in <FIG> is also executed separately from the scrolling of a content list displayed in the content list region <NUM>. The controller <NUM> executes scrolling movement of the status bar <NUM> in the case in which the operating unit <NUM> of the touchscreen display <NUM> acquires a designated operation that differs from an operation for scrolling the content list. Since an operation for the scrolling of a content list and an operation for the scrolling movement of a status bar is similar to the example of an operation for the scrolling of content and an operation for the scrolling movement of a content region in the foregoing first embodiment, duplicate description thereof will be omitted herein.

Furthermore, similarly to the first display above, the controller <NUM> respectively sets an operation for causing scrolling movement of the content list region <NUM> and an operation for causing scrolling movement of the status bar <NUM>, and selectively executes scrolling movement of these regions. Also, in the case in which scrolling movement of the status bar <NUM> starts as a result of a designated operation, subsequent drag operations and flick operations are treated as operations controlling the magnitude of scrolling movement of the status bar <NUM>, until a later-discussed operation that reverts the scrolling movement of the status bar <NUM> is acquired.

As a result of the user placing the status bar <NUM> or the menu bar <NUM> at a desired position with an operation like the above, in some cases the user's next operation may be acquired in a state in which the status bar <NUM> and the menu bar <NUM> are displayed at the bottom edge of the screen <NUM>, and the content list region <NUM> is no longer displayed, as in <FIG>. Also, the user's next operation may be acquired in a state in which the status bar <NUM> and the menu bar <NUM> are displayed in the approximate center of the screen <NUM>, and the content list region <NUM> is displayed below, as in <FIG>. At this point, since the user is conceivably executing scrolling movement of the status bar <NUM> in order to operate the status bar <NUM> or the menu bar <NUM>, operations on thumbnails being displayed in the content list region <NUM> may also be disabled. Alternatively, thumbnails displayed in the content list region <NUM> may also remain operable in order to raise the user's freedom of operation.

A status bar <NUM> and a menu bar <NUM> that have undergone scrolling movement may be reverted together with the content list region <NUM> in the case in which the user executes the above designated operation one more time or in the opposite direction, or ends viewing of a notification displayed in the status bar <NUM> or executes an operation with respect to an interface element included on the menu bar <NUM> while the status bar <NUM> and the menu bar <NUM> have undergone scrolling movement, for example.

Next, a fourth embodiment of the present disclosure will be described with reference to <FIG>. In the present embodiment, the scrolling movement starting from a content region (or a content list region), the scrolling movement starting from a menu bar, and the scrolling movement starting from a status bar in the foregoing first through third embodiments are used differently according to the support state of the operating system (OS) of the client device <NUM> or an application displayed on-screen.

<FIG> is a flowchart illustrating an example of a process by a client device according to the fourth embodiment of the present disclosure. First, the operating unit <NUM> of the client device <NUM> acquires a designated operation indicating scrolling movement that is not the scrolling of content (or a content list) (step S101). Herein, the designated operation may be, as discussed earlier, flicking on the second tap of a double tap, performing a long press with the pad of a finger, flicking after performing a long press with the pad of a finger, dragging with the pad of a finger, flicking after moving a finger up and down several times while tapping, operating a touch sensor (additionally) provided on the rear face of the client device <NUM>, operating a touch sensor (additionally) provided on a side face of the client device <NUM> or at the edge of the display, or shaking the client device <NUM> while tapping, for example.

At this point, in the case of determining that the operating unit <NUM> has acquired the designated operation, the controller <NUM> may control the display unit <NUM> to display an effect indicating that a separate scrolling display mode has started. For example, an effect like peeling paper may be displayed in the portions undergoing scrolling movement on-screen (for example, the content region <NUM> in the example of <FIG>, the menu bar <NUM> in the example of <FIG>, or the status bar <NUM> in the example of <FIG>). Also, an effect may be displayed in which these portions are reduced slightly and appear to be floating. These effects may be displayed not only at the start, but also during the scrolling movement.

Next, a determination of whether or not the OS supports a scrolling movement function is made (step S103), and if the OS supports the function (YES), scrolling movement starting from the status bar like in the third embodiment is executed (step S105). In the present embodiment, since the status bar is displayed by a function of the OS, OS support of a scrolling movement function may be a condition for realizing scrolling movement starting from the status bar. Obviously, scrolling movement starting from the menu bar or scrolling movement starting from the content region (or content list region) may also be executed, even in the case in which the OS supports the function.

Conversely, in the case in which the OS does not support the function in the determination of step S103 (NO), a determination of whether or not the application being displayed on-screen supports a scrolling movement function is made (step S107). At this point, if the application supports the function (YES), scrolling movement starting from the menu bar like in the second embodiment is executed (step S109). In the present embodiment, since the menu bar is displayed by a function of the application, application support of a scrolling movement function may be a condition for realizing scrolling movement starting from the menu bar. Obviously, scrolling movement starting from the content region (or content list region) may also be executed, even in the case in which the application supports the function.

Conversely, in the case in which the application does not support the function in the determination of step S107 (NO), scrolling movement starting from the content region (or content list region) like in the first embodiment is executed (step S111). At this point, the controller <NUM> adds a dummy content portion, advertising, or the like to be displayed as a spacer at the beginning of the content (or content list), for example, such that this content portion or advertising is displayed following the ordinary scrolling of the content (or content list).

<FIG> and <FIG> are diagrams illustrating examples of upward scrolling movement according to another embodiment of the present disclosure that is not part of the claimed invention. <FIG> illustrate an example of a content display, while <FIG> illustrate an example of a content list display. The foregoing first through third embodiments are described by taking as an example the case in which the user's finger operating the touchscreen display <NUM> is positioned at the bottom of the content region <NUM> (or the content list region <NUM>). Similarly, usability improvement using upward scrolling movement may also be attempted in the case in which the user's finger is positioned at the top of the content region <NUM> (or the content list region <NUM>).

For example, as illustrated in the examples of <FIG> and <FIG>, the content region <NUM> (or the content list region <NUM>) may undergo upward scrolling movement to place interface elements or thumbnails closer to a range easily operated by the user. Similarly, as illustrated in the examples of <FIG> and <FIG>, the menu bar <NUM> or <NUM> may also undergo upward scrolling movement in the case in which the menu bar <NUM> or <NUM> is displayed at the bottom edge rather than the top edge of the screen <NUM> or <NUM>. Also, as illustrated in the examples of <FIG> and <FIG>, the status bar <NUM> or <NUM> may also undergo upward scrolling movement in the case in which the status bar <NUM> or <NUM> is displayed at the bottom edge of the screen <NUM> or <NUM>.

<FIG> is a diagram illustrating an example of automatic stopping and spacer display according to another embodiment of the present disclosure. In the illustrated example, scrolling movement starting from the status bar <NUM> is executed. In <FIG>, thumbnails (P10 to P17) of image content displayed in the content list region <NUM> are scrolled, without starting a mode for scrolling movement of the status bar <NUM>. At this point, if a designated operation as discussed above is acquired, such as a long press with the pad of a finger, scrolling with the pad of a finger, or shaking the client device <NUM> while tapping, for example, the controller <NUM> starts the mode for scrolling movement of the status bar <NUM>.

<FIG> is a display example of when the mode for scrolling movement of the status bar <NUM> is started. At this point, the status bar <NUM>, the menu bar <NUM>, and the content list region <NUM> move slightly downward while keeping the displayed content (like when captured). The spacer <NUM> is displayed in the blank part produced by the movement. In the illustrated example, the spacer <NUM> may be an image like a string by which the status bar <NUM> hangs from the top edge of the screen <NUM>. At the time of <FIG>, this string is very slack.

<FIG> is a display example while scrolling movement of the status bar <NUM> is in progress. At this point, the status bar <NUM>, the menu bar <NUM>, and the content list region <NUM> are moving downward while continuing to keep the displayed content at the time of <FIG>. As discussed above, even in this state it is still possible to select the status bar <NUM> or operate an interface element included on the menu bar <NUM>. Also, the string being displayed as the spacer <NUM> is gradually losing slack to reflect that the distance has widened between the top edge of the screen <NUM> and the status bar <NUM>.

<FIG> is a display example of when scrolling movement of the status bar <NUM> has stopped. At this point, the status bar <NUM> and the menu bar <NUM> have moved close to the bottom edge of the screen <NUM>, and are estimated to be at a position that is sufficiently easily to operate with a user's finger positioned at the bottom of the screen <NUM>, for example. Consequently, the controller <NUM> may also set this position as a limit point for the scrolling movement of the status bar <NUM>. At this point, the string being displayed as the spacer <NUM> is being displayed in a taut state to reflect that the downward movement of the status bar <NUM> has reached the limit.

In the illustrated example, the scrolling movement of the status bar <NUM> and the menu bar <NUM> may be stopped at a suitable position without user adjustment, as a result of the controller <NUM> of the client device <NUM> automatically determining a travel amount for the scrolling movement of the status bar <NUM>. Herein, the travel amount of the scrolling movement may be determined according to the display size of interface elements that remain operable, or in other words, the display size of the status bar <NUM> or interface elements displayed on the menu bar <NUM> in the above example. Also, by displaying an image expressing the relationship between an automatically determined travel amount and the current travel amount, like the string in the above example, the user is able to intuitively recognize how far the scrolling movement has advanced. Obviously, similar control and display is likewise possible for scrolling movement of the menu bar <NUM> or the content list region <NUM>, as well as the scrolling movement of respective regions on the screen <NUM>.

<FIG> is a diagram illustrating a display example when reverting the scrolling movement illustrated in <FIG>. <FIG> is the same display as <FIG>, but if at this point a designated operation for reverting scrolling movement is acquired, such as an operation of tapping and then flicking upward, for example, the controller <NUM> starts a control for reverting the scrolling movement of the status bar <NUM>. In the illustrated example, the scrolling movement is automatically reverted by the above designated operation. <FIG> illustrates a midway state. Unlike the example of <FIG>, for example, the string displayed as the spacer <NUM> remains in a taut state, and movement may be expressed as though the status bar <NUM> is being dragged upward, for example.

As illustrated in <FIG>, when the status bar <NUM> moves up to the top edge of the screen <NUM>, the mode for scrolling movement of the status bar <NUM> ends, and subsequently, the scrolling display of the thumbnails displayed in the content list region <NUM> is resumed. Note that although in the above example the scrolling movement is automatically reverted by the operation in <FIG>, in another example, the scrolling movement may be reverted manually by the user executing an upward drag operation or flick operation until reaching the state in <FIG>. In this case, it is also possible to stop the upward operation partway through, and again return to the state in <FIG>. Thus, the display of the spacer <NUM> in <FIG> may be a somewhat slack string similar to <FIG> to express that the status bar <NUM> is movable both upwards and downwards.

<FIG> is a diagram illustrating a display when reverting the scrolling movement illustrated in <FIG>. <FIG> is the same display as <FIG>, but at this point an operation selecting the status bar <NUM> is acquired. As discussed earlier, since notifications indicating received messages, software updates, and the like are displayed on the status bar <NUM>, if the status bar <NUM> is selected, a status screen <NUM> as illustrated in <FIG> may be referenced. By selecting a close button <NUM> displayed on the status screen <NUM>, the display of the status screen <NUM> ends, and in addition, the display position of the status bar <NUM> reverts back as illustrated in <FIG>, and the scrolling movement mode ends.

<FIG> is a diagram illustrating yet another display example when reverting the scrolling movement illustrated in <FIG>. <FIG> is the same display as <FIG>, but at this point an operation via an interface element included on the menu bar <NUM> produces a screen transition within an application, or in other words, a change in the display of a document. In the illustrated example, a transition to a map display screen <NUM> as illustrated in <FIG> is being executed, and at this point the scrolling movement of the status bar <NUM> is reverted back. The position of the status bar <NUM> may revert back immediately, or revert over a designated amount of time while displaying an animation or the like. On the other hand, although a screen transition is not produced in the display of <FIG> even in the case in which an operation, such as deleting content, for example, is executed on a thumbnail of image content displayed in the content list region <NUM> via an interface element included on the menu bar <NUM>, the scrolling movement of the status bar <NUM> may revert back as illustrated in <FIG>.

<FIG> is a diagram illustrating a display example of a horizontal screen according to another embodiment of the present disclosure. In the example in <FIG>, when a contact region (Touch) exists on the right side of a horizontal screen <NUM>, the displayed content undergoes scrolling movement to the right, and a spacer <NUM> is displayed in the emptied part. Also, in the example in <FIG>, when a contact region (Touch) exists on the left side of the horizontal screen <NUM>, the displayed content undergoes scrolling movement to the left, and a spacer <NUM> is displayed in the emptied part. In this way, the embodiment of the present disclosure discussed above is also applicable to a horizontal screen similarly to a vertical screen in a client device <NUM> such as a smartphone.

<FIG> is a diagram illustrating a display example of a large screen according to another embodiment of the present disclosure. In the example in <FIG>, when a contact region (Touch) exists in the lower-right of a large screen <NUM>, the displayed content undergoes scrolling movement down and to the right, and a spacer <NUM> is displayed in the emptied L-shaped part. Also, in the example in <FIG>, when a contact region (Touch) exists in the lower-left of the large screen <NUM>, the displayed content undergoes scrolling movement down and to the left, and a spacer <NUM> is displayed in the emptied L-shaped part. In this way, the embodiment of the present disclosure discussed above is also applicable to a large screen the may be scrolled both vertically and horizontally in a client device <NUM> such as a tablet. In this case, the travel direction of the scrolling movement may be determined according to a position on a touchscreen display or on a case near a touchscreen display at which a designated user operation was executed, as in the above examples.

In the foregoing embodiment, display control for a client device is executed internally within the client device, such that the client device functions as the display control device. However, an embodiment of the present disclosure is not limited to such an example. For example, a server that communicates with a client device via a network may also provide the function of display control for the client device. In this case, one or multiple server devices constituting the server function as the display control device.

Embodiments of the present disclosure encompass a display control device (a client device or a server device) as described in the foregoing, a system, an information processing method executed by a display device or system, a program for causing a display control device to function, and a non-transient tangible medium storing a program, for example.

Claim 1:
An information processing apparatus, comprising:
a touchscreen display (<NUM>); and
being configured to:
display, on the touchscreen display (<NUM>), status information of a status of the information processing apparatus in a status region (<NUM>), a content in a content region (<NUM>), and a menu region (<NUM>) in a first display control mode,
detect a first touch operation on the touchscreen display (<NUM>);
cause, in response to the detection of the first touch operation, scrolling to scroll the displayed content inside the content region (<NUM>),
detect a second touch operation different from the first touch operation on the touchscreen display (<NUM>),
cause, in response to the detection of the second touch operation, a second display control mode in which a display position of the status region (<NUM>), a display position of the menu region (<NUM>), and a display position of the content region (<NUM>) in the first display control mode are each changed to a changed position which is lower on the touchscreen display (<NUM>) than the display position in the first display control mode,
detect a third touch operation performed on the touchscreen display (<NUM>) and in the status region (<NUM>) at the changed position in the second display control mode,
display, in response to the detection of the third touch operation, a notification (<NUM>) in the second display control mode,
detect a fourth touch operation performed on a button (<NUM>) displayed on the touchscreen display (<NUM>), and
revert, in response to the detection of the fourth touch operation, the second display control mode to the first display control mode.