Display device and multi-view touch method

Abstract

The embodiment of the invention provides a display device and a multi-view touch control method, and the method can respond to first touch control data input by a user, and distribute the first touch control data to a first view. Wherein the first touch data is touch data acting on the intersection area of the first view and the second view. If the first touch data comprises the moving event in the target direction, responding to the first touch data based on the first view; and if the first touch data does not include the movement event in the target direction, sending the first touch data to the second view based on the first view, and when the first touch data includes the target feature, responding to the first touch data based on the second view. According to the method, when a plurality of views are overlapped, the view which the touch data expects to act on can be determined according to the event type of the touch data, and the touch data are responded based on the determined view, so that the accuracy of touch interaction operation is improved, 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 and a multi-view touch control method. Background Art

[0002] A display device is an intelligent device that can present a user interface and support user interaction. Taking a smart TV as an example, a smart TV is a TV product based on Internet application technology, with an open operating system and a chip, an open application platform, and can realize two-way human-computer interaction functions, integrating various functions such as audio-visual, entertainment, and data to meet the diverse and personalized needs of users. The display device can also achieve touch interaction operations through an internal or external touch control module.

[0003] To meet the needs of users for quick operations, for a display device that supports touch interaction operations, a quick view including a hidden state and an expanded state can be run, and the quick view supports touch. Users can call out the expanded quick view in the display device through specific touch gestures. For example, the quick view can be a control center view, and users can call out the expanded control center view through touch gestures such as swiping up or down. To enable the quick view to recognize the above touch gestures in real time, the quick view in the hidden state will always display a partial transparent view on the screen to receive touch events input by the user, and the display level of the transparent view is the highest, so as to ensure that users can call out the expanded quick view in any scenario.

[0004] However, there will be an intersection area between the above transparent view and other views. When other views also support touch, the touch made by the user in the intersection area will conflict, making the display device unable to accurately identify which view the touch event acting on the intersection area is for, resulting in a decrease in the accuracy rate of the display device in responding to touch events and affecting the user's interaction experience. Summary of the Invention

[0005] This application provides a display device and a multi-view touch control method to solve the problem that the status bar view in the display device is difficult to control.

[0006] In a first aspect, some embodiments of the present application provide a display device, including a display and a controller. Among them, the display is configured to display a user interface, the user interface includes a first view and a second view, the display level of the first view is higher than that of the second view, and the first view is displayed based on first layout parameters; when the first view is displayed based on the first layout parameters, there is a first intersection area between the first view and the second view, and the first intersection area of the first view is a transparent view; the display is connected to a touch interaction module, and the touch interaction module is used to detect touch data input by the user; the controller is configured to execute the following program steps:

[0007] In response to first touch data input by the user, distribute the first touch data to the first view, where the first touch data is touch data acting on the first intersection area;

[0008] If the first touch data includes a movement event in a target direction, respond to the first touch data based on the first view;

[0009] If the first touch data does not include a movement event in the target direction, send the first touch data from the first view to the second view, and parse the first touch data based on the second view; and, when the first touch data includes a target feature, respond to the first touch data through the second view.

[0010] In a second aspect, some embodiments of the present application further provide a multi-view touch method, which is applied to the display device provided in the first aspect. The display device includes a display and a controller. The display is configured to display a user interface, the user interface includes a first view and a second view, the display level of the first view is higher than that of the second view, and the first view is displayed based on first layout parameters; when the first view is displayed based on the first layout parameters, there is a first intersection area between the first view and the second view, and the first intersection area of the first view is a transparent view; the display is connected to a touch interaction module, and the touch interaction module is used to detect touch data input by the user; the method includes:

[0011] In response to first touch data input by the user, distribute the first touch data to the first view, where the first touch data is touch data acting on the first intersection area;

[0012] If the first touch data includes a movement event in a target direction, respond to the first touch data based on the first view;

[0013] If the first touch data does not include a movement event in the target direction, send the first touch data from the first view to the second view, and parse the first touch data based on the second view; and, when the first touch data includes a target feature, respond to the first touch data through the second view.

[0014] As can be seen from the above technical solutions, for the display device and status bar view provided by some embodiments of the present application, the method can respond to the first touch data input by the user and distribute the first touch data to the first view. Among them, the first touch data is touch data acting on the intersection area of the first view and the second view. If the first touch data includes a movement event in the target direction, respond to the first touch data based on the first view; if the first touch data does not include a movement event in the target direction, send the first touch data from the first view to the second view, then parse the first touch data based on the second view, and when the first touch data includes a target feature, respond to the first touch data based on the second view. The method can determine the view that the touch data is expected to act on according to the event type of the touch data when multiple views overlap, and respond to the touch data based on the determined view, thereby improving the accuracy of touch interaction operations and improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] 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 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 also be obtained based on these drawings.

[0016] Figure 1 It is a schematic diagram of the usage scenario of the display device in some embodiments of the present application;

[0017] Figure 2 It is a block diagram of the hardware configuration of the display device provided by some embodiments of the present application;

[0018] Figure 3 It is a block diagram of the hardware configuration of the control device provided by some embodiments of the present application;

[0019] Figure 4 It is a schematic diagram of the software configuration in the display device provided by some embodiments of the present application;

[0020] Figure 5 It is a schematic diagram of the touch data provided by some embodiments of the present application;

[0021] Figure 6 It is a schematic diagram of the display effect of the control center view provided by some embodiments of the present application;

[0022] Figure 7 Schematic diagram of the display effect of the status bar view provided by some embodiments of the present application;

[0023] Figure 8 Schematic diagram of the relationship between the display levels of each view provided by some embodiments of the present application;

[0024] Figure 9 Schematic diagram of the process of the multi-view touch method provided by some embodiments of the present application;

[0025] Figure 10 Schematic diagram of the touch effect in the first intersection area provided by some embodiments of the present application;

[0026] Figure 11 Schematic diagram of the touch point effect based on the first view responding to the movement event provided by some embodiments of the present application;

[0027] Figure 12 Schematic diagram of the process of the touch point based on the first view responding to the lift event provided by some embodiments of the present application;

[0028] Figure 13 Schematic diagram of the effect of the first view in the hidden state provided by some embodiments of the present application;

[0029] Figure 14 Schematic diagram of the effect of the first view in the expanded state provided by some embodiments of the present application;

[0030] Figure 15a Schematic diagram of a rectangular object provided by some embodiments of the present application;

[0031] Figure 15b Schematic diagram of another rectangular object provided by some embodiments of the present application;

[0032] Figure 16 Schematic diagram of the process based on the second view responding to the fall event provided by some embodiments of the present application;

[0033] Figure 17 Schematic diagram of the principle of marking the view to be responded provided by some embodiments of the present application;

[0034] Figure 18 Schematic diagram of the effect of setting the view to be responded to the pressed state provided by some embodiments of the present application;

[0035] Figure 19 Schematic diagram of the principle of marking the view to be responded according to the rectangular object provided by some embodiments of the present application;

[0036] Figure 20 Schematic diagram of the process based on the second view responding to the lift event touch point provided by some embodiments of the present application;

[0037] Figure 21 Schematic diagram showing the effect of the third view provided for some embodiments of the present application;

[0038] Figure 22 Flow chart showing the response to touch data based on the second view provided for some embodiments of the present application;

[0039] Figure 23 Flow chart showing the response to touch data during cross - region movement provided for some embodiments of the present application. Detailed implementation manners

[0040] 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 only examples of systems and methods consistent with some aspects of the present application detailed in the claims.

[0041] It should be noted that the brief description of the terms in the present application is only for facilitating the understanding of the following described implementation manners, 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.

