Display device and touch method for display device

Abstract

The present application provides a display device and a touch method for the display device. The display device comprises at least one processor connected to a display, a touch interaction module, and a memory, the processor being configured to execute a computer program or an instruction in the memory to cause the display device to: in response to first touch data input by a user, distribute the first touch data to a first view, the first touch data being touch data acting on an intersection area of the first view and a second view; if the first touch data comprises a movement event in a target direction, respond to the first touch data on the basis of the first view; if the first touch data does not comprise the movement event in the target direction, send the first touch data to the second view on the basis of the first view; and when the first touch data comprises a target feature, respond to the first touch data on the basis of the second view. During overlapping of multiple views, a view desired to be acted on is determined on the basis of touch data, and the touch data is responded to on the basis of the view, thereby improving the accuracy of touch interaction operations.

Description

Display device and touch control method for display device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application No. 202410063218.5, filed on January 16, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application relates to the technical field of display devices, and in particular to a display device and a touch control method for the display device. Background Art

[0004] Display devices are terminal devices that can present a user interface and support user interaction. For example, smart TVs are based on Internet application technology, feature open operating systems and chips, and possess an open application platform. They enable two-way human-computer interaction and integrate multiple functions, including audio, video, entertainment, and data, to meet diverse and personalized user needs. Display devices can also implement touch-sensitive interactive operations through built-in or external touch modules.

[0005] In order to meet the needs of users for quick operations, for display devices that support touch interactive operations, quick views including hidden and expanded states can be run, and the quick views support touch. Users can call out the expanded quick view on the display device through specific touch gestures. For example, the quick view can be a control center view, and the user can call out the expanded control center view through touch gestures such as swiping up or down. In order for 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 transparent view has the highest display level, thereby ensuring that the user can call out the expanded quick view in any scenario.

[0006] However, the above-mentioned transparent view will have an intersection area with other views. When other views also support touch, the touch performed by the user in the intersection area will conflict, making it impossible for the display device to accurately identify which view the touch event acting on the intersection area is acting on, resulting in a decrease in the accuracy of the display device in responding to touch events, affecting the user's interactive experience. Summary of the Invention

[0007] According to some embodiments of the present application, a display device may include a display, a touch interaction module connected to the display, a memory, and at least one processor. The display may be configured to display a user interface, the user interface may include a first view and a second view, the display level of the first view may be higher than the display level 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, the first view and the second view have a first intersection area, and the first intersection area of ​​the first view is a transparent view; the touch interaction module may be configured to detect touch data input by a user; the memory may be configured to store computer programs or instructions; the at least one processor, connected to the display and the memory, may be configured to execute the computer program or instructions to cause the display device to: in response to first touch data input by the 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 motion 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 motion event in the 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, if the first touch data includes a target feature, respond to the first touch data through the second view.

[0008] According to some embodiments of the present application, a touch control method for a display device is also provided. The display device may include a display and a touch interaction module connected to the display, the touch interaction module being configured to detect touch data input by a user. The display may be configured to display a user interface, the user interface may include a first view and a second view, the display level of the first view may be higher than the display level 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, the first view and the second view have a first intersection area, and the first intersection area of ​​the first view is a transparent view. The method includes: in response to first touch data input by the user, distributing 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 motion event in a target direction, responding to the first touch data based on the first view; if the first touch data does not include a motion event in the target direction, sending the first touch data to the second view based on the first view, and parsing the first touch data based on the second view; and, if the first touch data includes a target feature, responding to the first touch data through the second view. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to more clearly illustrate the solutions in the embodiments of the present application or related technologies, the following briefly introduces the drawings required for use in the embodiments or related technology descriptions. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0010] FIG1 is a schematic diagram of a usage scenario of a display device according to some embodiments of the present application;

[0011] FIG2 is a hardware configuration block diagram of a display device according to some embodiments of the present application;

[0012] FIG3 is a hardware configuration block diagram of a control device provided according to some embodiments of the present application;

[0013] FIG4 is a schematic diagram of software configuration in a display device according to some embodiments of the present application;

[0014] FIG5 is a schematic diagram of touch data provided according to some embodiments of the present application;

[0015] FIG6 is a schematic diagram showing the display effect of a control center view according to some embodiments of the present application;

[0016] FIG7 is a schematic diagram of a display effect of a status bar view provided according to some embodiments of the present application;

[0017] FIG8 is a schematic diagram showing the relationship between various view display levels provided according to some embodiments of the present application;

[0018] FIG9 is a schematic diagram of a flow chart of a multi-view touch method according to some embodiments of the present application;

[0019] FIG10 is a schematic diagram showing the effect of touch control in the first intersection area according to some embodiments of the present application;

[0020] FIG11 is a schematic diagram showing the effect of responding to a touch point movement event based on a first view according to some embodiments of the present application;

[0021] FIG12 is a schematic diagram of a process of responding to a touch point of a lift event based on a first view according to some embodiments of the present application;

[0022] FIG13 is a schematic diagram showing the effect of a first view in a hidden state according to some embodiments of the present application;

[0023] FIG14 is a schematic diagram showing the effect of a first view in an expanded state according to some embodiments of the present application;

[0024] FIG15a is a schematic diagram of a rectangular object provided according to some embodiments of the present application;

[0025] FIG15 b is a schematic diagram of another rectangular object provided according to some embodiments of the present application;

[0026] FIG16 is a schematic diagram of a process of responding to a drop event based on a second view according to some embodiments of the present application;

[0027] FIG17 is a schematic diagram of a view for marking a response according to some embodiments of the present application;

[0028] FIG18 is a schematic diagram showing the effect of setting a waiting-for-response view to a pressed state according to some embodiments of the present application;

[0029] FIG19 is a schematic diagram of marking a view to be responded to based on a rectangular object according to some embodiments of the present application;

[0030] FIG20 is a schematic diagram of a process of responding to a touch point of a lift event based on a second view according to some embodiments of the present application;

[0031] FIG21 is a schematic diagram showing the effect of displaying a third view according to some embodiments of the present application;

[0032] FIG22 is a schematic diagram of a process of responding to touch data based on a second view according to some embodiments of the present application;

[0033] FIG23 is a schematic diagram of a process for responding to touch data when moving across regions according to some embodiments of the present application. DETAILED DESCRIPTION

[0034] The following embodiments are described in detail, with examples illustrated in the accompanying drawings. When the following description refers to the drawings, identical numbers in different figures represent identical or similar elements unless otherwise indicated. The embodiments described in the following embodiments are not intended to represent all possible implementations consistent with the present application. They are merely examples of systems and methods consistent with certain aspects of the present application, as detailed in the claims.

