Display device, remote control device and view display method

Abstract

The invention discloses a display device, a remote control device and a view display method.The method comprises the steps that an operation interface containing a list view is presented on a displayer, and the list view comprises at least one sub-view which is not completely displayed on the operation interface; under the condition that the sub-view receives a direction key event, running a program used for requesting to scroll the rectangular area of the sub-view to a visible position on a screen, so that the sub-view is scrolled and displayed at the visible position in the operation interface according to the scroll amount; wherein the scroll amount is calculated according to the visible area of the sub-view in the operation interface and the area of the sub-view; and under the condition that the sub-view receives a hovering event of the cursor, ending operation of a program used for requesting to roll the rectangular area of the sub-view to a visible position on the screen so as to maintain that the sub-view is not completely displayed on the operation interface. The view can be prevented from rolling continuously when the remote control equipment points to the edge of the operation interface, and the user experience is improved.

Description

Technical Field

[0001] This application relates to the technical field of display devices, and in particular, to a display device, a remote control device, and a view display method. Background Art

[0002] With the rapid development of the functions of display devices, the operation interface has become increasingly complex. Traditional remote control devices are operated through buttons, with cumbersome operations and low interaction efficiency. Therefore, remote control devices with pointing functions have emerged. However, when the remote control device points to the edge of the operation interface, the un-displayed view will continuously scroll into the operation interface, resulting in a poor user experience. Summary of the Invention

[0003] This application provides a display device, a remote control device, and a view display method, which can avoid continuous view scrolling when the remote control device points to the edge of the operation interface and improve the user experience.

[0004] In a first aspect, some embodiments provide a display device, including: a display, a communication module, and a controller. Among them, the display is configured to display an operation interface, and there is a cursor in the operation interface, and the position of the cursor on the operation interface is determined by the position pointed by the remote control device in three-dimensional space;

[0005] The communication module is configured to be connected to the remote control device;

[0006] And at least one controller, which is connected to the display and the communication module and is configured to execute instructions to enable the display device to:

[0007] Present an operation interface including a list view on the display, where the list view includes at least one sub-view that is not completely displayed in the operation interface;

[0008] In the case where the sub-view receives a direction key event, run a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, so that the sub-view scrolls and is displayed at a visible position within the operation interface according to the scrolling amount; where the scrolling amount is calculated based on the visible area of the sub-view within the operation interface and the self-area of the sub-view;

[0009] In the case where the sub-view receives a cursor hovering event, end the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen to maintain the sub-view not being completely displayed in the operation interface.

[0010] Technical effects: Some embodiments provide a display device. An operation interface including a list view is presented on a display. The list view includes at least one sub-view that is not fully displayed in the operation interface. When the sub-view receives a direction key event, a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is run. In this way, the sub-view is scrolled and displayed at a visible position within the operation interface according to the scroll amount. And since only one direction key event can be received after a single operation of the direction key, the program will not cause other sub-views to continuously scroll onto the screen after running. When the sub-view receives a cursor hovering event, the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is ended. In this way, even if the sub-view continuously receives a cursor hovering event, since the program is ended, the sub-view is prevented from scrolling onto the screen. Therefore, it is possible to maintain the sub-view not being fully displayed in the operation interface. At the same time, other sub-views cannot receive the hovering event and are blocked from scrolling, so that when the remote control device points to the edge of the operation interface, continuous scrolling of the view is avoided, improving the user experience.

[0011] In a second aspect, some embodiments further provide a remote control device, including: a communication unit and at least one processor. Among them, it is configured to communicate with the display device, and present an operation interface including a list view on the display of the display device. The list view includes at least one sub-view that is not fully displayed in the operation interface;

[0012] And at least one processor, which is connected to the communication unit and is configured to execute instructions to enable the remote control device to:

[0013] In response to a trigger operation of a direction key, send direction key information to the display device through the communication unit to instruct the display device to distribute a direction key event after receiving the direction key information, and when the sub-view matching the direction key information receives the direction key event, run a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, so that the sub-view is scrolled and displayed at a visible position within the operation interface according to the scroll amount; where the scroll amount is calculated based on the visible area of the sub-view within the operation interface and the self-area of the sub-view;

[0014] In response to an enabling operation of a pointing function, send cursor position information to the display device through the communication unit to instruct the display device to distribute a hovering event after receiving the position information, and when the sub-view matching the position information receives the hovering event, end the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen to maintain the sub-view not being fully displayed in the operation interface.

[0015] Technical effects: Some embodiments provide a remote control device that has direction buttons and a pointing function. In response to a trigger operation of the direction buttons, the remote control device sends direction button information to a display device to instruct the display device to distribute a direction button event. When a sub-view that matches the direction button information receives the direction button event, a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is run. In this way, the sub-view is scrolled and displayed within the operation interface according to the scroll amount. Moreover, since only one direction button event can be received after a single operation of the direction button, other sub-views will not continue to scroll onto the screen after the program runs. In response to the activation operation of the pointing function, the remote control device sends the position information of the cursor to the display device to instruct the display device to distribute a hover event. When a sub-view that matches the position information receives the hover event, the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is terminated. In this way, even if the sub-view continuously receives the hover event of the cursor, since the program is terminated, the sub-view is prevented from scrolling onto the screen. Therefore, it is possible to maintain the sub-view from being fully displayed in the operation interface. At the same time, other sub-views cannot receive the hover event, blocking the scrolling of other sub-views. When the remote control device points to the edge of the operation interface, continuous scrolling of the view is avoided, enhancing the user experience.

[0016] In a third aspect, some embodiments further provide a view display method, which is applied to the display device provided in the first aspect. The display device includes: a display, a communication module, and a controller. The method includes:

[0017] Present an operation interface including a list view on the display, where the list view includes at least one sub-view that is not fully displayed in the operation interface;

[0018] When a sub-view receives a direction button event, run a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, so that the sub-view is scrolled and displayed at a visible position within the operation interface according to the scroll amount; wherein, the scroll amount is calculated based on the visible area of the sub-view within the operation interface and the self-area of the sub-view;

[0019] When a sub-view receives a hover event of the cursor, terminate the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen to maintain the sub-view from being fully displayed in the operation interface.

[0020] Technical effects: Some embodiments provide a view display method. An operation interface including a list view is presented on a display. The list view includes at least one sub-view that is not fully displayed on the operation interface. When the sub-view receives a direction key event, a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is run. In this way, the sub-view is scrolled and displayed at a visible position within the operation interface according to the scroll amount. And, since only one direction key event can be received after a single operation of the direction key, the program will not cause other sub-views to continuously scroll to the screen after running. When the sub-view receives a cursor hovering event, the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is ended. In this way, even if the sub-view continuously receives a cursor hovering event, since the program is ended, the sub-view is prevented from scrolling to the screen. Therefore, it is possible to maintain the sub-view not fully displayed on the operation interface. At the same time, other sub-views cannot receive the hovering event and the scrolling of other sub-views is blocked. When the remote control device points to the edge of the operation interface, view continuous scrolling is avoided, improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0022] Figure 1 Schematic diagram of an operation scenario between a display device and a control device provided by some embodiments of the present application;

[0023] Figure 2 Schematic diagram of the hardware configuration of a display device provided by some embodiments of the present application;

[0024] Figure 3 Schematic diagram of the hardware configuration of a control device provided by some embodiments of the present application;

[0025] Figure 4 Schematic diagram of the software configuration of a display device provided by some embodiments of the present application;

[0026] Figure 5 Schematic diagram of the interaction between a pointing remote control and a display device provided by some embodiments of the present application Figure 1 ;

[0027] Figure 6 Schematic diagram of the interaction between a pointing remote control and a display device provided by some embodiments of the present application Figure 2 ;

[0028] Figure 7 Schematic diagram of interaction between a pointing remote control and a display device provided in some embodiments of the present application Figure 3 ;

[0029] Figure 8 Schematic diagram of interaction between a pointing remote control and a display device provided in some embodiments of the present application Figure 4 ;

[0030] Figure 9 Schematic diagram of interaction between a pointing remote control and a display device provided in some embodiments of the present application Figure 5 ;