[0042] The terms "first", "second", "third", etc. in the specification, claims and the above - mentioned 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.

[0043] The terms "comprising" and "having" and any variations thereof are intended to cover but not exclusively include. 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.

[0044] 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 functions related to that element.

[0045] Figure 1 Schematic diagram of the operation scenario between the display device and the control device provided for 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. Among them, the control device 100 can be a remote control, a stylus, etc.

[0046] In some embodiments, the mobile terminal 300 can install software applications with the display device 200 and achieve connection communication through network communication protocols to achieve the purpose of one-to-one control operations and data communication. 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.

[0047] As Figure 1 also shown, the display device 200 also communicates with the server 400 for data communication 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.

[0048] In addition to providing the function of receiving broadcast television, the display device 200 can also additionally provide an intelligent network television function that supports computer functions, including but not limited to, network television, smart television, Internet Protocol Television (IPTV), etc.

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

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

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

[0052] In some embodiments, the display 260 includes a display screen component for presenting a picture, and a driving component for driving image display, which is used to receive the image signal output from the controller, and components for displaying video content, image content, and menu manipulation interfaces, as well as a user manipulation UI interface, etc.

[0053] In some embodiments, the display 260 is connected to the touch interaction module, enabling the display device 200 to support touch interaction operations. The touch interaction module can be an in-built module that forms a touch display screen together with the touch screen. Of course, it can also be an external module. For example, to implement touch interaction operations, for the display device 200 with an in-built touch interaction module, the display 260 can be a touch screen that can receive touch signals input by fingers, contacts, styluses, etc., and execute touch interaction responses according to pre-set interaction strategies.

[0054] For the display device 200 with an external touch interaction module, a terminal, device, or component with touch functionality can be connected through the device interface of the display device 200. For example, a touchpad is connected to the USB or USB-C interface of the display device 200. The touchpad can receive the touch trajectory input by the user in real time and transmit the touch trajectory to the display device 200 through the USB channel. The display device 200 can then execute an interaction response based on the received touch trajectory in combination with a touch application, enabling the display device 200 to support touch interaction operations.

[0055] In some embodiments, the communicator 220 is a component for communicating with external devices or the server 400 according to various communication protocol types.

[0056] In some embodiments, the controller 250 includes a processor, a video processor, an audio processor, a graphics processor, RAM, ROM, and a first interface to an nth interface 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.

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

[0058] In some embodiments, if a user inputs a user command on the graphical user interface (GUI) displayed on the display 260, the user input interface receives the user input command through the graphical user interface (GUI).

[0059] In some embodiments, the user interface 280 is an interface that can be used to receive control inputs.

[0060] Figure 3 For some embodiments provided in this application Figure 1 The hardware configuration block diagram of the control device. As Figure 3As shown, the control device 100 includes a device controller 110, a communication interface 130, a user input / output interface, a memory, and a power supply.

[0061] The control device 100 is configured to control the display device 200, and can receive input operation instructions from the user, and convert the operation instructions into instructions recognizable and responsive by the display device 200, acting as an interaction intermediary between the user and the display device 200.

[0062] In some embodiments, the control device 100 can be an intelligent device. For example, the control device 100 can install various applications for controlling the display device 200 according to user needs.

[0063] In some embodiments, as Figure 1 shown, the mobile terminal 300 or other intelligent electronic devices can perform functions similar to those of the control device 100 after installing an application for controlling the display device 200.

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

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

[0066] The 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.

[0067] In some embodiments, the control device 100 includes at least one of the communication interface 130 and the user input / output interface 140. The communication interface 130 is configured in the control device 100. For example, modules such as WiFi, Bluetooth, and NFC can encode user input instructions through the WiFi protocol, or the Bluetooth protocol, or the NFC protocol and send them to the display device 200.

[0068] The memory 190 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.

[0069] The power supply 180 is used to provide operating power support for each component of the control device 100 under the control of the controller.

[0070] As Figure 4 , in some embodiments, the system is divided into four layers, from top to bottom are the Applications layer (referred to as the "application layer" for short), the Application Framework layer (referred to as the "framework layer" for short), the Android runtime and the System Libraries layer (referred to as the "system runtime layer" for short), and the Kernel layer.

[0071] In some embodiments, at least one application runs in the application layer. These applications can be window programs, system setting programs, or clock programs, etc. that come with the operating system; they can also be applications developed by third-party developers. In specific implementation, the application packages in the application layer are not limited to the above examples.

[0072] 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, which decides to let the applications in the application layer take actions. Applications can access resources in the system and obtain system services during execution through the API interface.

[0073] As Figure 4 shown, in the embodiment of the present application, the application framework layer includes a View System, Managers, a Content Provider, etc. Among them, the View System can design and implement the interface and interaction of the application. 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 icons, windows, toolbars, wallpapers, and desktop widgets on the user interface.

[0074] In some embodiments, the activity manager is used to manage the life cycles of various application programs and the general navigation back function, such as controlling the exit, opening, and backward movement of application programs. The window manager is used to manage all window programs, such as obtaining the display screen size, determining whether there is a status bar, locking the screen, capturing the screen, and controlling the change of the display window (such as shrinking the display window, jittering the display, distorting the display, etc.).

[0075] In some embodiments, the system runtime layer provides support for the upper layer, i.e., the framework layer. When the framework layer is used, the Android operating system will run the C / C++ libraries included in the system runtime layer to implement the functions to be achieved by the framework layer.

[0076] In some embodiments, the kernel layer is the layer between hardware and software. As Figure 4 shown, the kernel layer includes at least one of the following drivers: audio driver, display driver, Bluetooth driver, camera driver, WIFI driver, USB driver, HDMI driver, sensor driver (such as fingerprint sensor, temperature sensor, pressure sensor, etc.), and power driver, etc.

[0077] Based on the above application layer and application framework layer, in some embodiments, different types of application programs can be configured in the display device 200, such as media playback application programs, conference application programs, media center application programs, and application centers, etc. Users can start different types of application programs in the display device 200 to achieve different functions and display different views at the same time.

[0078] The display device 200 can also deploy other device interfaces, hardware, and drivers based on the kernel layer according to the specific display requirements of the display device 200. For example, in order to enrich the display types of the display device 200, an HDMI interface and a USB interface can be set on the display device 200. Among them, the HDMI interface can be connected to a device with video and audio input / output functions, and the corresponding audio / video output / input functions can be implemented through the HDMI driver. The USB interface can be connected to a device with signal and data transmission functions and interactive functions, and based on the USB driver, access signals, transmit data, and perform specific interactive actions.

[0079] For a display device 200 that supports touch interaction operations, the display device 200 is built-in with a touch interaction module, and can receive touch data input by a user through the touch interaction module. According to the interaction principle of the touch interaction module, the touch interaction module can detect relevant parameters in a touch action. For example, if a capacitive touch layer is provided on the screen of the display 260 of the display device 200, when a user's finger touches any position of the touch layer, the capacitance at the touch position of the touch layer will change. At this time, the touch interaction module can record the position where the capacitance changes, and combine with a timer in the controller to record the time when the capacitance change occurs, so as to generate touch data.

[0080] In some embodiments, the physical signals detected by the touch interaction module need to be converted before they can be read by the controller 250 of the display device 200. For example, the analog signal of the capacitance change needs to be converted into a digital signal and then transmitted to the controller 250 of the display device 200. In order to adapt to the screen display process of the display device 200, the touch data detected by the touch interaction module also needs to be coordinate-mapped so that the position points corresponding to the touch data can have a corresponding relationship with the pixel points in the display 260 or the user interface of the display device 200. For example, the coordinate position detection accuracy of the touch interaction module is 65536×65536, while the resolution of the display 260 of the display device 200 is 3840×2160. After the touch interaction module detects the touch data, the touch point positions in the width and height directions can be coordinate-mapped according to the ratios of 65536 / 3840 and 65536 / 2160, so that the display device 200 can perform relevant operation responses based on the coordinate positions of the mapped touch points.