[0035] It should be noted that the brief descriptions of terms in this application are only for the purpose of facilitating the understanding of the embodiments described below, and are not intended to limit the embodiments of this application. Unless otherwise specified, these terms should be understood according to their ordinary and usual meanings.

[0036] In the specification and claims of this application and the accompanying drawings, the terms "first," "second," "third," etc. are used to distinguish similar or similar objects or entities, and are not necessarily intended to limit a particular order or sequence, unless otherwise noted. It should be understood that the terms used in this manner are interchangeable under appropriate circumstances.

[0037] The terms "comprise," "include," and "have," and any variations thereof, are intended to cover but not exclude inclusion; for example, a product or device comprising a list of components is not necessarily limited to all the components expressly listed but may include other components not expressly listed or inherent to such product or device.

[0038] The term "module" refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and / or software code that is capable of performing the functionality associated with that element.

[0039] Figure 1 is a schematic diagram of an operation scenario between a display device and a control device according to some embodiments of the present application. As shown in Figure 1, a user can operate a display device 200 through touch operation, a mobile terminal 300, and a control device 100. The control device 100 can be a remote control, a stylus, etc.

[0040] In some embodiments, the mobile terminal 300 can install software applications on the display device 200 and connect to the display device 200 through a network communication protocol to achieve one-to-one control operations and data communication. It is also possible to transmit audio and video content displayed on the mobile terminal 300 to the display device 200 for synchronous display.

[0041] 1 , the display device 200 can also communicate data with the server 400 through various communication methods. The display device 200 can be allowed to communicate via a local area network (LAN), a wireless local area network (WLAN), and other networks.

[0042] In addition to providing broadcast reception television functions, the display device 200 may also provide intelligent network television functions with computer support functions, including but not limited to network television, smart TV, and Internet Protocol Television (IPTV).

[0043] Figure 2 is a block diagram of the hardware configuration of a display device according to some embodiments of the present application. In some embodiments, the display device 200 may include at least one of a tuner / demodulator 210, a communication device 220, a detector 230, a device interface 240, at least one processor 250, a display 260, an audio output interface 270, a memory, a power supply, and a user interface.

[0044] In some embodiments, detector 230 can be used to collect signals from the external environment or external interactions. For example, detector 230 can include a light receiver, a sensor that can be used to collect information about ambient light intensity; or detector 230 can include an image collector, such as a camera, that can be used to collect information about the external environment, user attributes, or user interaction gestures; or detector 230 can include a sound collector, such as a microphone, that can be used to receive external sounds.

[0045] In some embodiments, the display 260 may include a display screen component for presenting images and a driving component for driving image display, which can be used to receive image signals output from the controller, display video content, image content, and components of a menu control interface and a user control UI interface, etc.

[0046] In some embodiments, the display 260 can be connected to a touch interaction module so that the display device 200 supports touch interaction operations. The touch interaction module can be a built-in module, which together with the touch screen forms a touch display screen, or it can be an external module. For example, in order to realize touch interaction operations, for a display device 200 with a built-in touch interaction module, the display 260 can be a touch screen, which can receive touch signals input by fingers, contacts, styluses, etc., and perform touch interaction responses according to pre-set interaction strategies. For a display device 200 with an external touch interaction module, a terminal, device, or component with touch function can be connected through the device interface of the display device 200. For example, the Universal Serial Bus (USB) or USB-C interface of the display device 200 is connected to a touch panel, and the touch panel can receive the touch track input by the user in real time and transmit the touch track to the display device 200 through the USB channel. The display device 200 can then perform interaction responses based on the received touch track in combination with the touch application, so that the display device 200 supports touch interaction operations.

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

[0048] In some embodiments, the processor may include at least one of a central processing unit (CPU), a video processor, an audio processor, a graphics processing unit (GPU), a random access memory (RAM), a read-only memory (ROM), a first interface to an nth interface for input / output, a communication bus, etc. The at least one processor 250 may control the operation of the display device and respond to user operations through various software control programs, or computer programs or instructions, stored in the memory. The at least one processor 250 controls the overall operation of the display device 200.

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

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

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

[0052] Figure 3 is a hardware configuration block diagram of a control device according to some embodiments of the present application. As shown in Figure 3, the control device 100 may include a device controller 110, a communication interface 130, a user input / output interface, a memory, and a power supply.

[0053] In some embodiments, the control device 100 can be configured to control the display device 200, and can receive the user's input operation instructions, and convert the operation instructions into instructions that the display device 200 can recognize and respond to, thereby acting as an interactive intermediary between the user and the display device 200.

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

[0055] In some embodiments, as shown in FIG. 1 , the mobile terminal 300 or other intelligent electronic device can perform similar functions as the control device 100 after installing an application for controlling the display device 200 .

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

[0057] The communication interface 130 communicates control signals and data signals with the display device 200 under the control of the device controller 110. The communication interface 130 may include at least one of a WiFi chip 131, a Bluetooth module 132, an NFC module 133, or other near field communication modules.

[0058] The user input / output interface 140 , wherein the input interface may include at least one of a microphone 141 , a touch panel 142 , a sensor 143 , a button 144 , and other input interfaces.

[0059] In some embodiments, the control device 100 may include at least one of a communication interface 130 and a user input / output interface 140. The control device 100 may be configured with the communication interface 130, such as a WiFi, Bluetooth, or NFC module, to encode user input commands via the WiFi protocol, Bluetooth protocol, or NFC protocol and transmit them to the display device 200.

[0060] The memory 190 can be 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 also store various control signal instructions input by the user.

[0061] The power supply 180 can be used to provide operating power support for various components of the control device 100 under the control of the controller.

[0062] As shown in Figure 4, in some embodiments, the display device divides the system into four layers, from top to bottom: the application layer (referred to as the "application layer"), the application framework layer (referred to as the "framework layer"), the Android runtime and system library layer (referred to as the "system runtime library layer"), and the kernel layer.

[0063] In some embodiments, the application layer may include at least one application. These applications may include a window program, a system settings program, a clock program, or other programs included with the operating system, or applications developed by third-party developers. In specific implementations, the application packages in the application layer are not limited to the above examples.

[0064] The framework layer provides applications with an application programming interface (API) and programming framework. The application framework layer includes predefined functions. The application framework layer acts as a processing center, determining actions for applications in the application layer. Applications use the API to access system resources and services during execution.