[0031] Figure 10 Schematic diagram of interaction between a pointing remote control and a display device provided in some embodiments of the present application Figure 6 ;

[0032] Figure 11 Schematic diagram of interaction between a pointing remote control and a display device provided in some embodiments of the present application Figure 7 ;

[0033] Figure 12 Schematic diagram of interaction between a pointing remote control and a display device provided in some embodiments of the present application Figure 8 ;

[0034] Figure 13 Flow schematic diagram of a view display method provided in some embodiments of the present application;

[0035] Figure 14 Schematic diagram showing a list view in an operation interface provided in some embodiments of the present application;

[0036] Figure 15 Schematic diagram of scrolling to a visible position after receiving a direction key event provided in some embodiments of the present application;

[0037] Figure 16 Data interaction schematic diagram of a view display method provided in some embodiments of the present application;

[0038] Figure 17 Schematic diagram of maintaining a sub - view not fully displayed in an operation interface provided in some embodiments of the present application;

[0039] Figure 18 Schematic diagram of maintaining a sub - view not fully displayed in an operation interface provided in some other embodiments of the present application;

[0040] Figure 19 Data interaction schematic diagram of a view display method provided in some other embodiments of the present application;

[0041] Figure 20Schematic diagram of the overall process of the view display method provided by some embodiments of the present application;

[0042] Figure 21 Schematic diagram of the next-level subviews included in the subview provided by some embodiments of the present application;

[0043] Figure 22 Schematic diagram of the next-level subviews included in the subview provided by some other embodiments of the present application;

[0044] Figure 23 Internal structure diagram of the computer device provided by some embodiments of the present application. Detailed implementation manners

[0045] The embodiments will be described in detail below, and the examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following embodiments do not represent all implementation manners consistent with the present application. They are merely examples of systems and methods consistent with some aspects of the present application detailed in the claims.

[0046] It should be noted that the brief description of the terms in the present application is only for the convenience of understanding the implementation manners described next, rather than intending to limit the implementation manners of the present application. Unless otherwise specified, these terms should be understood in their ordinary and common meanings.

[0047] The terms "first", "second", "third", etc. in the specification, claims and the above drawings of the present application are used to distinguish similar or like objects or entities, and do not necessarily mean to limit a specific order or sequence, unless otherwise noted. It should be understood that such terms can be interchanged under appropriate circumstances.

[0048] The terms "comprising" and "having" and any variations thereof are intended to cover but not exclude inclusion. For example, a product or device comprising a series of components does not necessarily have to be limited to all the components clearly listed, but may include other components not clearly listed or inherent to these products or devices.

[0049] The term "module" refers to any known or later-developed hardware, software, firmware, artificial intelligence, fuzzy logic, or a combination of hardware or / and software code that can perform the functions related to the element.

[0050] In the embodiments of the present application, the display device 200 generally refers to a device with the capabilities of displaying images and processing data. For example, the display device 200 includes, but is not limited to, smart TVs, mobile terminals, computers, monitors, advertising screens, wearable devices, virtual reality devices, augmented reality devices, etc. The remote control device refers to a device that controls the display device remotely. As the control device of the display device, the remote control device controls the display device through the movement of the remote control device or the triggering operation of the buttons.

[0051] Figure 1 It is a schematic diagram of the operation scenario between the display device and the control device provided by some embodiments of the present application. As Figure 1 shown, the user can operate the display device 200 through touch operations, the mobile terminal 300, and the control device 100. For example, the control device 100 can be a remote control device, a stylus, a gamepad, etc.

[0052] The mobile terminal 300 can be used as a control device to perform the human-computer interaction between the user and the display device 200. The mobile terminal 300 can also be used as a communication device to establish a communication connection with the display device 200 for data interaction. In some embodiments, software applications can be installed on the mobile terminal 300 and the display device 200, and they can be connected and communicate through network communication protocols to achieve one-to-one control operations and data communication purposes. It is also possible to transmit the audio and video content displayed on the mobile terminal 300 to the display device 200 to achieve the synchronous display function.

[0053] As Figure 1 also shown, the display device 200 also communicates with the server 400 through various communication methods. The display device 200 is allowed to communicate and connect through a local area network (LAN), a wireless local area network (WLAN), and other networks.

[0054] The display device 200 can provide a broadcast receiving TV function, and can also additionally provide a smart network TV function with computer support functions, including but not limited to, network TV, smart TV, Internet Protocol TV (IPTV), etc.

[0055] Figure 2 For some embodiments of the present application Figure 1 is the hardware configuration block diagram of the display device 200 in

[0056] In some embodiments, the display device 200 may include at least one of a tuner demodulator 210, a communication device 220, a detector 230, a device interface 240, a controller 250, a display 260, an audio output device 270, a memory, a power supply, and a user input interface.

[0057] In some embodiments, the detector 230 is configured to collect signals of the external environment or for external interaction. For example, the detector 230 includes a light receiver, a sensor for collecting ambient light intensity; or, the detector 230 includes an image collector, such as a camera, which can be used to collect external environment scenes, user attributes or user interaction gestures. Alternatively, the detector 230 includes a sound collector, such as a microphone, etc., for receiving external sounds.

[0058] In some embodiments, the display 260 includes a display function component for presenting a picture and a driving component for driving image display. The display 260 is configured to receive an image signal output from the controller 250 for display. For example, the display 260 can be used to display video content, image content, components of a menu manipulation interface, and a user manipulation UI interface, etc.

[0059] In some embodiments, the communication device 220 is a component for communicating with an external device or server 400 according to various communication protocol types. The display device 200 may be provided with a plurality of communication devices 220 according to different supported communication methods. For example, when the display device 200 supports wireless network communication, the display device 200 may be provided with a communication device 220 including a WiFi function. When the display device 200 supports Bluetooth connection communication, the display device 200 needs to be provided with a communication device 220 including a Bluetooth function. When the display device 200 supports ultra-wideband connection communication (UWB, Ultra-Wideband), the display device 200 needs to be provided with a communication device 220 including a UWB antenna array.

[0060] The communication device 220 can enable the display device 200 to communicate with an external device or server 400 through a wireless or wired connection. Among them, the wired connection can connect the display device 200 to an external device through components such as a data cable and an interface. The wireless connection can connect the display device 200 to an external device through a wireless signal or a wireless network. The display device 200 can directly establish a connection relationship with an external device, or indirectly establish a connection relationship through a gateway, a router, a connection device, etc.

[0061] In some embodiments, the controller 250 may include at least one of a central processing unit, a video processor, an audio processor, a graphics processor, and a power processor, and first to n interfaces for input / output. The controller 250 controls the operation of the display device and responds to user operations through various software control programs stored in the memory. The controller 250 controls the overall operation of the display device 200.

[0062] In some embodiments, the controller 250 and the tuner-demodulator 210 may be located in different separate devices, that is, the tuner-demodulator 210 may also be located in an external device of the main device where the controller 250 is located, such as an external set-top box.

[0063] In some embodiments, the user may input a user command through a graphical user interface (GUI) displayed on the display 260 , and the user input interface receives the user input command through the graphical user interface (GUI).

[0064] In some embodiments, the audio output device 270 may be a local speaker of the display device 200, or may be an external audio output device of the display device 200. In particular, for the external audio output device of the display device 200, the display device 200 may also be provided with an external audio output terminal, and the audio output device may be connected to the display device 200 through the external audio output terminal to output the sound of the display device 200.

[0065] In some embodiments, the user input interface 280 may be used to receive instructions from a user.

[0066] Figure 3 Some embodiments of the present application provide Figure 1 The hardware configuration diagram of the control device in the figure. Figure 3 As shown, the control device 100 may include: a controller 110, a communication interface 130, a user input / output interface, a memory, and a power supply. Exemplarily, the control device 100 may be a remote control device.

[0067] The control device 100 is configured to control the display device 200 , and can receive user input operation instructions, and convert the operation instructions into instructions that the display device 200 can recognize and respond to, playing the role of an interactive intermediary between the user and the display device 200 .