[0081] Among them, the touch data can include different operation parameters according to the user's input method. For example, as Figure 5 shown, the touch data can include the touch time, touch position, touch event type, number of touch points, etc. of a touch event. During a touch interaction process, the touch event types that the touch interaction module can detect include: the down event, move event, and up event of a touch action. Corresponding to the entire touch trajectory formed by the touch data, it can be the starting point [down; x1, y1, t1], trajectory point [move; x2, y2, t2], and ending point [up; x3, y3, t3]. Each touch data records the corresponding touch event type, touch time t, and touch position (x, y), that is, the touch points of the touch trajectory can include the starting point, trajectory point, and ending point.

[0082] It should be noted that when performing a touch interaction operation, the user's finger or touch device is in surface contact with the touch interaction module, that is, the touch interaction module can detect a contact area, and the contact area includes multiple contact points. Therefore, when the display device 200 performs interaction control, it can detect (or specify) a contact point in the contact area as the touch point. For example, when the contact area is an elliptical area formed by the user's finger contacting the touch interaction module, the display device 200 can determine the coordinate extrema in two mutually perpendicular directions by traversing the contact point coordinates in the elliptical area, so as to delimit the major axis and minor axis of the elliptical area, and use the contact point located at the intersection of the major axis and minor axis as the touch point.

[0083] During the execution of the touch interaction response process, the display device 200 can classify different touch times, touch positions, the number of touch points, and touch event types, that is, it can detect the user's touch input gesture, and thus execute different interaction responses for different input gestures. For example, in the touch trajectory detected by the touch interaction module, the number of touch points is 1, the touch event type only includes the down event and the up event, and the time interval between the down event and the up event is less than the click event time threshold. And, the change distance of the touch position between the down event and the up event is less than the jitter distance threshold, then it can be determined that the current user's touch input gesture is a click gesture. Then, based on the click gesture, the display device 200 performs an operation of starting an application according to the icon in the area corresponding to the touch position of the click gesture.

[0084] Similarly, based on the touch time, touch position, the number of touch points, and touch event type, the display device 200 can also detect other touch interaction operation gestures input by the user, such as double-click gesture, swipe gesture, long-press gesture, multi-finger click gesture, multi-finger swipe gesture, etc. Different interaction gestures can derive different touch parameters. For example, the swipe gesture can also generate parameters such as swipe distance, swipe speed, swipe direction, and swipe trajectory shape. Different touch parameters can be used to perform different interaction controls.

[0085] In some embodiments, in order to enrich the types of touch interactions supported by the display device 200, the display device 200 can also perform complex gesture detection according to the dynamic change rules of touch time, touch position, number of touch points, and touch event type. For example, when the touch interaction module detects that the touch trajectory input by the user includes multiple touch points, and the touch positions of each touch point approach each other as the user inputs, it can be determined that the touch gesture currently input by the user is a grabbing gesture. Based on complex gesture detection, the display device 200 can perform more interactive responses. For example, when the detected touch gesture is a grabbing operation on an image View, the display device 200 can respond to the grabbing gesture and perform control actions to select and move the image display position.

[0086] In some embodiments, when the display device 200 detects the touch data input by the user, it distributes the touches in the touch data to the view with the highest display level at the current position according to the position coordinates corresponding to each touch event in the touch data. Exemplarily, when the display device 200 receives the touch data detected by the touch interaction module, it distributes the touch events to the activity of the corresponding window according to the position coordinates of each touch event in the touch data, and the activity then distributes the touch events to the View component with the highest display level at this position coordinate. Among them, an activity can include multiple different View components.

[0087] In order to meet the user's quick operation requirements, in some embodiments, the application program of the display device 200 is configured with a quick application, and the quick application is used to present a quick view. Among them, the display level of the quick view is the highest display level in the display device 200, and the quick view includes a hidden state and an expanded state. For example, the quick view can be the control center view of the control center application; or, the quick view can also be the main interface view of a social application, etc. In the hidden state, the user cannot perceive the quick interface on the screen of the display device 200; only in the expanded state can the user perceive the existence of the quick interface on the screen.

[0088] When the quick view is in the hidden state, the display device 200 displays the quick view based on the first layout parameter; under the first layout parameter, the display device 200 only displays a small part of the transparent view of the quick view in a specific area of the screen, and at this time the user cannot perceive the existence of the quick view. The transparent view is a part of the quick view, and the display level is the highest display level of the display device 200. Therefore, when the user touches in the display area of the transparent view, the display device 200 will distribute the touch events generated by the touch to the quick view. That is, in the hidden state, the quick view can receive the touch events applied by the user to the display area of the transparent view based on the highest-level transparent view displayed on the screen of the display device 200.

[0089] For example, as Figure 10 shown, in the hidden state, the display device 200 displays a transparent view of the quick view in the Figure 10 first intersection area. The Alpha value (transparency value) of the transparent view is 0, and the user will not perceive the quick view in the first intersection area. However, when the user touches the first intersection area, since the display level of the transparent view in the first intersection area is the highest and the transparent view is part of the quick view, the display device 200 will distribute the touch event acting on the first intersection area to the quick view for it to process.

[0090] When the quick view is in the expanded state, the display device 200 displays the quick view based on the second layout parameter; under the second layout parameter, the quick view shows a complete quick view on the screen of the display device 200. Among them, the complete quick view includes a transparent view and an opaque view, and only at this time can the user perceive the existence of the quick view. For example, when the quick view is the control center view, in the expanded state, the control center view displayed by the display device 200 is as Figure 14 shown.

[0091] In order to switch between the hidden state and the expanded state of the quick view, in some embodiments, the touch gesture can also be associated with the touch position to form a touch interaction operation based on a specific position, so that the display device 200 can respond to this touch interaction operation and switch the hidden quick view to the expanded state. For example, the touch gesture is associated with the target direction. When the display device 200 detects that the down event during the touch operation acts on the display area of the transparent view, and there is a displacement greater than a certain threshold in the target direction during the move event, until the up event is detected, the display device 200 can determine that the current touch gesture is a touch gesture of sliding in the target direction. Therefore, the display device 200 can respond to this touch gesture and control the display 260 to present a specific quick view.

[0092] Exemplarily, the display area of the above transparent view can be located at the top of the screen, the bottom of the screen, the left edge of the screen, or the right edge of the screen, and the target direction can be horizontally to the left, horizontally to the right, vertically downwards, or vertically upwards. When the display area of the transparent view is located at the top of the screen, the target direction can be horizontally downwards; when the display area of the transparent view is located at the bottom of the screen, the target direction can be horizontally upwards; when the display area of the transparent view is located at the left edge of the screen, the target direction can be horizontally to the right; when the display area of the transparent view is located at the right edge of the screen, the target direction can be horizontally to the left.

[0093] It should be noted that the display area of the transparent view and the target direction can be any one or a combination of the above, and the display area and the target direction of the transparent area can also be freely adjusted. Regarding this, the present application does not make any restrictions.