[0065] As shown in FIG4 , in some embodiments of the present application, the application framework layer may further include a view system, managers, content providers, etc., wherein the view system may design and implement the interface and interaction of the application, and the view system may include lists, grids, text boxes, buttons, etc. The manager may include at least one of the following modules: an activity manager may be used to interact with all activities running in the system; a location manager may be used to provide system services or applications with access to the system location service; a package manager may be used to retrieve various information related to the application packages currently installed on the device; a notification manager may be used to control the display and clearing of notification messages; and a window manager may be used to manage icons, windows, toolbars, wallpapers, and desktop widgets on the user interface.

[0066] In some embodiments, the activity manager can also be used to manage the lifecycle of each application and common navigation back functions, such as controlling the exit, opening, and back of an application. The window manager can be used to manage all window programs, such as obtaining the display screen size, determining whether there is a status bar, locking the screen, taking screenshots, and controlling display window changes (for example, shrinking the display window, shaking the display, distorting the display, etc.).

[0067] In some embodiments, the system runtime layer provides support for the upper layer, namely the framework layer. When the framework layer is used, the Android operating system will run the C / C++ library contained in the system runtime layer to implement the functions to be implemented by the framework layer.

[0068] In some embodiments, the kernel layer is a layer between hardware and software. As shown in FIG4 , the kernel layer may include at least one of the following drivers: an audio driver, a display driver, a Bluetooth driver, a camera driver, a Wi-Fi driver, a USB driver, a High Definition Multimedia Interface (HDMI) driver, a sensor driver (such as a fingerprint sensor, a temperature sensor, a pressure sensor, etc.), and a power driver.

[0069] Based on the above-mentioned application layer and application framework layer, in some embodiments, different types of applications can be configured in the display device, such as media playback applications, conference applications, media center applications, and application centers, etc. Users can realize different functions by launching different types of applications in the display device and display different views at the same time.

[0070] Display devices can also deploy other device interfaces, hardware, and drivers based on the kernel layer according to the specific display requirements of the display device. For example, to enrich the display types of the display device, the display device can be provided with an HDMI interface and a USB interface. The HDMI interface can connect to devices with video and audio input / output functions, and implement the corresponding audio and video output / input functions through the HDMI driver. The USB interface can connect to devices with signal and data transmission functions and interactive functions, and based on the USB driver, it can access signals, transmit data, and perform specific interactive actions.

[0071] For display devices that support touch interaction operations, the display device may have a built-in touch interaction module, and the touch data input by the user may be received through the touch interaction module. According to the interaction principle of the touch interaction module, the touch interaction module may detect relevant parameters in the touch action. For example, the display 260 of the display device 200 is provided with a capacitive touch layer. When the user's finger touches any position of the touch layer, the capacitance of the touch layer at the touched position will change. At this time, the touch interaction module can record the position of the capacitance change and, in conjunction with a timer in at least one processor, record the time when the capacitance change occurs to generate touch data.

[0072] In some embodiments, the physical signal detected by the touch interaction module needs to be converted before it can be read by at least one processor of the display device. For example, the analog signal of the capacitance change needs to be converted into a digital signal and then transmitted to the at least one processor 250 of the display device 200. In order to adapt to the screen display process of the display device, the touch data detected by the touch interaction module also needs to be coordinate mapped so that the position point corresponding to the touch data can correspond to the pixel point in the display or user interface of the display device. For example, the coordinate position detection accuracy of the touch interaction module is 65536×65536, and 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 position in the width and height directions can be coordinate mapped according to the ratio of 65536 / 3840 and 65536 / 2160, so that the display device 200 can perform related operation responses based on the mapped touch point position coordinates.

[0073] In some embodiments, the touch data may include different operating parameters according to the user's input method. For example, as shown in Figure 5, the touch data may include the touch time, touch position, touch event type, number of touch points, etc. of the touch event. During a touch interaction process, the touch event types that can be detected by the touch interaction module include but are not limited to: a down event, a move event, and an up event of a touch action. Corresponding to the entire touch trajectory formed by the touch data, it can be a starting point [down; x1, y1, t1], a trajectory point [move; x2, y2, t2], and an end 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 point of the touch trajectory may include a starting point, a trajectory point, and an end point.

[0074] It should be noted that, since the user's finger or touch device is in surface contact with the touch interaction module when performing touch interaction operations, that is, the touch interaction module can detect a contact area, which may include multiple contact points. Therefore, when the display device performs interactive control, it can detect (or specify) a contact point in the contact area as a touch point. For example, when the contact area is an elliptical area formed when the user's finger contacts the touch interaction module, the display device 200 can traverse the contact point coordinates in the elliptical area to determine the extreme values ​​of the coordinates in two mutually perpendicular directions to delineate the major axis and minor axis of the elliptical area, and use the contact point at the intersection of the major axis and the minor axis as the touch point.

[0075] In the process of executing the touch interaction response, the display device can classify different touch times, touch positions, number of touch points and touch event types, so as to detect the user's touch input gesture, thereby performing different interactive responses for different input gestures. For example, when the number of touch points in the touch trajectory detected by the touch interaction module is 1, the touch event type only includes a down event and an up event, and the time interval between the down event and the up event is less than the single-click event time threshold. In addition, if the touch position change distance of the down event and the up event is less than the jitter distance threshold, it can be determined that the current user's touch input gesture is a click gesture. Based on the click gesture, the display device 200 executes the operation of starting the application according to the icon in the area where the touch position corresponding to the click gesture is located.

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

[0077] In some embodiments, in order to enrich the types of touch interactions supported by the display device, the display device can also perform complex gesture detection based on the dynamic changes in touch time, touch position, number of touch points, and touch event type. For example, when the touch interaction module detects that the touch trajectory of the user input includes multiple touch points, and the touch position of each touch point approaches 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 for the image View, the display device 200 can respond to the grabbing gesture and perform a control action to select and move the image display position.

[0078] In some embodiments, when a display device detects touch data input by a user, it can distribute the touch events in the touch data to the view with the highest display level at the current location, according to the location coordinates corresponding to each touch event in the touch data. For example, when the display device 200 receives touch data detected by the touch interaction module, it can distribute the touch events to the activity of the corresponding window according to the location coordinates of each touch event in the touch data. The activity then distributes the touch events to the View component with the highest display level at the location coordinates. An activity can include multiple different View components.

[0079] To meet users' needs for quick operations, in some embodiments, the display device's applications can be configured with shortcut applications, which can be used to present shortcut views. The shortcut view can be displayed at the highest level of the display device and can be in either a hidden or expanded state. For example, a shortcut view can be the control center view of a control center application; or, alternatively, the home page view of a social networking application. In the hidden state, the user cannot perceive the shortcut interface on the display device's screen; only in the expanded state can the user perceive the shortcut interface on the screen.