[0068] In some embodiments, the control device 100 may be a smart device, for example, the control device 100 may be installed with various applications for controlling the display device 200 according to user needs.

[0069] In some embodiments, Figure 1 As shown, the mobile terminal 300 or other intelligent electronic devices can play a similar function as the control device 100 after installing the application for controlling the display device 200 .

[0070] The controller 110 includes a processor 112, a RAM 113, a ROM 114, a communication interface 130, and a communication bus. The controller 110 is used to control the operation and operation of the control device 100, as well as the communication and cooperation between the internal components and the external and internal data processing functions.

[0071] Under the control of the controller 110, the communication interface 130 enables the communication of control signals and data signals with the display device 200. The communication interface 130 may include at least one of other near-field communication modules such as a WiFi chip 131, a Bluetooth module 132, an NFC module 133, etc.

[0072] A user input / output interface 140, where the input interface includes at least one of a microphone 141, a touchpad 142, a sensor 143, a button 144, and other input interfaces.

[0073] In some embodiments, the control device 100 includes at least one of the communication interface 130 and the input / output interface 140. The communication interface 130 configured in the control device 100, such as modules like WiFi, Bluetooth, NFC, UWB, etc., can encode user input instructions through the WiFi protocol, or the Bluetooth protocol, the NFC protocol, or the UWB protocol and send them to the display device 200. Among them, encoding the user input instructions through the UWB protocol and sending them to the display device 200 can achieve the control of the pointing function.

[0074] A memory 190, which is used to store various operating programs, data, and applications for driving and controlling the control device 100 under the control of the controller. The memory 190 can store various control signal instructions input by the user.

[0075] A power supply 180, which is used to provide operating power support for each component of the control device 100 under the control of the controller.

[0076] To perform user interaction, in some embodiments, the display device 200 may run an operating system. The operating system is a computer program for managing and controlling the hardware resources and software resources in the display device 200. The operating system can (control the display device) provide a user interface, allowing the user to interact with the display device 200 and support the running of various application programs.

[0077] It should be noted that the operating system may be a native operating system based on a specific operating platform, or a third-party operating system deeply customized based on a specific operating platform, or an independent operating system specially developed for the display device.

[0078] The operating system can be divided into different modules or levels according to the functions implemented. For example, as Figure 4 shown, in some embodiments, the system is divided into four layers, from top to bottom are the application layer (abbreviation "application layer"), the application framework layer (abbreviation "framework layer"), the system library layer, and the kernel layer.

[0079] In some embodiments, the application layer is used to provide services and interfaces for applications so that the display device 200 can run the applications and interact with users based on the applications. At least one application can run in the application layer. These applications can be window programs, system setting programs, clock programs, etc. that come with the operating system; they can also be applications developed by third-party developers. In specific implementations, the application packages in the application layer are not limited to the above examples.

[0080] The framework layer provides application programming interfaces (APIs) and programming frameworks for applications. The application framework layer includes some predefined functions. The application framework layer is equivalent to a processing center that determines the actions of the applications in the application layer. Through the API interface, an application can access the resources in the system and obtain the services of the system during execution.

[0081] As Figure 4 shown, in the embodiment of the present application, the application framework layer includes a view system, managers, content providers, etc. Among them, the view system can design and implement the interfaces and interactions of applications. The view system includes lists, grids, text boxes, buttons, etc. The managers include at least one of the following modules: The activity manager is used to interact with all the activities running in the system; the location manager is used to provide access to the system location service for system services or applications; the package manager is used to retrieve various information related to the application packages currently installed on the device; the notification manager is used to control the display and clearing of notification messages; the window manager is used to manage the icons, windows, toolbars, wallpapers, and desktop widgets on the user interface.

[0082] In some embodiments, the activity manager is used to manage the life cycles of various applications and the usual navigation back functions, such as controlling the exit, opening, and backward movement of applications. The window manager is used to manage all window programs, such as obtaining the size of the display screen, determining whether there is a status bar, locking the screen, capturing the screen, and controlling the changes of the display window. For example, shrinking the display window, jittering the display, and distorting the display.

[0083] In some embodiments, the system runtime library layer can provide support for the framework layer. When the framework layer is used, the operating system will run the instruction libraries included in the system runtime library layer, such as C / C++ instruction libraries, to implement the functions that the framework layer is intended to achieve.

[0084] In some embodiments, the kernel layer is a functional layer between the hardware and software of the display device 200. The kernel layer can implement functions such as hardware abstraction, multitasking, and memory management. For example, as Figure 4 shown, hardware drivers can be configured in the kernel layer. The drivers included in the kernel layer can be at least one of the following drivers: audio driver, display driver, Bluetooth driver, camera driver, WIFI driver, USB driver, HDMI driver, sensor drivers (such as fingerprint sensors, temperature sensors, pressure sensors, etc.), and power drivers, etc.

[0085] It should be noted that the above examples are only a simple division of the functions of the operating system and do not limit the specific form of the operating system of the display device 200 in the embodiments of the present application. Depending on factors such as the functions of the display device and the type of the operating system, the number of levels and the specific level types included in the operating system can be in other forms.

[0086] In some embodiments, a display device is provided. The display device includes: a display configured to display a user interface, where the user interface includes at least one control; the user interface also has a cursor, and the position of the cursor on the user interface is determined by the position pointed to by the remote control in three-dimensional space.

[0087] Optionally, the user can start the display device through voice, remote control, or the switch of the TV device. After the display device is started, the user interface corresponding to the home page is displayed through the display. The user can switch to other user interfaces through voice or remote control, such as: the user interface corresponding to the TV drama label, the user interface corresponding to the movie label, the user interface corresponding to a certain page provided by a certain application, etc. The embodiments of the present application do not limit this.

[0088] Optionally, among all the user interfaces displayed by the display, some user interfaces contain controls, and some user interfaces may not contain controls. The solution provided by the embodiments of the present application is directed to the user interfaces that contain controls. The number of controls on the user interfaces that contain controls may be only one or may be more than one. The embodiments of the present application do not limit this.

[0089] Optionally, the remote control used in conjunction with the display device can be a remote control with a pointing function, hereinafter simply referred to as a pointing remote control. When the pointing function is enabled, a cursor is also present on the user interface displayed on the display. The position of the cursor on the user interface is determined by the position pointed to by the pointing remote control in three-dimensional space. In the embodiments of the present application, the position pointed to by the pointing remote control in three-dimensional space is also referred to as the position data of the pointing remote control in three-dimensional space. The specific implementation process of determining the position of the cursor on the user interface based on the position data of the pointing remote control is described below.

[0090] The position data of the pointing remote control in three-dimensional space can include: position coordinates and pointing direction. Among them, the position coordinates are the physical position of the pointing remote control relative to the display device (for example, the horizontal distance and vertical height from the display device). The pointing direction is the pointing angle of the pointing remote control (for example, the horizontal angle and vertical angle relative to the display device). The pointing remote control is built-in with a gyroscope for detecting the rotation angle of the remote control and an accelerometer for detecting the moving acceleration of the remote control. Through these sensors, the pointing remote control can determine its own position data in three-dimensional space in real time.

[0091] In some embodiments, after the pointing remote control obtains its own position data in three-dimensional space, it can send this position data to the display device. The display device can perform screen coordinate conversion based on this position data, thereby converting the position data of the pointing remote control in three-dimensional space into the screen coordinate system. The obtained screen coordinates can be used as the position of the cursor on the user interface, and the cursor is drawn at this position, thereby displaying the cursor.

[0092] In some embodiments, the pointing remote control includes a coordinate conversion module. After the pointing remote control obtains its own position data in three-dimensional space, it can input this position data into the coordinate conversion module. The coordinate conversion module can perform screen coordinate conversion based on this position data, thereby converting this position data into the screen coordinate system to obtain screen coordinates. These screen coordinates can be used as the position of the cursor on the user interface, and the position of the cursor on the user interface is sent to the display device. After the display device receives the position of the cursor on the user interface, it draws the cursor at this position, thereby displaying the cursor. Exemplarily, the position of the cursor on the user interface is the coordinate (a, b), and the display device draws the cursor at the position with the coordinate (a, b) on the user interface, thereby displaying the cursor.