[0094] The quick view in the expanded state can provide different functions based on sub-views or display controls. That is, in some embodiments, the quick view includes at least a combination of one or more of the first sub-views or display controls, and the root nodes of the first sub-views are the same. Among them, the first sub-view included in the control center view is a first sub-view with a touchable attribute. When the user clicks on the first sub-view in the quick view with a finger or a stylus, the display device 200 can jump to other views or execute the program corresponding to the clicked sub-view based on the clicked sub-view; the display control can be a control with a touchable attribute or a control without a touchable attribute. That is, the control center view can include at least a combination of one or more of TextView (text view), Button (button), ImageView (image view), EditText (editable text), ProgressBar (progress bar), LinearLayout (linear layout), and RelativeLayout (relative layout). For example, when the quick view is the control center view, the first sub-view included in the control center view is as Figure 6 shown. The display device 200 can set a listener for the first sub-view or the display control in the XML layout file of the control center view. By using the android:onClick attribute in the XML layout file to specify that the processing method for the touch data corresponding to the click gesture is onMyButtonClick, and execute the corresponding program through the onMyButtonClick method.

[0095] For ease of understanding, the following embodiments will be described by taking the example that the transparent view shown in the hidden state of the quick view is located at the top of the screen and the target direction is the horizontal downward direction.

[0096] Obviously, in the hidden state, there will be an intersection area between the quick view and other views, such as the status bar view, the media playback view that is full-screen displayed in the media playback application, or the meeting view that is full-screen displayed in the meeting application, etc. And when other views also include sub-views or display controls that support touch, since the display level of the quick view is higher than that of other views, the touch events generated by the user's touch in the intersection area can only be distributed to the quick view, making it impossible for other views to normally implement the touch function and resulting in the problem of touch conflict. For example, when the quick view is the control center view and the display device 200 displays media in full screen through the media playback view, there is a small intersection area between the button control for closing the current media playback view and the transparent view of the control center view. If the user's hand placement position is in the intersection area, the touch event generated by the touch will not be distributed to the media playback view, affecting the user experience.

[0097] For the convenience of distinction, in the following embodiments, the quick view is referred to as the first view, and the view that intersects with the quick view is referred to as the second view. The sub-views and display controls included in the first view are collectively referred to as the first sub-views, and the sub-views and display controls included in the second view are collectively referred to as the second sub-views.

[0098] In some embodiments, the second view may be a status bar view. The status bar view includes a plurality of second sub-views. The second sub-views of the status bar view are used to present the basic information of the display device 200, and the root nodes of the second sub-views are the same. The display level of the status bar view is lower than that of the first view, but higher than that of other application views. For example, as Figure 7 shown, the status bar view is displayed at the top of the screen. The sub-views of the status bar view may include at least several or one of the sub-views of time information, the sub-views of Bluetooth status, the sub-views of WIFI status, and the sub-views of battery information. The display device 200 can update the display content of the sub-views in real time through the data information associated with the sub-views.

[0099] In the embodiments of the present application, the first view is taken as the control center view and the second view is taken as the status bar view as an example for illustration, but it is not limited thereto. The first view and the second view can both be other views.

[0100] In some embodiments, when the control center view is in a hidden state, the display device 200 displays the control center view based on the first layout parameter. At this time, the display levels of the various views in the display device 200 are as Figure 8 shown, Figure 8 in the direction from left to right in the screen area is the direction from the top of the screen to the bottom of the screen. There is an intersection area between the control center view and the status bar view at the top of the screen. The intersection area of the control center view is a transparent view. Among them, the display level of the control center view is higher than that of the status bar view, and the display level of the status bar view is higher than that of other application views. The display device 200 will distribute the touch data acting on the intersection area to the control center view.

[0101] It should be noted that in the hidden state, the transparent view displayed by the control center view on the screen may completely coincide with the status bar view or may partially coincide. The present application does not limit this.

[0102] In some embodiments, when the display device 200 full-screen displays the application view of other applications, it reads the screen resolution of the display device and obtains the full-screen display area of the screen according to the screen resolution. The display areas of the control center view and the status bar view are subtracted from the full-screen display area to obtain the reference display area of the application view. As Figure 8As shown, after the display device 200 calculates the reference display area, it controls the display 260 to display the application view of other applications in the reference display area.

[0103] In some embodiments, the control center view and the status bar view can be Views in the same application or Views in different applications respectively. When the control center view and the status bar view are Views in the same application, the root nodes of the control center view and the status bar view are the same; when the control center view and the status bar view are Views in different applications, the root nodes of the control center view and the status bar view are different. For example, the control center view and the status bar view can be different parent views in Application A; or, the control center view can be the root view of Application A, and the status bar view can be the root view of Application B.

[0104] Obviously, when the display device 200 displays the control center view based on the first layout parameter, there is an intersection area between the control center view and the status bar view. When the user touches in the intersection area, the touch event generated by the touch can only be distributed to the control center view. For example, as Figure 10 shown, when the control center view is in a hidden state, a small part of the transparent view is displayed in the first intersection area, and the first intersection area is the intersection area between the control center view and the status bar view. Obviously, most of the display area of the status bar view is occupied by the transparent view of the control center view. If the status bar view is also a touchable view, it is easy to have a touch conflict problem between the two. Therefore, some display devices 200 and terminal devices will set the status bar view to a non-touchable view.

[0105] However, different from small-screen devices such as mobile phones and tablets, due to the large screen resolution of the display device 200, the status bar view in the display device 200 will also occupy a relatively large display area. The non-touchable status bar view will reduce the touchable space of the display device 200, resulting in a decline in the user experience.

[0106] Based on the above application scenarios, some embodiments of the present application provide a display device 200, including a display 260 and a controller 250. Among them, the display 260 is configured to display a user interface, the user interface includes a first view and a second view, the display level of the first view is higher than that of the second view, and the first view is displayed based on the first layout parameter; when the first view is displayed based on the first layout parameter, there is a first intersection area between the first view and the second view, and the first intersection area of the first view is a transparent view. The display 260 is also connected to a touch interaction module, and the touch interaction module is used to detect touch data input by the user.

[0107] It should be noted that both the first view and the second view provided in the embodiments of the present application are views with touchable attributes, which can improve the problem of the reduction of the above-mentioned touchable space. Among them, the first view can be the quick view provided in the above embodiments, and the second view is a view that has an intersection area with the first view.

[0108] For the sake of convenience of description, in the embodiments of the present application, the set of touch event data generated by the user's touch in the first intersection area is referred to as the first touch data.

[0109] As Figure 9 shown, the controller 250 is configured to execute the following program steps:

[0110] S9001: In response to the first touch data input by the user, distribute the first touch data to the first view.

[0111] After the display device 200 receives the touch data input by the user based on the touch interaction module, it detects the touch event included in the touch data in response to the touch data. The touch data includes at least a down event and an up event, and the position coordinates of the down event and the up event may be the same or different. The display device 200 distributes the touch event to the view with the highest display level at the position according to the position coordinates of each touch event in the touch data.

[0112] Among them, the first touch data is the touch data acting on the first intersection area. Therefore, when the display device 200 receives the first touch data, the control system distributes the first touch data to the first view with the highest display level in the first intersection area. For example, the first view is the control center view and the second view is the status bar view. As Figure 10 shown, the user touches the first intersection area of the status bar view and the control center view in the display device 200 with a finger. Since the first intersection area of the control center view is a transparent view, the user cannot perceive the control center view located in the first intersection area. At this time, the display device 200 distributes the first touch data acting on this area to the control center view.

[0113] In some embodiments, when the first view receives the first touch data, it records the position coordinates and touch time of the down event in the first touch data. For example, when the control center view of the display device 200 receives the first touch data, it records the down event as [down; x1, y1, t1] based on the control center view.