[0080] When the quick view is hidden, the display device can display the quick view based on the first layout parameter. Under the first layout parameter, the display device can only display a small transparent view in a specific area of ​​the quick view on the screen. In this case, the user cannot perceive the existence of the quick view. As part of the quick view, the transparent view is displayed at the highest display level of the display device. Therefore, when the user touches the display area of ​​the transparent view, the display device will distribute the touch event generated by the touch to the quick view. That is, in the hidden state, the quick view can receive the user's touch event on the display area of ​​the transparent view based on the highest level transparent view displayed on the display device screen.

[0081] For example, as shown in FIG10 , in the hidden state, the display device 200 may display a transparent view of the quick view in the first intersection area of ​​FIG10 . 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 transparent view in the first intersection area has the highest display level and 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, allowing the quick view to process it.

[0082] When a quick view is expanded, the display device 200 may display the quick view based on a second layout parameter. Under the second layout parameter, the quick view displays the entire quick view on the screen of the display device 200. The entire quick view may include both a transparent view and an opaque view, allowing the user to perceive the existence of the quick view. For example, when the quick view is a control center view, the control center view displayed on the display device 200 in the expanded state may be as shown in FIG14 .

[0083] In order to switch 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 the 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 a down event in the touch operation acts on the display area of ​​the transparent view, and a move event has a displacement greater than a certain threshold in the target direction, when 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 the touch gesture and control the display 260 to present a specific quick view.

[0084] For example, the display area of ​​the transparent view can be located at the top, bottom, left edge, or right edge of the screen, and the target direction can be horizontally left, horizontally right, vertically downward, or vertically upward. When the display area of ​​the transparent view is located at the top of the screen, the target direction can be horizontally downward; when the display area of ​​the transparent view is located at the bottom of the screen, the target direction can be horizontally upward; when the display area of ​​the transparent view is located at the left edge of the screen, the target direction can be horizontally right; when the display area of ​​the transparent view is located at the right edge of the screen, the target direction can be horizontally left.

[0085] It should be noted that the display area and target direction of the transparent view can be any one or more combinations of the above, and the display area and target direction of the transparent area can also be freely adjusted. This application does not impose any restrictions on this.

[0086] In some embodiments, the expanded quick view may provide different functions based on the subview or display control, that is, in some embodiments, the quick view may include at least a combination of one or more of the first subview or display control, and the root node of the first subview is the same. Among them, the first subview that the control center view may include is a first subview with a touchable attribute. When the user clicks the first subview in the quick view with a finger or a stylus, the display device may jump to other views or execute the program corresponding to the subview based on the clicked subview; the display control may be a control with a touchable attribute or a control with a non-touchable attribute. That is, the control center view may include at least a combination of one or more of TextView, Button, ImageView, EditText, ProgressBar, LinearLayout, and RelativeLayout. For example, when the quick view is the control center view, the first subview that the control center view may include is shown in Figure 6. The display device 200 can set a listener for the first subview or display control in a layout file of the control center view, such as an Extensible Markup Language (XML) layout file. The android:onClick attribute is used in the XML layout file to specify that the method for processing touch data corresponding to the click gesture is onMyButtonClick, and the corresponding program is executed through the onMyButtonClick method.

[0087] For ease of understanding, the following embodiments are described by taking as an example a transparent view displayed when the shortcut view is in a hidden state and located at the top of the screen, with a target direction being a horizontal downward direction.

[0088] Obviously, in the hidden state, the quick view will have an intersection area with other views, such as the status bar view, the media playback view displayed in full screen in the media playback application, or the conference view displayed in full screen in the conference application. When other views also include sub-views or display controls that support touch, since the display level of the quick view is higher than the display level of other views, the touch events generated by the user touching in the intersection area can only be distributed to the quick view, making it impossible for other views to implement touch functions normally, resulting in touch conflict problems. For example, the quick view is the control center view, and when the display device 200 displays media in full screen through the media playback view, there is a small intersection area between the button control that can be used to close the current media playback view and the transparent view of the control center view. If the user's hand 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.

[0089] For ease of distinction, the following embodiments refer to the shortcut view as the first view, the view that intersects with the shortcut view as the second view, the subviews and display controls included in the first view are collectively referred to as the first subview, and the subviews and display controls included in the second view are collectively referred to as the second subview.

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

[0091] In some embodiments of the present application, the first view is a control center view and the second view is a status bar view as an example for description, but this is not a limitation. The first view and the second view may be other views.

[0092] In some embodiments, when the control center view is in a hidden state, the display device may display the control center view based on the first layout parameter. At this time, the display hierarchy of each view in the display device 200 may be as shown in FIG8 . In FIG8 , the direction of the screen area from left to right is the direction from the top of the screen to the bottom of the screen. The control center view and the status bar view have an intersection area at the top of the screen, and the intersection area of ​​the control center view is a transparent view. Among them, the display hierarchy of the control center view is higher than the display hierarchy of the status bar view, and the display hierarchy of the status bar view is higher than the display hierarchy of other application views. The display device 200 will distribute the touch data acting on the intersection area to the control center view.

[0093] It should be noted that, in the hidden state, the transparent view displayed by the control center view on the screen can completely overlap with the status bar view, or can also partially overlap. This application does not impose any restrictions on this.

[0094] In some embodiments, when displaying the application view of another application in full screen, the display device can read the screen resolution of the display device and obtain the full-screen display area of ​​the screen based on 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 baseline display area of ​​the application view. As shown in Figure 8, after the display device 200 calculates the baseline display area, it controls the display 260 to display the application view of the other application in the baseline display area.

[0095] In some embodiments, the control center view and the status bar view can be views in the same application, or they can be views of different applications. When the control center view and the status bar view are views of 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 of 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 (Parent View) in application A; or, the control center view can be the root view (Root View) of application A, and the status bar view can be the root view of application B.

[0096] 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 the intersection area, the touch event generated by the touch can only be distributed to the control center view. For example, as shown in Figure 10, 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 of ​​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 view with touchable attributes, the two are prone to touch conflicts. Therefore, some display devices and terminal devices will set the status bar view to a view with non-touchable attributes.

[0097] However, unlike small-screen devices such as mobile phones and tablets, when the resolution of the display device screen is larger, the status bar view in the display device will also occupy a larger display area. The status bar view with non-touchable attributes will reduce the touchable space of the display device, resulting in a decreased user experience.

[0098] Based on the above application scenarios, some embodiments of the present application provide a display device, which may include a display, a touch interaction module connected to the display, a memory and at least one processor. The display may be configured to display a user interface, and the user interface may include a first view and a second view. The display level of the first view may be higher than the display level of the second view, and the first view is displayed based on a 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 touch interaction module may be configured to detect touch data input by a user; the memory may be configured to store computer programs or instructions; and the at least one processor is connected to the display and the memory.