[0093] Exemplarily, refer to Figure 5As shown, when the position data of the pointing remote control in the three-dimensional space is A, the position of the cursor on the user interface is the coordinate (a1, b1). When the position data of the pointing remote control in the three-dimensional space is B, the position of the cursor on the user interface is the coordinate (a2, b2). When the position data of the pointing remote control in the three-dimensional space is C, the screen coordinates calculated by the above method exceed the screen range, and the display device no longer draws the cursor. Therefore, the cursor disappears.

[0094] See Figure 6 As shown, the pointing remote control supports single-click. When the cursor hovers over a certain control, the user can press the touch area (confirmation key) on the pointing remote control, and the display device executes the corresponding logic in response to this operation. Here, the control can be a card, button, input box, radio button, switch, dialog box, checkbox, slider, play progress bar, scroll bar, drop-down menu, label, list, etc. The embodiments of the present application do not make limitations in this regard.

[0095] See Figure 7 As shown, the pointing remote control supports selection. When there are multiple options and their corresponding selection boxes displayed on the user interface, if the user wants to select the first option and the third option, the user can first control the cursor to hover over the selection box corresponding to the first option and press the touch area on the pointing remote control. At this time, the first option is selected; then, the user can control the cursor to hover over the selection box corresponding to the third option and press the touch area on the pointing remote control. At this time, the third option is selected, thus completing the selection.

[0096] See Figure 8 As shown, the pointing remote control supports drag-and-select multiple. When there are multiple options and their corresponding selection boxes displayed on the user interface, if the user wants to select all options, the user can control the cursor to hover at any position in the upper area of the first option, press the touch area on the pointing remote control and drag down until the cursor moves to the lower area of the last option. At this time, all options are selected, thus completing the drag-and-select multiple.

[0097] See Figure 9 As shown, the pointing remote control supports dragging. When a video is being played on the user interface and a play progress bar is displayed, the user can control the cursor to hover at a certain position on the play progress bar, and then press the touch area on the pointing remote control. The video played on the user interface will fast forward or rewind to the video frame corresponding to this position, thus completing the dragging of the play progress. The play progress bar in this example is only an example. Controls that support dragging also include sliders, scroll bars, labels, cards, lists, etc. The embodiments of the present application do not make limitations in this regard.

[0098] See Figure 10As shown, the pointing remote control supports swiping. When there is a cursor displayed on the user interface, the user can swipe up, down, left, or right on the touch area of the pointing remote control, and the display device will execute the corresponding responses to these swipes.

[0099] See Figure 11 As shown, the pointing remote control supports continuous swiping. When there is a cursor displayed on the user interface, the user can continuously swipe up, down, left, or right on the touch area of the pointing remote control, and the display device will execute the corresponding responses to these continuous swipes and display a damping swipe effect on the user interface. Figure 11 Figure for continuous upward swiping.

[0100] See Figure 12 As shown, the pointing remote control supports continuous reverse swiping. When there is a cursor displayed on the user interface, the user can first swipe in one direction and then in the opposite direction on the touch area of the pointing remote control, and the display device will execute the corresponding responses to the continuous reverse swiping and display a damping swipe effect on the user interface. Figure 12 Figure for first swiping up and then swiping down.

[0101] With the rapid development of the functions of display devices, the operation interface has become increasingly complex. Traditional remote control devices are operated through buttons, which are cumbersome and have low interaction efficiency. As a result, remote control devices with pointing functions have emerged. The remote control device with a pointing function points to the operation interface of the display device, and a cursor is displayed at the pointing position of the operation interface. When the remote control device points to the edge of the operation interface, if the view at the pointing position is not fully displayed, the system will scroll the view to the visible position of the operation interface. However, after the view scrolls out, the view at the pointing position will be updated to the next view. Similarly, the system will continue to scroll the next view to the visible position of the operation interface, and so on, resulting in continuous scrolling of other unshown views into the operation interface. This behavior of continuous scrolling of other unshown views when the remote control device points to a view at the edge of the operation interface leads to a poor user experience. Therefore, there is an urgent need for a display device, a remote control device, and a view display method that can avoid continuous scrolling of views when the remote control device points to the edge of the operation interface and improve the user experience.

[0102] Based on this, embodiments of the present application propose a display device, a remote control device, and a view display method. An operation interface including a list view is presented on a display. The list view includes at least one sub-view that is not fully displayed in the operation interface. When the sub-view receives a direction key event, a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is run. In this way, the sub-view is scrolled and displayed at a visible position within the operation interface according to the scroll amount. Moreover, since only one direction key event can be received after a single operation of the direction key, the program will not cause other sub-views to continuously scroll onto the screen after running; when the sub-view receives a cursor hover event, the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is terminated. In this way, even if the sub-view continuously receives the cursor hover event, since the program is terminated, the sub-view is prevented from scrolling onto the screen. Therefore, it is possible to maintain the sub-view not being fully displayed in the operation interface. At the same time, other sub-views cannot receive the hover event and the scrolling of other sub-views is blocked, so that when the remote control device points to the edge of the operation interface, continuous view scrolling is avoided, enhancing the user experience.

[0103] In an exemplary embodiment, as Figure 13 shown, a view display method is provided. Taking the method applied to the Figure 1 display device 200 as an example for illustration, it includes the following steps 1302 to step 1306. Among them:

[0104] Step 1302, present an operation interface including a list view on the display. The list view includes at least one sub-view that is not fully displayed in the operation interface.

[0105] Among them, the operation interface refers to the interface displayed on the display. In a scenario where a remote control device is used to control the operation interface, there is a cursor in the operation interface, and the position of the cursor on the operation interface is determined by the position pointed to by the remote control device in three-dimensional space.

[0106] The list view refers to a control for displaying a scrolling list. The list view includes at least one sub-view, and each sub-view is an item in the list. At least one sub-view in the list control is displayed by scrolling the screen. Exemplarily, the list view can be a RecyclerView.

[0107] Since the number of sub-views in the list view is different, the operation interface may fully display all sub-views in the list view at one time, or may display some sub-views in the list view at a single time. At least one other sub-view that is not fully displayed is displayed by scrolling the screen.

[0108] As Figure 14The figure shows a schematic diagram of a list view displayed in an operation interface in some embodiments. The list view is shown on the left side of the operation interface. Some sub-views in the list view are fully displayed within the operation interface. At the same time, it also includes at least one sub-view that is not fully displayed within the operation interface. For example, the sub-views corresponding to "test video source" and "Pictures". It can also be seen from the figure that the sub-views that are not fully displayed within the operation interface are often at the edge of the operation interface. Exemplarily, they can be at the upper edge, lower edge, left edge, or right edge of the operation interface. It can be understood that the sub-views at the edge of the operation interface can be fully displayed or not fully displayed. Among them, the thumbnail of the sub-view for drawing the focus style is shown in the right area of the operation interface.

[0109] Step 1304, when the sub-view receives a direction key event, run a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, so that the sub-view scrolls and is displayed at a visible position within the operation interface according to the scrolling amount; wherein, the scrolling amount is calculated based on the visible area of the sub-view within the operation interface and the self area of the sub-view.

[0110] Among them, the remote control device may include direction keys, which are used to perform selection operations in multiple directions on the content in the operation interface. Exemplarily, the direction keys at least include keys such as up, down, left, and right. Among them, the remote control device may only have key functions, or may also have both key functions and pointing functions.

[0111] The direction key event refers to an event generated by the display device after receiving the direction key information sent by the remote control device. Exemplarily, the direction key event at least includes an upward event, a downward event, a leftward event, a rightward event, etc. In some embodiments, the direction key event is distributed by the system framework layer of the display device, and each view listens for the events distributed by the system service layer.

[0112] The rectangular area refers to the area occupied by the sub-view on the screen as defined during design, that is, the self area of the sub-view. Since the sub-view is not fully displayed within the operation interface, the rectangular area includes a visible area and an invisible area. The visible position refers to the position that can be seen by the user within the operation interface.