[0114] S9002: If the first touch data includes a movement event in a target direction, respond to the first touch data based on the first view.

[0115] After the display device 200 distributes the first touch data to the first view, the first touch data is temporarily stored in the memory of the application associated with the first view based on the first view. Since the first intersection area includes two overlapping views, the display device 200 also needs to determine the view that the first touch data is expected to act on based on the first view. And because the first view needs to be called out by the user's sliding touch operation in the target direction, the display device 200 will detect whether the first touch data includes a movement event in the target direction based on the first view, that is, whether the first touch data includes a move event, and whether there is a displacement in the target direction for the move event.

[0116] When the first touch data includes a movement event in the target direction, it indicates that the first touch data is touch data acting on the first view, and the display device 200 responds to the first touch data based on the first view. Therefore, in some embodiments, when the display device 200 responds to the first touch data based on the first view, it parses the first position coordinates of the movement event in the first touch data. Then, it updates the layout coordinates of the first view according to the first position coordinates, and controls the display 260 to display the first view according to the layout coordinates, so that the first view moves in the user interface.

[0117] For example, when the control center view receives the first data distributed by the operating system, it parses the position coordinates and touch time of each movement event in the first touch data, that is, [move; x1, y1, t1]. Then, it updates the layout parameters of the XML layout file corresponding to the first view according to the coordinate distance between the movement event with the latest touch time and the coordinates of the previous touch event. When the coordinate distance between the touch point with the latest touch time and the previous touch point is 50 pixel points, it modifies the left and top attributes in the layout parameters, that is, layoutParams.topMargin += 50, and then calls the setLayoutParams() method to update the layout coordinates of the layout parameters. After the display device 200 modifies the layout coordinates based on the control center view in response to the movement event, it deletes the currently processed movement event from the memory to consume the touch event of the first touch data in a timely manner. As Figure 11 shown, when the display device 200 responds to the movement event of the first touch data based on the control center view, the non-transparent view of the control center view will move to the display area of the screen following the user's downward sliding touch operation.

[0118] As Figure 12As shown, in some embodiments, the display device 200 also receives a lift event of the first touch data based on the first view (S1201). When the user raises their hand, the touch interaction module generates an up event. Since the up event of the first touch data acts on the first intersection area, the display device 200 distributes the lift event of the first touch data to the first view, and based on the first view, in response to the lift event, reads the first height of the first view and detects the moving distance of the first view in the target direction (S1202). Then, it calculates the height ratio of the moving distance to the first height (S1203). That is to say, since the above-mentioned sliding touch operation may also be a misoperation by the user, the display device 200 also determines whether it is necessary to slide out all the non-transparent views of the first view based on the height of the first view and the moving distance of the first view.

[0119] After the display device 200 calculates the height ratio based on the first view, if the height ratio is less than the height ratio threshold, it controls the display 260 to display the first view according to the first layout parameter, so that the first view moves back to the initial position (S1204). At this time, as Figure 13 shown, in the user interface of the display device 200, the part of the first view that is still a transparent view is displayed at this time, and the user cannot perceive the first view from the display content of the user interface. If the height ratio is greater than or equal to the height ratio threshold, the display device 200 controls the display 260 to display the first view according to the second layout parameter. Among them, when the first view is displayed based on the second layout parameter, the area of the non-transparent view in the first view is larger than the area of the non-transparent view when the first view is displayed based on the first layout parameter. At this time, the display content of the user interface of the display device 200 is as Figure 14 shown.

[0120] For example, before the user touches, the user interface of the display device 200 is as Figure 13 shown. The preset height ratio threshold in the display device 200 is 0.4. When the user lifts the touch, the control system of the display device 200 sends an up event of the first touch data to the control center view. The display device 200 can read the first height of the control center view based on the layout file of the control center view and calculate the moving distance of the control center view in the target direction. If the moving distance is greater than 0, calculate the ratio of the moving distance to the first height. If the moving distance / first height ≥ 0.4, the control center view is fully displayed in the user interface, as Figure 14 shown. The left side of the control center view is a transparent view, and the right side is a non-transparent view; if the moving distance / first height < 0.4, as Figure 13 shown, move the control center view back to the initial position.

[0121] S9003: If the first touch data does not include a movement event in a target direction, send the first touch data to the second view based on the first view, and parse the first touch data based on the second view; and when the first touch data includes a target feature, respond to the first touch data based on the second view.

[0122] When the display device 200 detects based on the first view that the first touch data does not include a motion event, it indicates that the first touch data may be touch data acting on the second view. The display device 200 sends the first touch data to the second view based on the first view, that is, sends the first touch data directionally to the second view through the first view.

[0123] When the user touches the first intersection area to generate a touch event, the hand position generates the first down event in the display device 200, and the display device 200 distributes the down event to the first view. After receiving the down event, the first view records the position coordinates of the event. Before the user raises his hand, if the user does not move the touch position, the display device 200 will not generate a move event. At this time, the display device 200 will send the data related to the down event to the second view for processing.

[0124] In the above touch process, before the user raises his hand, the display device 200 may generate one or more down events. For example, after the user places his hand on the first intersection area of the touch screen, he continues to press the touch screen; at this time, if the pressure of the user's finger is uneven or the user's finger shakes slightly, the display device 200 will generate multiple down events before the up event, and the position coordinates of the down events are discontinuous.

[0125] In some embodiments, when the number of drop events is one, the display device 200 directly sends the position coordinates of the drop event to the second view. When the number of drop events is multiple, the display device 200 will continue to record the position coordinates of each drop event. Then, according to the position coordinates of the drop event, the scope of action of the drop event is calculated, and the calculated scope of action and the position coordinates of the latest drop event in the current touch time are sent to the second view.

[0126] For ease of description, the present embodiment refers to the positions of the drop events in the first touch data as the second position coordinates, and the position coordinates of the drop event with the latest touch time in the first touch data as the third position coordinates. The following describes the processing process of the first view when there are multiple drop events.

[0127] In some embodiments, when the first touch data does not include the touch points of the movement event, the display device 200 records the second position coordinates of the falling event in the first touch data based on the first view. For example, when the display device 200 is a touch screen, the user places a finger on the intersection area of the control center view and the status bar view and continuously presses the touch screen at the landing position; at this time, when the pressing force of the user's finger changes, due to uneven force, the touch screen will continuously generate multiple down events with different position coordinates, that is, the action position of the down event jumps on the touch screen. During this process, since the user does not perform actions such as swiping and lifting the hand, the touch screen will not generate move events and up events. Therefore, before the first touch data up event is generated by the touch screen, the first touch data will include multiple down events with different position coordinates.

[0128] After the display device 200 records the second position coordinates of the falling event based on the first view, a rectangular object is generated according to the second position coordinates to determine the action range of the down event in the first touch data. The rectangular object is used to represent the action range of the current falling event in the first touch data and can be generated according to the recorded second position coordinates based on the minimum rectangle principle.

[0129] For example, after the display device 200 distributes the down event to the control center view, the control center view will continuously record the second position coordinates of each down event and generate a rectangle (rect) object according to the recorded second position coordinates based on the minimum rectangle principle. The display device 200 can set the upper left corner coordinates and the lower right corner coordinates of the rectangular object according to the touch points of the maximum abscissa and the minimum abscissa, or the touch points of the maximum ordinate and the minimum ordinate in the second position coordinates, so as to generate a rectangle object as shown in Figure 15a 、 Figure 15b shown. Figure 15a and Figure 15b In, the dotted area is the rectangular object, and the touch points included in the rectangular object correspond to the touch points of each position coordinate of the falling event.