[0099] It should be noted that the first view and the second view provided in this application are both touchable views, which can improve the problem of reduced touchable space mentioned above. The first view can be the shortcut view provided in the above embodiment, and the second view is a view that has an intersection area with the first view.

[0100] For ease of description, in some embodiments of the present application, a touch event data set generated when a user touches the first intersection area is referred to as first touch data.

[0101] As shown in FIG9 , the at least one processor may be configured to execute the computer program or instructions stored in the memory to enable the display device to perform program steps including but not limited to the following:

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

[0103] In some embodiments, after receiving touch data input by a user via a touch interaction module, the display device may detect touch events included in the touch data in response to the touch data. The touch data may include at least a down event and an up event, and the location coordinates of the down event and the up event may be the same or different. The display device may distribute the touch events to the view with the highest display level at that location based on the location coordinates of each touch event in the touch data.

[0104] Among them, the first touch data can be touch data acting on the first intersection area. Therefore, when the display device receives the first touch data, the control system of the display device will distribute the first touch data to the first view with the highest display level in the first intersection area, such as at least one of the aforementioned processes. For example, the first view is the control center view, and the second view is the status bar view. As shown in Figure 10, 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 will distribute the first touch data acting on this area to the control center view.

[0105] In some embodiments, when the first view receives the first touch data, it can record 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.

[0106] 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.