[0113] When a sub - view receives a direction key event, running a program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen refers to a program in a display device. Among them, the program may include at least one function, and running the program means executing at least one function under the program. After the program runs, the rectangular area of the sub - view is scrolled and displayed at a visible position on the operation interface. Exemplarily, at least one function may include the requestChildRectangleOnScreen function of the RecyclerView layout manager.

[0114] The visible area refers to the area of the sub - view displayed within the operation interface, and the range of the visible area can be determined by the width and height of the visible area. The self - area refers to the range occupied on the screen as defined for the sub - view during design, and the self - area can be determined by the width and height of the sub - view.

[0115] The scroll amount indicates the size of the area scrolled from an invisible position on the screen to a visible position. The scroll amount can be characterized by width and height, and can also be characterized by area.

[0116] In some embodiments, the controller determines the scroll amount according to the difference between the area of the visible area and the area of the self - area. Exemplarily, the scroll amount can be the difference in area plus the product of the inner margin (padding) and the width of the sub - view, where the height of the inner margin is known. In some embodiments, the controller determines the scroll amount according to the difference between the height of the visible area and the height of the self - area. Exemplarily, the scroll amount can be the difference in height plus the inner margin, where the height of the inner margin is known. Since the scroll amount is greater than the difference between the area of the visible area and the area of the self - area in the sub - view, or greater than the difference in height, after the sub - view is scrolled and displayed according to the scroll amount, it can be fully displayed at the visible position and display a partial view of the next sub - view.

[0117] In some other embodiments, the scroll amount is equal to the difference between the area of the visible area and the area of the self - area in the sub - view, or equal to the difference in height. Therefore, after the sub - view is scrolled and displayed according to the scroll amount, it can be fully displayed at the visible position and does not display a partial view of the next sub - view.

[0118] As Figure 15 shown is a schematic diagram of scrolling to a visible position after receiving a direction key event in some embodiments. A list view is displayed in the left - hand area of the operation interface. After the sub - view that is not fully displayed receives a direction key event, it scrolls to a visible position within the operation interface and is fully displayed at the visible position. For example, the control corresponding to "**File (21)". Additionally, referring to Figure 15After the sub - view scrolls to a visible position within the operation interface, the controller draws a focus style for the sub - view. Among them, the thumbnail of the sub - view with the focus style drawn is displayed in the right - hand area of the operation interface.

[0119] In some embodiments, the remote control device responds to the triggering operation of the direction key, sends direction key information to the display device. After receiving the direction key information, the display device distributes the direction key event. When the sub - view that matches the direction key information receives the direction key event, a program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen is run, so that the sub - view is scrolled and displayed at a visible position within the operation interface according to the scroll amount. Among them, for a remote control device with a pointing function, when the sub - view receives the direction key event, the program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen can be run, and the pointing function of the corresponding remote control device can be in a closed state or an open state.

[0120] Step 1306, when the sub - view receives the hover event of the cursor, end running the program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen, so as to keep the sub - view not fully displayed in the operation interface.

[0121] Among them, the position of the cursor in the operation interface is determined by the position pointed to by the remote control device in three - dimensional space.

[0122] The hover event refers to an event generated by the display device after detecting that the pointing function of the remote control device is turned on. Exemplarily, the system service layer of the display device distributes the hover event, and each view in the display device listens to the event distributed by the system service layer. When the sub - view receives the hover event of the cursor, it indicates that the remote control device points to this sub - view in the operation interface in three - dimensional space.

[0123] The program that ends running when the sub - view receives the hover event of the cursor is the program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen. Since the sub - view is not fully displayed in the operation interface, after receiving the hover event, the above - mentioned program ends running, and the sub - view will maintain its display state in the operation interface, that is, it will remain not fully displayed in the operation interface.

[0124] Exemplarily, each sub-view in the list view registers a function for listening to events sent from the upper layer. When an incomplete sub-view listens to a hover event through the listening function, a hover attribute and a focus attribute are added to the sub-view; before ending the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, it is determined whether the sub-view has a hover attribute. If the sub-view has a hover attribute, the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is ended to keep the sub-view not fully displayed on the operation interface; correspondingly, if the sub-view does not have a hover attribute, it indicates that the reason for the sub-view to obtain focus may be receiving a direction key event, and the controller runs the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, so that the sub-view scrolls and is displayed at a visible position within the operation interface according to the scroll amount.

[0125] In some embodiments, when a fully displayed sub-view listens to a hover event, since the sub-control is fully displayed, therefore, ending the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen can keep the sub-view fully displayed at a visible position on the operation interface.

[0126] Such as Figure 16The following shows a schematic diagram of data interaction for the view display method in some embodiments. For the RecyclerView scenario, in response to the enabling operation of the pointing function of the remote control device, the system framework layer of the display device distributes a hover event based on the position information of the cursor sent by the remote control device; each sub-view (View) in the list view (RecyclerView) registers a function for listening to events sent from the upper layer. When any sub-view listens to the hover event, the sub-view is added with a hover attribute, and the requestFocus function is called and executed; among them, the requestFocus function is used to add a focus attribute to the sub-view and call the requestChildFocus function of the list view; in the requestChildFocus function, the requestChildRectangleOnScreen function of the layout manager (LayoutManager) is called. Among them, in the embodiments of the present application, the requestChildRectangleOnScreen function can be directly overridden in the custom layout manager to add a judgment on the hover attribute. When the sub-view has a hover attribute, the overridden requestChildRectangleOnScreen function directly returns false to keep the sub-view from being fully displayed on the operation interface; when the sub-view does not have a hover attribute, it is determined whether the sub-view is fully displayed on the operation interface. If it is not fully displayed, the un-overridden function super.requestChildRectangleOnScreen is run to make the sub-view scroll and be displayed at the visible position within the operation interface according to the scroll amount; if it is fully displayed, the overridden requestChildRectangleOnScreen function directly returns false to keep the sub-view fully displayed on the operation interface.

[0127] As Figure 17 shown, the following is a schematic diagram of keeping a sub-view from being fully displayed on the operation interface in some embodiments. As Figure 18 shown, the following is a schematic diagram of keeping a sub-view from being fully displayed on the operation interface in some other embodiments. Referring to Figure 17 , the partially displayed sub-view is at the upper edge of the operation interface. When the sub-view receives the hover event of the cursor, the program for requesting to scroll the rectangular area of the sub-view to the visible position on the screen ends, keeping the sub-view from being fully displayed on the operation interface, and a focus style, such as a focus box, is drawn for the sub-view. Referring to Figure 18 , the partially displayed sub-view is at the lower edge of the operation interface. When the sub-view receives the hover event of the cursor, the program for requesting to scroll the rectangular area of the sub-view to the visible position on the screen ends, keeping the sub-view from being fully displayed on the operation interface, and a focus style is drawn for the sub-view.

[0128] In the above view display method, an operation interface including a list view is presented on a display. The list view includes at least one sub - view that is not fully displayed in the operation interface. When the sub - view receives a direction key event, a program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen is run. In this way, the sub - view scrolls and is displayed at a visible position within the operation interface according to the scroll amount. And since only one direction key event can be received after a single operation of the direction key, the program will not cause other sub - views to continuously scroll onto the screen after running. When the sub - view receives a cursor hover event, the program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen is ended. In this way, even if the sub - view continuously receives a cursor hover event, since the program is ended, the sub - view is prevented from scrolling onto the screen. Therefore, it is possible to maintain the sub - view not fully displayed in the operation interface. At the same time, other sub - views cannot receive the hover event and the scrolling of other sub - views is blocked, so that when the remote control device points to the edge of the operation interface, continuous view scrolling is avoided, improving the user experience.

[0129] In an exemplary embodiment, after ending the program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen, it further includes: when the sub - view receives a direction key event, if the sub - view is the first view or the last view in the list view, run the program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen, so that the sub - view scrolls and is displayed at a visible position within the operation interface according to the scroll amount.