[0130] In order to reduce the error of the display device 200 in recognizing touch data, in some embodiments, after the display device 200 distributes the first touch data to the first view, it records the position coordinates of the initial falling event in the first touch data based on the first view. The initial falling event is the down event with the earliest touch time in the first touch data. After recording the position coordinates of the initial falling event, if the first view receives another falling event of the first touch data, the display device 200 calculates the touch time difference between the current falling event and the initial falling event based on the first view. If the touch time difference is greater than or equal to the target time threshold, the display device 200 records the position coordinates of the current falling event based on the first view.

[0131] That is to say, after the first view of the display device 200 receives the user's hand-down position down event, it records the position coordinates of the touch point, and when it receives the down event again subsequently, it judges the touch time difference between the touch point and the down event of the hand-down position. When the touch time difference is greater than or equal to the preset target time threshold, it then records the position coordinates of the newly received down event based on the first view. For example, the target time threshold is 500 ms. When the touch time difference ≥ 500 ms, it records the position coordinates of the newly received down event based on the control center view.

[0132] After the display device 200 generates a rectangular object based on the first view, it records the third position coordinates according to the touch time. Then it sends the rectangular object and the third position coordinates to the second view based on the first view. For example, after the display device 200 generates a rectangular object based on the control center view, it directionally sends the position coordinates of the down event with the latest touch time and the rectangular object to the status bar view based on the control center view, so that the status bar view responds to the first touch data according to the above data information.

[0133] Therefore, as Figure 16 shown, in some embodiments, after the second view of the display device 200 receives the rectangular object and the third position coordinates sent by the first view, it reads the third position coordinates based on the second view (S1601). Then it queries the display area of the second sub-view (S1602). Among them, the second sub-view is a sub-view included in the second view, and the second sub-view has the same root node as the second view. If the third position coordinates are within the display area of the second sub-view, the second sub-view is marked as the view to be responded to (S1603).

[0134] For example, as Figure 17 shown, Figure 17 in which a is the third position coordinate, and the display areas of each second sub-view in the status bar view are rectangular areas. At this time, the coordinates of the third position coordinate and the rectangular area both refer to the screen coordinate system. If a is within the display area of a certain second sub-view, then that second sub-view is marked as the view to be responded to.

[0135] As Figure 18 shown, in some embodiments, when the display device 200 marks the second sub-view as the view to be responded to, it also sets the display state of the second sub-view to the pressed state, so as to prompt the user that the sub-view has been selected. Among them, setting the second sub-view to the pressed state can modify the background image of the second sub-view, or perform scaling on the display content of the second sub-view, but it is necessary to ensure that the display area of the second sub-view remains unchanged.

[0136] In some embodiments, since the coordinate system used in the second view may be different from the screen coordinate system, that is, the reference coordinates of the upper left corner are different, when the display device 200 marks the second sub-view as a view to be responded to, it also converts the third position coordinate into the view coordinate of the second sub-view area according to the view coordinate system of the second view. That is, when the display device 200 responds to the down event in the first touch data based on the second view, it needs to convert the position coordinate of the down event into the position coordinate of the second view, so that the display device 200 can mark the view to be responded to based on the second view.

[0137] After the display device 200 reads the third position coordinate based on the second view, if the third position coordinate is not within the display area of the second sub-view, it reads the rectangular object and marks the view to be responded to according to the rectangular object (S1604). That is to say, if the down event with the latest touch time in the current first touch data is not within the display area of any sub-view in the second view, the display device 200 reads the rectangular object sent by the first view to obtain the event scope of the current first touch data, and then determines the view to be responded to according to the event scope.

[0138] As Figure 16 、 Figure 19 shown, the display device 200 can determine the view to be responded to according to the overlapping degree between the rectangular object and the display area of the second sub-view. Therefore, in some embodiments, the display device 200 detects the second intersection area between the rectangular object and the second sub-view (S1605), and calculates the reference area according to the second height of the second intersection area (AR2) (S1606). The reference area (AR1) is the area in the rectangular object with a height equal to the second height. Then, it calculates the area ratio of the second intersection area to the reference area (S1607). If the area ratio is greater than the area ratio threshold, it marks the second sub-view as the view to be responded to (S1608).

[0139] For example, the area ratio threshold is 0.51. After the status bar view of the display device 200 determines that the touch point of the down event with the latest touch time is not within the display area of any second sub-view, it reads the rectangular object sent by the control center view and queries the second sub-view that intersects with the rectangular object. As Figure 19 shown, the area of the reference area is AR1, and the area of the intersection area is AR2. When AR1 / AR2 > 0.51, the display device 200 marks the second sub-view as the view to be responded to based on the status bar view; otherwise, it does not perform any processing.

[0140] Obviously, since the first touch data is the touch data where the touch point is located in the first intersection area, and the view with the highest display level in the first intersection area is the first view, the display device 200 will receive each touch event of the first touch data based on the first view. After the first view sends the relevant data of the drop event to the second view, the first view will also send the lift event corresponding to the first touch data to the second view.

[0141] Therefore, in some embodiments, as Figure 20 shown, the display device 200 receives the lift event sent by the first view based on the second view (S2001). Then, in response to the lift event, the fourth position coordinate of the lift event is parsed (S2002). If the fourth position coordinate is within the display area of the view to be responded to, it is marked that the first touch data includes the target feature to indicate that the current first touch data requires the second view to respond (S2003). Then, the display 260 is controlled to display the third view based on the view to be responded to. Among them, the third view is the view associated with the view to be responded to.

[0142] Exemplarily, when the display device 200 marks the second sub-view as the view to be responded to through the third position coordinate or the rectangular object, a to-be-responded identifier is set in the sub-view. When the status bar view receives the up event sent by the control center view, it detects the position coordinate of the up event and determines whether the up event is within the display area of the view to be responded to. If the up event is within the display area of the view to be responded to, the display device 200 responds to the first touch data through the view to be responded to, displays the third view associated with the view to be responded to, and clears the to-be-responded identifier and the pressed state of the view to be responded to.

[0143] For example, as Figure 21 shown, when the view to be responded to is the Bluetooth status view, the display device 200 controls the display to display the Bluetooth settings view associated with the Bluetooth status view of the status bar view. Among them, the XML layout file of the Bluetooth status view of the display device 200 can be set with the logic of clicking an event to jump to the Bluetooth settings view.

[0144] Conversely, in some embodiments, if the fourth position coordinate is not within the display area of the view to be responded to, the to-be-responded identifier of the view to be responded to is deleted, and the lift event sent by the first view is deleted based on the second view (S2004), that is, when the position coordinate of the up event is not within the display area of the view to be responded to, the second view of the display device 200 does not process the up event.

[0145] As can be seen from the above embodiments, when all touch points in the first touch data act on the first intersection area of the first view and the second view, the display device 200 provided by some embodiments of the present application can distribute all the first touch data to the first view, and determine whether the first touch data includes a move event. If the first touch data includes a move event, the display device 200 responds to the move event in real time based on the first view, moves the first view into the screen for display, and when receiving the up event of the first touch data, determines whether to switch the first view to an expanded state according to the moving distance and the height of the first view. Conversely, if the first touch data does not include a move event, the display device 200 distributes the first touch data to the second view for processing based on the first view, and then determines the view to be responded to by the current first touch data based on the second view. Moreover, when the second view receives the up event sent by the first view, it determines whether to respond to the first touch data according to the relative position of the up event and the view to be responded to, so as to accurately identify the view that the first touch data is expected to act on.