[0107] In some embodiments, after the display device distributes the first touch data to the first view, it may temporarily store the first touch data 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 also needs to determine the view on which the first touch data is expected to act 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 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 the move event has a displacement in the target direction (S9001').

[0108] 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 may respond to the first touch data based on the first view. Therefore, in some embodiments, when the display device responds to the first touch data based on the first view, it may parse the first position coordinates of the movement event in the first touch data. The layout coordinates of the first view may be updated based on the first position coordinates, and the display may be controlled to display the first view according to the layout coordinates, thereby moving the first view within the user interface.

[0109] 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, namely [move; x1, y1, t1]. Then, based on the coordinate distance between the latest movement event and the previous touch event, the layout parameters of the XML layout file corresponding to the first view are updated. When the coordinate distance between the touch point with the latest touch time and the previous touch point is a preset value of pixels, the left and top attributes in the layout parameters are modified. For example, if the preset value is 50, the modification of the left and top attributes in the layout parameters can be expressed as layoutParams.topMargin += 50, and then the setLayoutParams() method is called to update the layout coordinates of the layout parameters. After the display device 200 modifies the layout coordinates in response to the movement event based on the control center view, it deletes the currently processed movement event from the memory to promptly consume the touch event of the first touch data. As shown in Figure 11, when the display device 200 responds to the movement event of the first touch data based on the control center view, it can control the non-transparent view of the center view to move to the display area of ​​the screen following the user's touch operation of sliding downward.

[0110] As shown in Figure 12, in some embodiments, the display device 200 can also receive a lift event of the first touch data based on the first view (S1201). When the user raises his hand, the touch interaction module generates an up event. The up event of the first touch data acts on the first intersection area, so the display device 200 can distribute the lift event of the first touch data to the first view (S1201'), and respond to the lift event based on the first view, read the first height of the first view, and detect the moving distance of the first view in the target direction (S1202). Then calculate the height ratio of the moving distance to the first height (S1203). In other words, since the above-mentioned sliding touch operation may also be a user's erroneous operation, the display device 200 also determines whether it is necessary to slide out all the non-transparent views of the first view by the height of the first view and the moving distance of the first view.

[0111] After the display device 200 calculates the height ratio based on the first view, it determines whether the height ratio is less than the height ratio threshold (S1204); if the height ratio is less than the height ratio threshold, the display 260 is controlled to display the first view according to the first layout parameter so that the first view moves back to the initial position (S1205). At this time, as shown in Figure 13, the portion of the first view displayed in the user interface of the display device 200 is still the transparent view portion, 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 (S1206). 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 shown in Figure 14.

[0112] For example, before the user touches, the user interface of the display device 200 is shown in FIG13, and 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, such as the aforementioned at least one processor, can send 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, the ratio of the moving distance to the first height is calculated. If the moving distance / first height ≥ 0.4, the control center view is displayed in full screen in the user interface, as shown in FIG14, 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 shown in FIG13, the control center view is moved back to the initial position.

[0113] 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.

[0114] In some embodiments, when the display device detects based on the first view that the first touch data does not include a motion event, indicating that the first touch data may be touch data acting on the second view, the display device may send the first touch data to the second view based on the first view, that is, send the first touch data in a directionally manner to the second view through the first view.

[0115] For example, when a user touches the first intersection area and generates a touch event, the first down event is generated in display device 200 at the hand placement location. Display device 200 then distributes the down event to the first view. After receiving the down event, the first view records the location coordinates of the event. If the user does not move the touch location before lifting their hand, display device 200 does not generate a move event. In this case, display device 200 sends data related to the down event to the second view for processing.

[0116] During the touch process described above, the display device may generate one or more down events before the user lifts their hand. For example, if the user places their hand on the first intersection area of ​​the touch screen and continues to press the touch screen, if the user's finger pressure is uneven or there is a slight tremor in the finger, the display device 200 may generate multiple down events before the up event, and the position coordinates of the down events may be discontinuous.

[0117] In some embodiments, when there is only one drop event, the display device may send the location coordinates of the drop event to the second view. When there are multiple drop events, the display device may continuously record the location coordinates of each drop event. Based on the location coordinates of the drop events, the display device calculates the effective range of the drop events and sends the calculated effective range and the location coordinates of the latest drop event in the current touch time to the second view.

[0118] For ease of description, in this embodiment of the present application, the locations of the drop events in the first touch data are collectively referred to as the second location coordinates, and the location coordinates of the drop event with the latest touch time in the first touch data are referred to as the third location coordinates. The following describes the processing process of the first view when there are multiple drop events.

[0119] In some embodiments, when the first touch data does not include the touch point of the move event, the display device records the second position coordinates of the drop 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 his finger on the intersection area of ​​the control center view and the status bar view, and continues to press the touch screen at the drop position; at this time, when the pressure of the user's finger changes, the touch screen will continue to generate multiple down events with different position coordinates due to uneven force, that is, the effective position of the down event jumps on the touch screen. In this process, since the user does not slide or raise his hand, the touch screen will not generate move events and up events. Therefore, before the touch screen generates the first touch data up event, the first touch data will include multiple down events with different position coordinates.

[0120] After recording the second position coordinates of the down event based on the first view, the display device may generate a graphical object based on the second position coordinates to determine the scope of the down event in the first touch data. The graphical object represents the scope of the down event in the first touch data and may be generated based on the recorded second position coordinates using the minimum rectangle principle.

[0121] For example, after the display device 200 distributes the down event to the control center view, the control center view continuously records the second position coordinates of each down event and generates a graphic object based on the recorded second position coordinates, such as a rectangular (rect) object generated based on the minimum rectangle principle. The display device 200 can set the upper left corner coordinates and lower right corner coordinates of the rectangular object according to the touch point with the maximum horizontal coordinate and the minimum horizontal coordinate in the second position coordinates, or the touch point with the maximum vertical coordinate and the minimum vertical coordinate, thereby generating a rectangular object as shown in Figures 15a and 15b. In Figures 15a and 15b, the dotted area is a rectangular object, and the touch points included in the rectangular object correspond to the touch points of each position coordinate of the drop event.

[0122] In order to reduce the error in the display device's recognition of touch data, in some embodiments, after the display device distributes the first touch data to the first view, it can record the position coordinates of the initial drop event in the first touch data based on the first view. The initial drop event can be the down event with the earliest touch time in the first touch data. After recording the position coordinates of the initial drop event, if the first view receives a drop event of the first touch data again, the display device can calculate the touch time difference between the current drop event and the initial drop event based on the first view. If the touch time difference is greater than or equal to the target time threshold, the position coordinates of the current drop event are recorded based on the first view.

[0123] That is, after receiving a user hand-down event, the first view of the display device records the position coordinates of the touch point. When a subsequent down event is received, the touch time difference between the touch point and the hand-down event is determined. When the touch time difference is greater than or equal to the preset target time threshold, the position coordinates of the newly received down event are recorded based on the first view. For example, if the target time threshold is 500ms, when the touch time difference is ≥500ms, the position coordinates of the newly received down event are recorded based on the control center view.

[0124] After the display device generates a graphic object based on the first view, it can record the third position coordinates based on the touch time. The display device can then send the graphic object and the third position coordinates to the second view based on the first view. For example, after the display device 200 generates a graphic object based on the control center view, it can send the position coordinates and the orientation of the graphic object for the down event with the latest touch time based on the control center view to the status bar view, so that the status bar view responds to the first touch data based on the aforementioned data information.

[0125] As shown in Figure 16, in some embodiments, after the second view of the display device receives the graphic object and the third position coordinates sent by the first view, the third position coordinates are read based on the second view (S1601). Then, the display area of ​​the second subview is queried (S1602). The second subview may be a subview included in the second view, and the second subview has the same root node as the second view. It is determined whether the display area is within the subview display area (S1603). If the third position coordinates are within the display area of ​​the second subview, the second subview is marked as a view to be responded to (S1604).

[0126] For example, as shown in Figure 17, a represents the third position coordinate, and the display area of ​​each second subview in the status bar view is a rectangular area. In this case, the third position coordinate and the coordinates of the rectangular area are both referenced to the screen coordinate system. If a is within the display area of ​​a second subview, then that second subview is marked as a view to be responded to.

[0127] As shown in Figure 18, in some embodiments, when the display device marks the second subview as a view to be responded to, it may also set the display state of the second subview to a pressed state, thereby prompting the user that the subview has been selected. Setting the second subview to a pressed state may modify the background image of the second subview or scale the displayed content of the second subview, but the display area of ​​the second subview must remain unchanged.

[0128] In some embodiments, because the coordinate system used by the second view may differ from the screen coordinate system, i.e., the reference coordinates of the upper left corner are different, the display device may also convert the third position coordinates into the view coordinates of the second subview area based on the view coordinate system of the second view when marking the second subview as the view to be responded to. In other words, when the display device responds to a down event in the first touch data based on the second view, it needs to convert the position coordinates of the down event into the position coordinates of the second view, so that the display device can mark the view to be responded to based on the second view.

[0129] After the display device reads the third position coordinates based on the second view, if the third position coordinates are not within the display area of ​​the second subview, it reads the graphic object and marks the view to be responded to based on the graphic object (S1605). In other words, if the down event with the latest touch time in the current first touch data is not within the display area of ​​any subview in the second view, the display device reads the graphic 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 based on the event scope.

[0130] As shown in Figures 16 and 19, the display device 200 can determine the view to be responded to based on the degree of overlap between the graphic object (only a rectangular object is shown as an example in Figure 19) and the display area of ​​the second subview. Therefore, in some embodiments, the display device can also detect the second intersection area of ​​the graphic object and the second subview (S1606) and calculate the reference area based on the second height of the second intersection area (AR2) (S1607). The reference area (AR1) is the area in the graphic object whose height is equal to the second height. The area ratio of the second intersection area to the reference area is then calculated (S1608). It is determined whether the area ratio is greater than the area ratio threshold (S1609). If the area ratio is greater than the area ratio threshold, the second subview can be marked as a view to be responded to (S1610). If the area ratio is less than or equal to the area ratio threshold, the process ends.

[0131] For example, assume that 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 located in the display area of ​​any second sub-view, it reads the graphic object sent by the control center view and queries the second sub-view that intersects with the graphic object. As shown in Figure 19, taking the graphic object as a rectangular object as an example, 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 a view to be responded to based on the status bar view; otherwise, no processing is performed.

[0132] Obviously, since the first touch data is the touch data of the touch point located in the first intersection area, the view with the highest display level in the first intersection area is the first view, and the display device can 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 (S2001'). Therefore, in some embodiments, as shown in Figure 20, the display device can receive the lift event sent by the first view based on the second view (S2001). Then, in response to the lift event, the fourth position coordinates of the lift event are parsed (S2002). It is determined whether the fourth position coordinates are located in the display area of ​​the subview (S2003). If the fourth position coordinates are located in the display area of ​​the view to be responded to, the first touch data is marked as including the target feature to indicate that the current first touch data requires the second view to respond (S2004). Then, the display is controlled to display the third view based on the view to be responded to. Among them, the third view can be a view associated with the view to be responded to.

[0133] In some embodiments, when the display device 200 marks the second subview as a view to be responded to through a third position coordinate or a graphic object, a pending response identifier can be set in the subview. When the status bar view receives an up event sent by the control center view, it can detect the position coordinates of the up event and determine whether the up event is located in the display area of ​​the view to be responded to. If the up event is located in 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 pending response identifier and the pressed state of the view to be responded to.

[0134] For example, as shown in Figure 21, when the view to be responded to is the Bluetooth status view, the display device 200 can control the display 260 to display the Bluetooth settings view associated with the Bluetooth status view based on the Bluetooth status view in the status bar view. The XML layout file of the Bluetooth status view of the display device 200 can include logic for jumping to the Bluetooth settings view on a click event.

[0135] In other embodiments, if the fourth position coordinate is not located in the display area of ​​the view to be responded to, after deleting the pending response identifier of the view to be responded to, and deleting the up event sent by the first view based on the second view (S2005), that is, when the position coordinate of the up event is not located in the display area of ​​the view to be responded to, the second view of the display device does not process the up event.

[0136] As can be seen from the above embodiments, the display device provided in some embodiments of the present application can distribute all of the first touch data to the first view when all touch points in the first touch data act on the first intersection area of ​​the first view and the second view, and determine whether the first touch data includes a move event. If the first touch data includes a move event, the display device can respond to the move event in real time based on the first view, move the first view onto the screen for display, and upon receiving an up event for the first touch data, determine whether to switch the first view to an expanded state based on the movement distance and the height of the first view. If the first touch data does not include a move event, the display device can distribute the first touch data to the second view for processing based on the first view, and then determine the view to be responded to by the current first touch data based on the second view. When the second view receives an up event sent by the first view, it can determine whether to respond to the first touch data according to the view to be responded to based on the relative position of the up event and the view to be responded to, thereby accurately identifying the view on which the first touch data is intended to act.

[0137] Because the user may also touch the display area of ​​the second view other than the first intersection area, in other embodiments of the present application, the touch event data set generated by touching the display area of ​​the second view other than the first intersection area is referred to as second touch data. In the display area of ​​the second view other than the first intersection area, the second view has the highest display level. In this case, the display device can distribute the second touch data to the second view.

[0138] In some embodiments, a display device may distribute second touch data input by a user to a second view. The second touch data may be touch data applied to a display area of ​​the second view excluding the first intersection area. The second touch data may be parsed based on the second view. If the second touch data includes a target feature, the second touch data may be responded to based on the second view.

[0139] For example, when a user touches a display area of ​​the status bar view other than the first intersection area to generate second touch data, the display device 200 can distribute the entire second touch data to the status bar view. In this case, regardless of whether the second touch data includes a move event in the target direction, the display device 200 needs to send all touch data to the status bar view. Upon receiving the second touch data, the status bar view can determine the view to be responded to in the second view based on the position coordinates of the second touch data, and respond to the second touch data through the view to be responded to.

[0140] As shown in Figure 22, in some embodiments, after the display device distributes the second touch data (i.e., the touch event data set generated by the touch in the second view except for the first intersection area) to the second view (S2201'), the fifth position coordinates of the initial drop event in the second touch data can be parsed based on the second view (S2201). The initial drop event of the second touch data can be the drop event with the earliest touch time in the second touch data. Query the display area of ​​the second subview (S2202). Determine whether the fifth position coordinate is located in the subview display area (S2203). If the fifth position coordinate is located in the display area of ​​the second subview, the second subview can be marked as a view to be responded to (S2204). Then, based on the second view, receive the move event or drop event in the second touch data, and parse the sixth position coordinates of the move event or drop event in the second touch data. Determine whether the sixth position coordinate is located in the display area of ​​the view to be responded to (S2205). If the sixth position coordinate is located in the display area of ​​the view to be responded to, maintain the pending response identifier of the view to be responded to (S2206). When the second view receives a lift event of the second touch data and the lift event is located in the display area of ​​the view to be responded to, the display device displays the third view based on the pending response view of the second view; if the sixth position coordinate is not located in the display area of ​​the view to be responded to, delete the pending response identifier of the view to be responded to, and do not perform processing (S2207).

[0141] For example, when a user outputs second touch data in a display area other than the first intersection area in the status bar view, the control system of the display device 200, such as the aforementioned at least one processor, can distribute the complete down event, move event, and up event in the second touch data to the status bar view and parse 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 located in the display area of ​​a 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. If a move event or down event is not located in the display area of ​​the view to be responded to, the pending response flag of the sub-view is deleted, and the pending response view is no longer marked based on the position coordinates of the touch events in the second touch data. If each move event or down event is located in the display area of ​​the view to be responded to, the pending response flag of the sub-view is maintained, and when the touch event of the up event is also located in 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.

[0142] As can be seen from the above embodiments, the display device provided in some embodiments of the present application can distribute all the second touch data to the second view when the second touch data acts on the display area of ​​the second view except the first intersection area. The to-be-responded view is determined by the down event first received by the second view, and when all subsequently received touch events are located in the display area of ​​the to-be-responded view, the to-be-responded view of the second view responds to the second touch data based on the to-be-responded view of the second view, and displays the third view associated with the to-be-responded view, thereby allowing the display device to respond to the second touch data accurately and promptly.

[0143] However, when the user touches, they may also slide back and forth between the first intersection area and the display area of ​​the second view excluding the first intersection area. The display device also needs to judge the touch data generated across these areas to determine the view on which the current touch data is intended to act. For ease of distinction, for the touch event data set generated across areas, touch events located in the first intersection area are collectively referred to as first touch events, and touch events located in the second view excluding the first intersection area are collectively referred to as second touch events.

[0144] In the case where the hand drop location is in a display area other than the first intersection area in the second view, in some embodiments of the present application, the data set where the initial drop event is located in a display area other than the first intersection area in the second view, but there are subsequent touch events located in the first intersection area, is referred to as third touch data. The initial drop event can be the drop event with the earliest touch time in the third touch data, that is, the down event generated by the first hand drop.

[0145] As shown in FIG23 , when the user's hand drops in a display area other than the first intersection area in the second view, in some embodiments, the display device may further distribute the second touch event of the third touch data to the second view in response to the third touch data input by the user (S2301). The third touch data may be touch data indicating that the initial drop event is located in a display area other than the first intersection area in the second view. The display device may further distribute the first touch event of the third touch data to the first view (S2302). The event type of the first touch event is then detected based on the first view (S2303). A determination is made as to whether the event type is a lift event (S2304). If the event type is a lift event, the first touch event is recorded based on the first view (S2305), and the first touch event is sent to the second view based on the first view (S2306). If the event type is a move event or a drop event, the first touch event is deleted (S2307).

[0146] That is to say, when the down event received for the first time is located in the display area other than the first intersection area in the second view, the display device can distribute the second touch event generated in the current area to the second view. During the touch process, if the user's touch position slides to the first intersection area, the display device will distribute the first touch event generated by the first intersection area to the first view. At this time, the display device 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, so the display device can determine 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 does not process it based on the first view; if the event type is an up event, the display device 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 second view's pending response view based on the received up event. After the second view of the display device receives the up event sent by the first view, it executes steps S2201-S2207.

[0147] Obviously, in some embodiments, if the user inputs the third touch data and the lift event occurs in a display area of ​​the second view other than the first intersection area, the display device may directly dispatch the lift event to the second view. After receiving the lift event dispatched by the display device, the second view executes steps S2201-S2207.

[0148] For the case where the user's hand drops in the first intersection area, in some embodiments of the present application, the data set in which the initial drop event is located in the first intersection area but there is a subsequent touch event located in the second view other than the first intersection area can be called fourth touch data.

[0149] In some embodiments, the display device may further distribute the first touch event in the fourth touch data to the first view in response to fourth touch data input by the user. The fourth touch data may be touch data indicating that the initial drop event is located in the first intersection area. After receiving the first touch event, the first view executes steps S9001-S9002. When the user's touch position moves to a display area of ​​the second view other than the first intersection area, the display device generates a second touch event and distributes the second touch event of the fourth touch data to the second view, causing the second view to execute steps S2201-S2207.

[0150] To improve the responsiveness of touch data, in some embodiments, when the display device sends the second touch event in the fourth touch data to the second view based on the first view, it can also detect the movement distance of the first view. If the movement distance of the first view is greater than 0, the display is controlled to display the first view according to the first layout parameters, restoring it to its hidden state; otherwise, no processing is performed.

[0151] As can be seen from the above embodiments, when a user moves back and forth between the display areas of the first and second views, excluding the first intersection area, if the first down event occurs in the display area of ​​the second view, but before the up event occurs, 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 upon receiving the up event. When the first down event occurs in the first intersection area of ​​the first view, the display device executes steps S9001-S9003; and when the user's touch position moves to the second view, steps S2201-S2207 are executed.

[0152] Based on the above-mentioned display device, some embodiments of the present application also provide a touch method for a display device, wherein the display device includes a display, a memory and at least one processor. The display can be configured to display a user interface, and the user interface may include a first view and a second view. The display level of the first view may be higher than the display level of the second view, and the first view is displayed based on a 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 can be connected to a touch interaction module, and the touch interaction module can be used to detect touch data input by the user. Still as shown in FIG9 , the method includes but is not limited to the above-mentioned S9001-S9003, which will not be repeated here.

[0153] As can be seen from the above scheme, the touch method for a display device provided in some embodiments of the present application can distribute the first touch data to the first view in response to the first touch data input by the user. 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 touch data is responded to based on the first view; if the first touch data does not include a movement event in the target direction, the first touch data is sent to the second view based on the first view, and then the first touch data is parsed based on the second view, and when the first touch data includes the target feature, the first touch data is responded to based on the second view. The method can determine the view on which the touch data is expected to act 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 user experience.

[0154] The same and similar parts between the various embodiments in this specification can be referenced to each other and will not be repeated here.

[0155] Finally, it should be noted that the above embodiments are only used to illustrate the solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the solutions described in the aforementioned embodiments, or make equivalent replacements for some or all of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding solutions from the scope of the embodiments of the present application.

Claims

1. A display device, comprising: A display configured to display a user interface, the user interface including a first view and a second view, a display level of the first view being higher than that of the second view, 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; A touch interaction module connected to the display and configured to detect touch data input by a user; A memory configured to store computer programs or instructions; At least one processor connected to the display and the memory and configured to execute the computer programs or instructions to cause the display device to perform: In response to first touch data input by a user, distributing 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, responding 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, sending the first touch data from the first view to the second view and parsing the first touch data based on the second view; And, when the first touch data includes a target feature, responding to the first touch data based on the second view.

2. The display device according to claim 1, wherein when the at least one processor executes responding to the first touch data based on the first view, it is further configured to execute the computer programs or instructions to cause the display device to perform: Parsing first position coordinates of a movement event in the first touch data; Updating layout coordinates of the first view according to the first position coordinates; Controlling 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 at least one processor executes responding to the first touch data based on the first view, it is further configured to execute the computer programs or instructions to cause the display device to perform: Receiving a lifting event of the first touch data based on the first view; In response to the lifting event, reading a first height of the first view and detecting a moving distance of the first view in the target direction; Calculating a height ratio of the moving distance to the first height; If the height ratio is less than a height ratio threshold, controlling 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, controlling the display to display the first view according to second layout parameters, when the first view is displayed based on the second layout parameters, an area of a non - transparent view of the first view is greater than an 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, if the first touch data does not include a movement event in the target direction, the at least one processor performs sending the first touch data from the first view to the second view, and is further configured to execute the computer program or instructions to cause the display device to perform: Record the second position coordinates of the down event in the first touch data based on the first view; Generate a graphic object according to the second position coordinates; Parse the touch time of the down event; Record the third position coordinates according to the touch time, where the third position coordinates are the position coordinates of the down event with the latest touch time in the first touch data; Send the graphic object and the third position coordinates from the first view to the second view.

5. The display device according to claim 4, the at least one processor performs parsing the first touch data based on the second view, and is further configured to execute the computer program or instructions to cause the display device to perform: 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 a view to be responded to; If the third position coordinates are not within the display area of the second sub-view, read the graphic object and mark the view to be responded to according to the graphic object.

6. The display device according to claim 5, the at least one processor performs marking the view to be responded to according to the graphic object, and is further configured to execute the computer program or instructions to cause the display device to perform: Detect a second intersection area between the graphic 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 graphic 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 a view to be responded to.

7. The display device according to claim 6, if the first touch data does not include a movement event in the target direction, the at least one processor is further configured to execute the computer program or instructions to cause the display device to perform: Send the lift event of the first touch data from the first view to the second view; The at least one processor performs responding to the first touch data based on the second view, and is further configured to execute the computer program or instructions to cause the display device to perform: 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 a 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 at least one processor is further configured to execute the computer program or instructions to cause the display device to perform: In response to second touch data input by a user, distribute the second touch data to a second view, where the second touch data is touch data acting on a display area other than the first intersection area in the second view; 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 at least one processor is further configured to execute the computer program or instructions to cause the display device to perform: In response to third touch data input by a user, distribute a second touch event of the third touch data to a second view, where the third touch data is touch data for which an initial falling event acts on a display area other than the first intersection area in the second view, the initial falling event is the earliest falling event in terms of touch time in the third touch data, and the second touch event is a touch event located in a display area other than the first intersection area in the second view; Distribute a 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 an event type of the first touch event based on the first view; If the event type is a lifting event, send the first touch event to the second view based on the first view; If the event type is a moving event or a falling event, delete the first touch event.

10. A touch control method for a display device, the display device including a display configured to display a user interface, the user interface including a first view and a second view, a display level of the first view being higher than a display level of the second view, 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; 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 acting on the first intersection area; If the first touch data includes a moving 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 moving event in the 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.

Images