[0130] Among them, from Figure 17 and Figure 18 it can be seen that after the sub - view receives a hover event, the scrolling behavior of the sub - view is blocked and the display state of the sub - view in the operation interface is maintained. However, when the sub - view is the last view in the list view and the direction key event received by the sub - view is a down event, since no next sub - view can be found in the list view, the sub - view still has the hover attribute, thus continuing to block the scrolling behavior of the sub - view. Therefore, the last view will remain not fully displayed in the operation interface and cannot scroll to a visible position even when receiving a down event. Similarly, when the sub - view is the first view in the list view and receives an up event, the first view still remains not fully displayed in the operation interface.

[0131] Based on this, in the embodiment of the present application, when the sub-view receives the cursor hovering event and after the program for requesting to scroll the rectangular area of the sub-view to the visible position on the screen ends, when the sub-view receives the direction key event, if the sub-view is the first view or the last view in the list view, the program for requesting to scroll the rectangular area of the sub-view to the visible position on the screen is run, so that the sub-view scrolls and is displayed at the visible position within the operation interface according to the scroll amount.

[0132] In this embodiment, after the scrolling behavior of the sub-view is blocked when the sub-view receives the cursor hovering event, when the first view or the last view in the list view receives the direction key event, the program for requesting to scroll the rectangular area of the sub-view to the visible position on the screen is run, so that the sub-view scrolls and is displayed at the visible position within the operation interface according to the scroll amount, avoiding the problem that the first or last view cannot be fully displayed due to the blocked scrolling, which is beneficial to improving the user experience.

[0133] In an exemplary embodiment, if the sub-view is the first view or the last view in the list view, running the program for requesting to scroll the rectangular area of the sub-view to the visible position on the screen includes: if the type of the list view is a vertical list type, the sub-view is the first view in the list view, and the direction key event is not a downward event, or the type of the list view is a vertical list type, the sub-view is the last view in the list view, and the direction key event is not an upward event, or the type of the list view is a horizontal list type, the sub-view is the first view in the list view, and the direction key event is not a rightward event, or the type of the list view is a horizontal list type, the sub-view is the last view in the list view, and the direction key event is not a leftward event, then run the program for requesting to scroll the rectangular area of the sub-view to the visible position on the screen.

[0134] Among them, according to the view scrolling direction, the types of list views can be divided into vertical list types and horizontal list types.

[0135] When the scrolling of a partially displayed sub - view is blocked and a direction key event is received, for a list view of the vertical list type, if the sub - view is the first view in the list view and the direction key event is not a downward event, or if the sub - view is the last view in the list view and the direction key event is not an upward event, then run a program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen, so as to scroll and display the sub - view at a visible position within the operation interface according to the scrolling amount; for a list view of the horizontal list type, if the sub - view is the first view in the list view and the direction key event is not a right - hand event, or if the sub - view is the first view in the list view and the direction key event is not a right - hand event, then run a program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen, so as to scroll and display the sub - view at a visible position within the operation interface according to the scrolling amount. In this way, the first or last view that is not fully displayed in the list view can be scrolled to a visible position, improving the user experience.

[0136] In some embodiments, for a list view of the vertical list type, if the sub - view is the first view in the list view and the direction key event is a downward event, or if the sub - view is the last view in the list view and the direction key event is an upward event, since the direction key event points to another view that is fully displayed in the list view, therefore, end the running of the program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen, in order to maintain the full display of the sub - view within the operation interface. Similarly, for a list view of the horizontal list type, since the direction key event points to another view that is fully displayed in the list view, end the running of the program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen, in order to maintain the full display of the sub - view within the operation interface and improve the user experience.

[0137] Such as Figure 19The figure shows a data interaction schematic diagram of a view display method in some other embodiments. For the RecyclerView scenario, after the program for requesting to scroll the rectangular area of a child view to a visible position on the screen ends, in response to a trigger operation of a direction key on a remote control device, the system framework layer of the display device distributes a direction key event according to the direction key information sent by the remote control device; each child view in the list view registers a function for listening to events sent from the upper layer. When any child view listens to a direction key event, it calls and executes the focusSearch function to find a focus. In the focusSearch function, it calls the overridden onInterceptFocusSearch function of the layout manager. In the overridden onInterceptFocusSearch function, it determines whether the child view meets an additional scrolling condition. The additional scrolling condition includes: 1. For a vertical list type of list view: the child view is the first view in the list view and the direction key event is not a downward event, or the child view is the last view in the list view and the direction key event is not an upward event; 2. For a horizontal list type of list view: the child view is the first view in the list view and the direction key event is not a rightward event, or the type of the list view is a horizontal list type, the child view is the last view in the list view, and the direction key event is not a leftward event. When it is determined that the child view meets the additional scrolling condition, it calls and executes the requestChildRectangleOnScreen function to scroll the child view to a visible position within the operation interface according to the scrolling amount. When it is determined that the child view does not meet the additional scrolling condition, it searches for the next child view in the list view according to the direction key information. If there is a next child view that matches the direction key information, that is, the child view is not the first or last view in the list view, it adds a focus attribute to the next child view and runs the program for requesting to scroll the rectangular area of the child view to a visible position on the screen, so that the child view scrolls and is displayed at a visible position within the operation interface according to the scrolling amount. In some embodiments, the controller draws a focus style for the next child view.

[0138] In this embodiment, when the scrolling of an incompletely displayed child view is blocked and a direction key event is received, by performing scrolling on the child view that meets the additional scrolling condition according to the type of the list view, the sorting of the child view in the list view as the first or last one, and the type of the direction key event, the first or last view in the list view that is incompletely displayed can be scrolled to a visible position, improving the user experience.

[0139] In an exemplary embodiment, the view display method further includes: when a sub-view receives a cursor hovering event, ending the running of a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, and running another program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen; wherein, when there is still a next sub-view in the list view along the scrolling direction, the program, while causing the sub-view to scroll and be displayed at a visible position within the operation interface according to the scrolling amount, displays a partial view of the next sub-view; when there is still a next sub-view in the list view along the scrolling direction, the other program, while causing the sub-view to scroll and be displayed at a visible position within the operation interface according to the scrolling amount, does not display a partial view of the next sub-view.

[0140] Wherein, when a sub-view receives a cursor hovering event, the running of a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is ended, and the sub-view remains not fully displayed within the operation interface. To further improve the user experience, an embodiment of the present application proposes to run another program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen. When there is still a next sub-view in the list view along the scrolling direction, the other program causes the sub-view to scroll and be displayed at a visible position within the operation interface according to the scrolling amount, and does not display a partial view of the next sub-view.

[0141] Wherein, when running the other program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, the scrolling amount may be equal to the area difference between the self-area of the sub-view and the visible area of the sub-view within the operation interface, or equal to the height difference between the self-area of the sub-view and the visible area of the sub-view within the operation interface.

[0142] In this embodiment, when a sub-view receives a cursor hovering event, the running of a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is ended, and another program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is run. In this way, while the sub-view scrolls and is displayed at a visible position within the operation interface according to the scrolling amount, a partial view of the next sub-view is not displayed. Since the next sub-view is not displayed at a visible position within the operation interface, the next sub-view cannot obtain focus, thereby being able to avoid continuous scrolling of the view and improving the user experience.

[0143] In an exemplary embodiment, the view display method further includes: when a sub-view receives a cursor hovering event, obtaining the area ratio of the visible area of the sub-view within the operation interface to the self area of the sub-view; when the area ratio exceeds a preset ratio, running a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, so that the sub-view scrolls and is displayed at the visible position within the operation interface according to the scroll amount; when the area ratio does not exceed the preset ratio, ending the running of the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, so as to keep the sub-view not fully displayed within the operation interface, and drawing a focus style for the sub-view.

[0144] Wherein, when a sub-view receives a cursor hovering event, ending the running of the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, and keeping the sub-view not fully displayed within the operation interface. To further improve the user experience, the embodiment of the present application proposes to determine whether to run the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen according to whether the area ratio of the visible area of the sub-view within the operation interface to the self area of the sub-view exceeds a preset ratio.

[0145] When the area ratio exceeds the preset ratio, it indicates that although the sub-view is not fully displayed within the operation interface, the proportion of the visible area is relatively large. Running the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, so that the sub-view scrolls and is displayed at the visible position within the operation interface according to the scroll amount. In this way, the user can view the sub-view completely, improving the user experience. In some embodiments, a focus style can be drawn for the sub-view.