[0146] Since the user may also perform touches in the display area of the second view other than the first intersection area, in the embodiments of the present application, the set of touch event data generated by touches in the display area of the second view other than the first intersection area is referred to as the second touch data. And in the display area of the second view other than the first intersection area, the display level of the second view is the highest. At this time, the display device 200 distributes the second touch data to the second view.

[0147] Therefore, in some embodiments, the display device 200 responds to the second touch data input by the user and distributes the second touch data to the second view. Wherein, the second touch data is touch data acting on the display area of the second view other than the first intersection area. Then, the second touch data is parsed based on the second view. When the second touch data includes a target feature, the second touch data is responded to based on the second view.

[0148] For example, when the user performs a touch in the display area of the status bar view other than the first intersection area to generate the second touch data, the display device 200 distributes all the complete second touch data to the status bar view. At this time, regardless of whether the second touch data includes a move event in the target direction, the display device 200 needs to send all the touch data to the status bar view. When the status bar view receives the second touch data, it determines the view to be responded to in the second view through the position coordinates of the second touch data, so as to respond to the second touch data through the view to be responded to.

[0149] Such as Figure 22As shown, in some embodiments, after the display device 200 distributes the second touch data to the second view, it parses the fifth position coordinate of the initial falling event in the second touch data based on the second view (S2201). Here, the initial falling event of the second touch data is the falling event with the earliest touch time in the second touch data. If the fifth position coordinate is within the display area of the second sub-view, the second sub-view is marked as the view to be responded to (S2202). Then, based on the second view, it receives the moving event or falling event in the second touch data and parses the sixth position coordinate of the moving event or falling event in the second touch data. If the sixth position coordinate is within the display area of the view to be responded to, the to-be-responded identifier of the view to be responded to is maintained (S2203). When the second view receives the lifting event of the second touch data and the lifting event is within the display area of the view to be responded to, the display device 200 displays the third view based on the view to be responded to of the second view; if the sixth position coordinate is not within the display area of the view to be responded to, the to-be-responded identifier of the view to be responded to is deleted and no processing is performed (S2204).

[0150] For example, when the user outputs the second touch data in the display area of the status bar view except for the first intersection area, the control system of the display device 200 distributes the complete down event, move event, and up event in the second touch data to the status bar view, and parses the position coordinates of each touch event based on the status bar view. First, the display device 200 determines the view to be responded to based on the first down event received by the status bar view. When the first down event is within the display area of a certain second sub-view, the second sub-view is marked as the view to be responded to. All subsequent touch events received by the status bar view need to be compared with the display area of the view to be responded to in terms of position. If there is a move event or down event that is not within the display area of the view to be responded to, the to-be-responded identifier of that sub-view is deleted, and the view to be responded to is no longer marked by the position coordinates of the touch events in the second touch data. If each move event or down event is within the display area of the view to be responded to, the to-be-responded identifier of that sub-view is maintained, and when the touch event of the up event is also within the display area of the view to be responded to, the third view is displayed based on the view to be responded to in the second view.

[0151] As can be seen from the above embodiments, the display device 200 provided in some embodiments of the present application can distribute all of the second touch data to the second view when the second touch data acts on the display area of the second view except for the first intersection area. The view to be responded to is determined based on the first down event received by the second view, and when all subsequent received touch events are within the display area of the view to be responded to, the second touch data is responded to based on the view to be responded to of the second view, and the third view associated with the view to be responded to is displayed, enabling the display device 200 to accurately and timely respond to the second touch data.

[0152] However, when the user touches, the user may also slide back and forth in the first intersection area and the display area in the second view except for the first intersection area. The display device 200 also needs to determine the touch data generated across regions to determine the view that the current touch data is expected to act on. For the sake of distinction, for the set of touch event data generated across regions, the touch events located in the first intersection area are collectively referred to as the first touch events, and the touch events located in the second view except for the first intersection area are collectively referred to as the second touch events.

[0153] For the case where the initial touch-down position is in the display area of the second view except for the first intersection area, in the embodiment of the present application, the set of data where the initial touch-down event is in the display area of the second view except for the first intersection area but there are subsequent touch events in the first intersection area is referred to as the third touch data. The initial touch-down event is the touch-down event with the earliest touch time in the third touch data, that is, the down event generated by the first touch-down. As Figure 23 shown, when the user's initial touch-down position is in the display area of the second view except for the first intersection area, in some embodiments, the display device 200 also distributes the second touch event of the third touch data to the second view (S2301) in response to the third touch data input by the user. The third touch data is the touch data where the initial touch-down event is in the display area of the second view except for the first intersection area. The first touch event of the third touch data is distributed to the first view (S2302). Then, the event type of the first touch event is detected based on the first view (S2303). If the event type is a lift event, the first touch event is recorded based on the first view, and the first touch event is sent to the second view based on the first view (S2304); if the event type is a move event or a touch-down event, the first touch event is deleted (S2305).

[0154] That is to say, when the first received down event is in the display area of the second view except for the first intersection area, the display device 200 distributes the second touch event generated in the current area to the second view. During the touch process, if the position touched by the user slides to the first intersection area, the display device 200 distributes the first touch event generated in the first intersection area to the first view. At this time, the display device 200 receives the first touch event based on the first view and determines that the first down event of the current touch data has been distributed to the second view. Therefore, the display device 200 determines the event type of the current first touch event through the first view. If the event type is a down event or a move event, the display device 200 does not perform processing on it based on the first view; if the event type is an up event, the display device 200 sends the up event to the second view based on the first view, so that the second view determines whether to respond to the third touch data through the view to be responded to in the second view according to the received up event. After receiving the up event sent by the first view, the second view of the display device 200 executes the steps of S2201 - S2205.

[0155] Obviously, in some embodiments, when the user inputs the third touch data and the lift event is in the display area of the second view except for the first intersection area, the display device 200 directly distributes the lift event to the second view. After receiving the lift event distributed by the display device 200, the second view executes the steps of S2201 - S2205.

[0156] For the case where the user's hand - down position is in the first intersection area, in the embodiments of the present application, the data set in which the initial down event is in the first intersection area but there are subsequent touch events in the display area of the second view except for the first intersection area is called the fourth touch data.

[0157] In some embodiments, the display device 200 also responds to the fourth touch data input by the user and distributes the first touch event in the fourth touch data to the first view. Among them, the fourth touch data is the touch data with the initial down event in the first intersection area. After receiving the first touch event, the first view executes the steps of S9001 - S9002. When the touch position of the user moves to the display area of the second view except for the first intersection area, the display device 200 generates a second touch event and distributes the second touch event of the fourth touch data to the second view, so that the second view executes the steps of S2201 - S2205.

[0158] Moreover, in order to improve the response effect of touch data, in some embodiments, when the display device 200 sends the second touch event in the fourth touch data to the second view based on the first view, it also detects the moving distance of the first view. If the moving distance of the first view is greater than 0, the display 260 is controlled to display the first view according to the first layout parameter to restore it to the hidden state; otherwise, no processing is performed.

[0159] As can be seen from the above embodiments, when the user moves back and forth across regions in the display regions of the first view and the second view except for the first intersection region, if the first down event is located in the display region outside the first intersection region of the second view, before the up event, if the first view receives a touch event, the first view does not respond to the current touch event and only sends the up event to the second view in a directed manner when receiving the up event. When the first down event is located in the first intersection region of the first view, the display device 200 executes steps S9001 - S9003; and when the touch position of the user moves to the second view, steps S2201 - S2205 are executed.