[0146] When the area ratio does not exceed the preset ratio, it indicates that the proportion of the visible area of the sub-view is relatively small. Ending the running of the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, so as to keep the sub-view not fully displayed within the operation interface, thereby blocking the continuous scrolling of the sub-view and improving the user experience.

[0147] In some embodiments, when the area ratio does not exceed the preset ratio, a focus attribute can be added to the sub-view, so that a focus style can be drawn for the sub-view.

[0148] In some embodiments, the scrolling amount is equal to the area difference plus the product of the inner margin and the width of the sub - view. Therefore, while the sub - view scrolls to the visible position within the operation interface according to the scrolling amount, a partial view of the next sub - view will be displayed. At this time, if the next sub - view receives a hover event, since the partial view of the next sub - view serves as the new visible area and the corresponding area ratio does not exceed the preset ratio, the program for requesting to scroll the rectangular area of the next sub - view to the visible position on the screen is ended. The next sub - view can be maintained without being fully displayed in the operation interface, blocking the continuous scrolling of the sub - views and enhancing the user experience.

[0149] In some embodiments, the height ratio of the visible area of the sub - view within the operation interface to the self - area of the sub - view can also be obtained, and whether to run the program is determined according to the magnitude relationship between the height ratio and the preset ratio.

[0150] In this embodiment, when the sub - view receives the hover event of the cursor, it is determined whether to run the program for requesting to scroll the rectangular area of the sub - view to the visible position on the screen according to whether the area ratio of the visible area of the sub - view within the operation interface to the self - area of the sub - view exceeds the preset ratio. Thus, in the case of a relatively large area, the program is run so that the sub - view scrolls to the visible position within the operation interface according to the scrolling amount, enhancing the user experience; in the case of a relatively small area, the program is ended to maintain the sub - view without being fully displayed in the operation interface, which can block the continuous scrolling of the sub - view and enhance the user experience.

[0151] In an exemplary embodiment, the view display method further includes: when the area ratio does not exceed the preset ratio, ending the program for requesting to scroll the rectangular area of the sub - view to the visible position on the screen to maintain the sub - view without being fully displayed in the operation interface and not drawing a focus style for the sub - view.

[0152] Among them, when the sub - view receives the hover event of the cursor and the area ratio of the visible area of the sub - view within the operation interface to the self - area of the sub - view does not exceed the preset ratio, the focus attribute is not added to the sub - view. The focus attribute may still exist in the previous sub - control that was fully displayed. The program for requesting to scroll the rectangular area of the sub - view to the visible position on the screen is ended to maintain the sub - view without being fully displayed in the operation interface, which can block the continuous scrolling of the sub - view; at the same time, since the sub - view does not have the focus attribute, the controller does not draw a focus style for the sub - view.

[0153] In this embodiment, when the area ratio does not exceed the preset ratio, the focus attribute is not added to the sub-view, so that the focus style is not drawn for the sub-view, and the focus style maintains the original display state. At the same time, the program for requesting to scroll the rectangular area of the sub-view to the visible position on the screen is terminated. In this way, the sub-view remains incompletely displayed on the operation interface, blocking the continuous scrolling behavior of the view and improving the user experience.

[0154] In an exemplary embodiment, before terminating the program for requesting to scroll the rectangular area of the sub-view to the visible position on the screen, it further includes: when the sub-view receives the cursor hovering event, if the sub-view is the first view or the last view in the list view, the program for requesting to scroll the rectangular area of the sub-view to the visible position on the screen is run, so that the sub-view scrolls and is displayed at the visible position within the operation interface according to the scrolling amount; if the sub-view is not the first view in the list view and is not the last view, the program for requesting to scroll the rectangular area of the sub-view to the visible position on the screen is terminated to keep the sub-view incompletely displayed on the operation interface.

[0155] Among them, when the sub-view receives the cursor hovering event, it can be determined whether the sub-view is the first view or the last view in the list view. If it is the first view or the last view in the list view, the program for requesting to scroll the rectangular area of the sub-view to the visible position on the screen is run, so that the sub-view scrolls and is displayed at the visible position within the operation interface according to the scrolling amount. In this way, the first view or the last view in the list view scrolls and is displayed at the visible position within the operation interface. Since there is no next view in the list view that can obtain the focus in the scrolling direction, only this sub-view scrolls and is displayed at the visible position within the operation interface, and there will be no continuous view scrolling behavior. Moreover, the user can view the sub-view completely, improving the user experience.

[0156] If the sub-view is not the first view in the list view and is not the last view, the program for requesting to scroll the rectangular area of the sub-view to the visible position on the screen is terminated to keep the sub-view incompletely displayed on the operation interface. In this way, it is possible to prevent the sub-view and other un-displayed views from scrolling to the visible position on the operation interface, that is, blocking the continuous view scrolling behavior.

[0157] In this embodiment, when the sub-view receives the cursor hovering event, for the first view or the last view in the list view, a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is run. In this way, on the one hand, the first view or the last view in the list view can be scrolled and displayed at a visible position within the operation interface, and there will be no continuous view scrolling behavior. On the other hand, the user can see the sub-view completely, improving the user experience. For views that are not the first view or the last view in the list view, the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is ended. In this way, the continuous view scrolling behavior can be blocked, improving the user experience.

[0158] To illustrate the display device, remote control device, view display method and effects in this solution in detail, the following describes a most detailed embodiment:

[0159] The display device includes: a display, a communication module, and a controller. Among them, the display is configured to display an operation interface, and there is a cursor in the operation interface. The position of the cursor on the operation interface is determined by the position pointed to by the remote control device in the three-dimensional space; the communication module is configured to be connected to the remote control device; and at least one controller, which is connected to the display and the communication module and is configured to execute instructions to enable the display device to execute the view display method.

[0160] The remote control device includes: a communication unit and at least one processor. Among them, it is configured to communicate with the display device, present an operation interface including a list view on the display of the display device, and the list view includes at least one sub-view that is not completely displayed in the operation interface; and at least one processor, which is connected to the communication unit.

[0161] As Figure 20The figure shows a general flowchart of a view display method in some embodiments. Among them, when a sub-view of a display device receives a cursor hovering event, a hovering attribute is added to the sub-view, and a focus attribute is added to the sub-view by calling and executing the requestFocus function. It is determined whether the sub-view has a hovering attribute. If the sub-view has a hovering attribute, the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is ended to keep the sub-view not fully displayed on the operation interface, and a focus style is displayed for the sub-view; if the sub-view does not have a hovering attribute, it is determined whether the sub-view is fully displayed on the operation interface. If it is fully displayed, the sub-view is kept fully displayed on the operation interface, and a focus style is displayed for the sub-view. If it is not fully displayed, the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is run so that the sub-view scrolls and is displayed at a visible position within the operation interface according to the scroll amount; after the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is ended, when the sub-view receives a direction key event, the focusSearch function is called and executed to find the focus, and it is determined whether the sub-control meets the additional scroll condition. If it meets the condition, it is determined whether the sub-view is fully displayed on the operation interface. If it is fully displayed, the next view is searched; if it is not fully displayed, the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is run so that the sub-view scrolls and is displayed at a visible position within the operation interface according to the scroll amount, and then the next view is searched; it is determined whether the next view is searched. If it is searched, the step of adding a focus attribute is continued for the next sub-view. If it is not searched, it is handed over to the parent view for continued search. If it is not searched, the search is terminated and the focus remains unchanged.

[0162] In some embodiments, the sub-view further includes at least one next-level sub-view. Refer to Figure 21 and Figure 22 , each sub-view further includes a delete sub-view, a schedule information sub-view, and an edit sub-view. After each next-level sub-view monitors a hovering event, it has its corresponding focus style. When any next-level sub-view has a focus attribute and monitors a hovering event, the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is ended to keep the sub-view not fully displayed on the operation interface.

[0163] Some embodiments provide a display device. An operation interface including a list view is presented on the display. The list view includes at least one sub-view that is not fully displayed in the operation interface. When the sub-view receives a direction key event, a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is run. In this way, the sub-view is scrolled and displayed at a visible position within the operation interface according to the scroll amount. And since only one direction key event can be received after a single operation of the direction key, the program will not cause other sub-views to continuously scroll onto the screen after running. When the sub-view receives a cursor hovering event, the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen is ended. In this way, even if the sub-view continuously receives a cursor hovering event, since the program is ended, the sub-view is prevented from scrolling onto the screen. Therefore, it is possible to maintain that the sub-view is not fully displayed in the operation interface. At the same time, other sub-views cannot receive the hovering event and the scrolling of other sub-views is blocked, so that when the remote control device points to the edge of the operation interface, continuous scrolling of the view is avoided, improving the user experience.

[0164] It should be understood that although the steps in the flowcharts involved in the above-described embodiments are shown in sequence according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear indication in this article, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-described embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily executed at the same moment, but can be executed at different moments. The execution order of these steps or stages is not necessarily sequential, but can be executed alternately or in turn with at least a part of other steps or steps or stages in other steps.

[0165] In an exemplary embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as Figure 23As shown in the figure. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit, and an input device. Among them, the processor, the memory, and the input / output interface are connected through a system bus, and the communication interface, the display unit, and the input device are connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, near field communication (NFC), or other technologies. When the computer program is executed by the processor, it implements a view display method. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen. The input device of the computer device can be a touch layer covering the display screen, or a button, a trackball, or a touchpad provided on the housing of the computer device, or an external keyboard, touchpad, or mouse, etc.

[0166] Those skilled in the art can understand that Figure 23 the structure shown in the figure is only a block diagram of some structures related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine some components, or have a different component layout.

[0167] In an exemplary embodiment, a computer device is provided, including a memory and a processor. A computer program is stored in the memory, and when the processor executes the computer program, the steps in the above method embodiments are implemented.

[0168] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by the processor, the steps in the above method embodiments are implemented.

[0169] In one embodiment, a computer program product is provided, including a computer program, and when the computer program is executed by the processor, the steps in the above method embodiments are implemented.

[0170] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data need to comply with relevant regulations.

[0171] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, database, or other medium used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The databases involved in the embodiments provided in this application can include at least one of relational databases and non-relational databases. Non-relational databases can include distributed databases based on blockchain, etc., without limitation. The processors involved in the embodiments provided in this application can be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, data processing logics based on quantum computing, artificial intelligence (AI) processors, etc., without limitation.

[0172] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope recorded in this application.

[0173] The above-described embodiments merely represent several implementation manners of this application. The description thereof is relatively specific and detailed, but it should not be construed as a limitation on the patent scope of this application. It should be noted that for those of ordinary skill in the art, without departing from the concept of this application, several modifications and improvements can still be made, and these all belong to the protection scope of this application. Therefore, the protection scope of this application shall be subject to the appended claims.

Claims

1. A display device, characterized in that, Including: A display configured to display an operation interface, where a cursor is present in the operation interface, and the position of the cursor on the operation interface is determined by the position pointed to by a remote control device in three-dimensional space; A communication module configured to connect to the remote control device; And at least one controller, which is connected to the display and the communication module and is configured to execute instructions to cause the display device to: Present an operation interface including a list view on the display, where the list view includes at least one sub-view that is not fully shown in the operation interface; When a direction key event is received by the sub-view, run a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, so that the sub-view scrolls and is displayed at a visible position within the operation interface according to the scroll amount; where the scroll amount is calculated based on the visible area of the sub-view within the operation interface and the area of the sub-view itself; When a hover event of the cursor is received by the sub-view, end running the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen to maintain the sub-view not being fully shown in the operation interface.

2. The display device according to claim 1, wherein After the controller executes the program to end running the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, it is further configured to: When a direction key event is received by the sub-view, if the sub-view is the first view or the last view in the list view, run a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, so that the sub-view scrolls and is displayed at a visible position within the operation interface according to the scroll amount.

3. The display device according to claim 2, wherein The controller's execution of running a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen if the sub-view is the first view or the last view in the list view is configured as: If the type of the list view is a vertical list type, the sub-view is the first view in the list view, and the direction key event is not a downward event, or, The type of the list view is a vertical list type, the sub-view is the last view in the list view, and the direction key event is not an upward event, or, The type of the list view is a horizontal list type, the sub-view is the first view in the list view, and the direction key event is not a rightward event, or, The type of the list view is a horizontal list type, the sub-view is the last view in the list view, and the direction key event is not a leftward event, then run a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen.

4. The display device according to claim 1, wherein The controller is further configured to: When a hover event of the cursor is received by the sub-view, end running the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen and run another program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen; Wherein, when there is a next sub - view of the sub - view in the list view along the scrolling direction, the program, while causing the sub - view to be scrolled and displayed at a visible position within the operation interface according to the scrolling amount, displays a partial view of the next sub - view; when there is a next sub - view of the sub - view in the list view along the scrolling direction, another program, while causing the sub - view to be scrolled and displayed at a visible position within the operation interface according to the scrolling amount, does not display a partial view of the next sub - view.

5. The display device according to claim 1, wherein The controller is further configured to: When the sub - view receives a cursor hovering event, obtain the area ratio between the visible area of the sub - view within the operation interface and the self - area of the sub - view; When the area ratio exceeds a preset ratio, run a program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen, so that the sub - view is scrolled and displayed at a visible position within the operation interface according to the scrolling amount; When the area ratio does not exceed the preset ratio, end the program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen, so as to keep the sub - view not fully displayed within the operation interface and draw a focus style for the sub - view.

6. The display device according to claim 5, wherein, The controller is further configured to: When the area ratio does not exceed the preset ratio, end the program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen, so as to keep the sub - view not fully displayed within the operation interface and not draw a focus style for the sub - view.

7. The display device according to claim 1, wherein Before the controller executes to end the program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen, it is further configured to: When the sub - view receives a cursor hovering event, if the sub - view is the first view or the last view in the list view, run a program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen, so that the sub - view is scrolled and displayed at a visible position within the operation interface according to the scrolling amount; If the sub - view is not the first view in the list view and is not the last view, end the program for requesting to scroll the rectangular area of the sub - view to a visible position on the screen, so as to keep the sub - view not fully displayed within the operation interface.

8. A remote control device, characterized in that, Comprising: A communication unit, configured to communicate with a display device and present an operation interface including a list view on a display of the display device, the list view including at least one sub - view that is not fully displayed within the operation interface; And at least one processor, which is connected to the communication unit and is configured to execute instructions to cause the remote control device to: In response to a triggering operation of a direction key, send direction key information to the display device through the communication unit to instruct the display device to distribute a direction key event after receiving the direction key information, and when the sub-view that matches the direction key information receives the direction key event, run a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, so that the sub-view is scrolled and displayed at a visible position within the operation interface according to the scrolling amount; wherein, the scrolling amount is calculated based on the visible area of the sub-view within the operation interface and the self-area of the sub-view. In response to an enabling operation of a pointing function, send the position information of the cursor to the display device through the communication unit to instruct the display device to distribute a hovering event after receiving the position information, and when the sub-view that matches the position information receives the hovering event, end the running of the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, so as to maintain that the sub-view is not completely displayed within the operation interface.

9. A view display method, characterized in that, Comprising: Present an operation interface including a list view on a display, where the list view includes at least one sub-view that is not completely displayed within the operation interface. When the sub-view receives a direction key event, run a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, so that the sub-view is scrolled and displayed at a visible position within the operation interface according to the scrolling amount; wherein, the scrolling amount is calculated based on the visible area of the sub-view within the operation interface and the self-area of the sub-view. When the sub-view receives a hovering event of the cursor, end the running of the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, so as to maintain that the sub-view is not completely displayed within the operation interface.

10. The method according to claim 9, wherein After ending the running of the program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, further comprising: When the sub-view receives a direction key event, if the sub-view is the first view or the last view in the list view, run a program for requesting to scroll the rectangular area of the sub-view to a visible position on the screen, so that the sub-view is scrolled and displayed at a visible position within the operation interface according to the scrolling amount.

Images