[0160] Based on the above display device 200, some embodiments of the present application further provide a multi - view touch method, which is applied to the display device 200 provided in the above embodiments. The display device 200 includes a display 260 and a controller 250. Among them, the display 260 is configured to display a user interface, and the user interface includes a first view and a second view. The display level of the first view is higher than that of the second view, and the first view is displayed based on the first layout parameter; when the first view is displayed based on the first layout parameter, there is a first intersection region between the first view and the second view, and the first intersection region of the first view is a transparent view; the display is connected to a touch interaction module, and the touch interaction module is used to detect touch data input by the user. As Figure 9 shown, the method includes the following program steps:

[0161] S9001: In response to the first touch data input by the user, distribute the first touch data to the first view, where the first touch data is touch data acting on the first intersection region;

[0162] S9002: If the first touch data includes a moving event in the target direction, respond to the first touch data based on the first view;

[0163] S9003: If the first touch data does not include the moving event in the target direction, send the first touch data from the first view to the second view and parse the first touch data based on the second view; and when the first touch data includes a target feature, respond to the first touch data based on the second view.

[0164] As can be seen from the above technical solutions, for the display device and status bar view provided by some embodiments of the present application, the method can distribute the first touch data to the first view in response to the first touch data input by the user. Among them, the first touch data is the touch data acting on the intersection area of the first view and the second view. If the first touch data includes a movement event in the target direction, the first view responds to the first touch data; if the first touch data does not include a movement event in the target direction, the first view sends the first touch data to the second view, and then the second view parses the first touch data, and when the first touch data includes the target feature, the second view responds to the first touch data. The method can determine the view that the touch data is expected to act on according to the event type of the touch data when multiple views overlap, and respond to the touch data based on the determined view, thereby improving the accuracy of touch interaction operations and improving the user experience.

[0165] The same or similar parts among the various embodiments in this specification can be referred to each other, and will not be repeated here.

[0166] Those skilled in the art can clearly understand that the technology in the embodiments of the present invention can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solutions in the embodiments of the present invention, in essence, or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., including several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods in various embodiments or some parts of the embodiments of the present invention.

[0167] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, and are not intended to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements on some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the various embodiments of the present application.

[0168] For the sake of convenience of explanation, the above description has been made in combination with specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or to limit the embodiments to the specific forms disclosed above. According to the above teachings, various modifications and variations can be obtained. The selection and description of the above embodiments are for the purpose of better explaining the principles and practical applications, so that those skilled in the art can better use the embodiments and various different variations of the embodiments suitable for specific use considerations.

Claims

1. A display device, characterized in that, Comprising: A display configured to display a user interface, the user interface including a first view and a second view, the display level of the first view being higher than that of the second view, and the first view being displayed based on first layout parameters; when the first view is displayed based on the first layout parameters, there is a first intersection area between the first view and the second view, and the first intersection area of the first view is a transparent view; the display is connected to a touch interaction module for detecting touch data input by a user; A controller configured to: In response to first touch data input by a user, distribute the first touch data to the first view, the first touch data being touch data acting on the first intersection area; If the first touch data includes a movement event in a target direction, respond to the first touch data based on the first view; If the first touch data does not include the movement event in the target direction, send the first touch data from the first view to the second view and parse the first touch data based on the second view; And, when the first touch data includes a target feature, respond to the first touch data based on the second view.

2. The display device according to claim 1, wherein When the controller executes responding to the first touch data based on the first view, it is configured to: Parse the first position coordinates of the movement event in the first touch data; Update the layout coordinates of the first view according to the first position coordinates; Control the display to display the first view according to the layout coordinates, so that the first view moves in the user interface.

3. The display device according to claim 2, wherein When the controller executes responding to the first touch data based on the first view, it is further configured to: Receive a lift event of the first touch data based on the first view; In response to the lift event, read the first height of the first view and detect the moving distance of the first view in the target direction; Calculate the height ratio of the moving distance to the first height; If the height ratio is less than a height ratio threshold, control the display to display the first view according to the first layout parameters; If the height ratio is greater than or equal to the height ratio threshold, control the display to display the first view according to second layout parameters, and when the first view is displayed based on the second layout parameters, the area of the non-transparent view of the first view is greater than the area of the non-transparent view of the first view when the first view is displayed based on the first layout parameters.

4. The display device according to claim 1, wherein If the first touch data does not include the movement event in the target direction, when the controller executes sending the first touch data from the first view to the second view, it is configured to: Record the second position coordinates of the down event in the first touch data based on the first view; Generate a rectangular object according to the second position coordinates; Parse the touch time of the down event; Record third position coordinates according to the touch time, the third position coordinates being the position coordinates of the down event with the latest touch time in the first touch data; Send the rectangular object and the third position coordinates to the second view based on the first view.

5. The display device according to claim 4, characterized in that, The controller executes parsing the first touch data based on the second view and is configured to: Read the third position coordinates based on the second view; Query the display area of the second sub - view, where the second sub - view is a sub - view included in the second view; If the third position coordinates are within the display area of the second sub - view, mark the second sub - view as the view to be responded to; If the third position coordinates are not within the display area of the second sub - view, read the rectangular object and mark the view to be responded to according to the rectangular object.

6. The display device according to claim 5, wherein The controller executes marking the view to be responded to according to the rectangular object and is configured to: Detect the second intersection area between the rectangular object and the second sub - view; Calculate a reference area according to the second height of the second intersection area, where the reference area is the area in the rectangular object with a height equal to the second height; Calculate the area ratio of the second intersection area to the reference area; If the area ratio is greater than the area ratio threshold, mark the second sub - view as the view to be responded to.

7. The display device according to claim 6, characterized in that If the first touch data does not include a movement event in the target direction, the controller is further configured to send the lift event of the first touch data to the second view based on the first view; The controller executes responding to the first touch data based on the second view and is configured to: Receive the lift event sent by the first view based on the second view; In response to the lift event, parse the fourth position coordinates of the lift event; If the fourth position coordinates are within the display area of the view to be responded to, mark that the first touch data includes a target feature; Control the display to display the third view based on the view to be responded to; The third view is a view associated with the view to be responded to.

8. The display device according to claim 1, wherein, The controller is further configured to: In response to second touch data input by the user, distribute the second touch data to the second view, where the second touch data is touch data acting on the display area of the second view except the first intersection area; Parse the second touch data based on the second view; When the second touch data includes the target feature, respond to the second touch data based on the second view.

9. The display device according to claim 1, wherein The controller is further configured to: In response to third touch data input by the user, distribute the second touch event of the third touch data to the second view, where the third touch data is touch data with an initial fall event acting on the display area of the second view except the first intersection area, the initial fall event is the earliest fall event in the third touch data, and the second touch event is a touch event located in the display area of the second view except the first intersection area; Distribute the first touch event of the third touch data to the first view, where the first touch event is a touch event located in the first intersection area; Detect the event type of the first touch event based on the first view; If the event type is a lift event, send the first touch event to the second view based on the first view; If the event type is a move event or a drop event, delete the first touch event.

10. A multi-view touch method, characterized in that, Applied to a display device, configured to display a user interface, the user interface includes a first view and a second view, the display level of the first view is higher than that of the second view, and the first view is displayed based on first layout parameters; when the first view is displayed based on the first layout parameters, there is a first intersection area between the first view and the second view, and the first intersection area of the first view is a transparent view; The display is connected to a touch interaction module for detecting touch data input by a user; the method includes: In response to first touch data input by a user, distribute the first touch data to the first view, where the first touch data is touch data whose action is located in the first intersection area; If the first touch data includes a move event in a target direction, respond to the first touch data based on the first view; If the first touch data does not include a move event in the target direction, send the first touch data from the first view to the second view and parse the first touch data based on the second view; and, when the first touch data includes a target feature, respond to the first touch data based on the second view.

Images