Screen interaction method and device, medium, intelligent device, program product and vehicle

Abstract

The invention discloses a screen interaction method and device, a medium, an intelligent device, a program product and a vehicle, and the method comprises the steps: responding to a screen touch event, enabling a target control corresponding to the screen touch event to carry out the operation focus linkage processing, and executing the screen touch event. By means of the method, automatic linkage of the operation focus is achieved, it is ensured that execution of the touch event on the target control and synchronization of the operation focus are achieved, user operation is more visual and smoother, and therefore user experience is improved.

Description

Technical Field

[0001] The present invention relates to the field of intelligent terminal technology, and in particular to a screen interaction method, electronic equipment, computer-readable storage medium, intelligent device, computer program product and vehicle. Background Art

[0002] As smart devices such as Android TVs become more popular, users have higher and higher requirements for their operating experience. Smart TVs usually use remote controls as the main interactive tool, and select different controls through focus (focus flow). However, there are significant deficiencies in the interaction between the remote control focus and the touch screen. The touch and operation focus processing are not smooth, and it is impossible to accurately respond to operations according to user intentions. Summary of the invention

[0003] The present invention aims to solve at least one of the technical problems existing in the prior art. To this end, one purpose of the present invention is to provide a screen interaction method, which realizes automatic linkage of operation focus, ensures synchronization of execution of touch events on target controls with operation focus, makes user operation more intuitive and smooth, and thus improves user experience.

[0004] A second objective of the present invention is to provide an electronic device.

[0005] A third object of the present invention is to provide a computer-readable storage medium.

[0006] A fourth objective of the present invention is to provide a smart device.

[0007] A fifth object of the present invention is to provide a computer program product.

[0008] A sixth object of the present invention is to provide a vehicle.

[0009] In order to achieve the above-mentioned purpose, the screen interaction method of the first aspect of the embodiment of the present invention responds to a screen touch event, and the target control corresponding to the screen touch event performs operation focus linkage processing and executes the screen touch event.

[0010] According to the screen interaction method of an embodiment of the present invention, by responding to a screen touch event and performing operation focus linkage processing on the target control, it can ensure that when the user executes the screen touch event, the operation focus on the target control can always be synchronized with the execution of the screen touch event. This linkage processing mechanism automatically adjusts the operation focus by accurately controlling the flow of focus, thereby avoiding focus loss caused by mis-touch or unnecessary operation, thereby improving the user's response speed and accuracy when operating the screen control. Through this method, the present invention effectively ensures the consistency of touch interaction with user intention, making the user more intuitive and smooth during the operation process, thereby improving the user experience. Therefore, the screen interaction method of the present invention realizes accurate and smooth interaction in complex control operations through the synchronous execution of focus linkage processing and screen touch events, and effectively solves the problem of user operation inconvenience caused by improper management of the current operation focus.

[0011] In some embodiments, the screen interaction method further includes: determining a touch operation type of the screen touch event on the target control; and the target control performing operation focus linkage processing according to the touch operation type.

[0012] In some embodiments, the touch operation type includes a click operation; the target control performs operation focus linkage processing according to the touch operation type, including: the target control performs focus processing corresponding to the click operation.

[0013] In some embodiments, the target control is configured with a Touch Listener interface; when the target control monitors the touch event of the click operation through the Touch Listener interface, the target control obtains the operation focus.

[0014] In some embodiments, the touch operation type includes a sliding operation; the target control performs operation focus linkage processing according to the touch operation type, including: the target control performs focus removal processing corresponding to the sliding operation.

[0015] In some embodiments, the target control is a child control in a list parent control; the target control performs focus removal processing in response to the sliding operation, including: when the sliding operation corresponds to an operation of sliding the target control out of the touch range of the list parent control, the target control responds to the sliding operation, and after the target control moves out of the touch range of the list parent control, there is no visible operation focus on the screen.

[0016] In some embodiments, the screen interaction method further includes: after the target control slides out of the touch range of the list parent control, in response to any signal of the remote control, any child control in the list parent control obtains the operation focus.

[0017] In some embodiments, the target control performs defocusing processing in response to the sliding operation, and also includes: when the sliding operation corresponds to an operation of moving the target control within the touch range of the list parent control, the operation focus remains on the target control, and the list parent control responds to the sliding operation.

[0018] In some embodiments, the target control includes multiple indicator controls of a page switching component, the page switching component also includes multiple banner pages, and the multiple indicator controls are set corresponding to the multiple banner pages; the target control performs focus removal processing in response to the sliding operation, including: when the sliding operation corresponds to the action of switching the multiple banner pages, controlling the flow of the multiple indicator controls according to the switched banner page to obtain the operation focus.

[0019] In some embodiments, determining the touch operation type of the screen touch event includes: monitoring a screen touch event stream; and determining the target control and the touch operation type of the screen touch event on the target control according to the screen touch event stream.

[0020] In some embodiments, the screen touch event flow includes a down event; when the down event arrives, the innermost focusable control on the event transmission path of the down event is determined to be the target control.

[0021] In some embodiments, the screen touch event flow also includes a move event, which is after the down event; the target control and the touch operation type of the screen touch event on the target control are determined according to the screen touch event flow, including: when the move event meets the click operation condition, the touch operation type of the screen touch event on the target control is a click operation.

[0022] In some embodiments, the target control is a child control on the event transmission path of the down event; the click operation condition includes that the move event does not act on the parent control on the event transmission path of the down event and is within the click touch range of the target control.

[0023] In some embodiments, determining the target control and the touch operation type of the screen touch event on the target control according to the screen touch event flow also includes: when the move event meets the sliding operation condition, the touch operation type of the screen touch event on the target control is a sliding operation.

[0024] In some embodiments, the sliding operation condition includes that the move event exceeds the click touch range of the target control.

[0025] In some embodiments, the screen touch event flow also includes an up event, and the up event is after the move event; when the up event arrives, the target control listens to the trigger signal for performing operation focus linkage processing and executing the screen touch event.

[0026] In some embodiments, the screen interaction method further includes: when the screen touch event flow meets the click mistake touch determination condition, the target control does not obtain the operation focus and does not respond to the click operation.

[0027] In some embodiments, the conditions for determining a mistaken click touch include at least one of the following: the move event exceeds the click touch range of the target control; the target control is a child control, the parent control of the target control is in a slidable state and the move event corresponds to an action of sliding in a first direction, and the first direction is the slidable direction of the parent control; the target control is a child control, the parent control of the target control is in a slidable state and the move event corresponds to an action of sliding in a second direction, and the second direction is a non-slidable direction of the parent control.

[0028] In some embodiments, the screen interaction method also includes: when the parent control of the target control is in a slidable state and the move event corresponds to a sliding action in a first direction, the parent control responds to a sliding event corresponding to the move event; or, when the parent control of the target control is in a slidable state and the move event corresponds to a sliding action in a second direction, the parent control does not respond to the sliding event corresponding to the move event.

[0029] In some embodiments, before the target control corresponding to the screen touch event performs operation focus linkage processing and executes the screen touch event, the screen interaction method further includes: determining that the target control is a control that can receive focus in the screen touch mode.

[0030] In order to achieve the above-mentioned purpose, the electronic device of the embodiment of the second aspect of the present invention includes: at least one processor; a memory communicatively connected to the at least one processor; the memory stores a computer program executable by the at least one processor, and the at least one processor implements the screen interaction method described in the above embodiment when executing the computer program.

[0031] In an electronic device according to an embodiment of the present invention, at least one processor executes a computer program that implements the screen interaction method described in the above embodiment, and by responding to a screen touch event and performing operation focus linkage processing on the target control, it can ensure that when the user executes a screen touch event, the operation focus on the target control can always be synchronized with the execution of the screen touch event. This linkage processing mechanism automatically adjusts the operation focus by accurately controlling the flow of focus, thereby avoiding focus loss due to accidental touches or unnecessary operations, thereby improving the user's response speed and accuracy when operating the screen control. In this way, the present invention effectively ensures the consistency of touch interaction with user intentions, making the user more intuitive and smooth during the operation process, thereby improving the user experience.

[0032] In order to achieve the above-mentioned purpose, a computer-readable storage medium of an embodiment of the third aspect of the present invention stores a computer program thereon, and when the computer program is executed, the screen interaction method described in the above embodiment is implemented.

[0033] According to the computer-readable storage medium of an embodiment of the present invention, the screen interaction method described in the above embodiment is adopted to realize automatic linkage of operation focus, ensure the synchronization of execution of touch events on target controls and operation focus, make user operations more intuitive and smooth, thereby improving user experience.

[0034] In order to achieve the above-mentioned purpose, the smart device of the fourth aspect of the embodiment of the present invention includes the electronic device described in the above embodiment; or, the smart device includes a touch screen and a controller, and the controller is connected to the touch screen for executing the screen interaction method described in the above embodiment.

[0035] According to the intelligent device of the embodiment of the present invention, the controller is connected to the touch screen, and by executing the screen interaction method described in the above embodiment, by responding to a screen touch event and performing operation focus linkage processing on the target control, it can ensure that when the user executes the screen touch event, the operation focus on the target control can always be synchronized with the execution of the screen touch event. This linkage processing mechanism automatically adjusts the operation focus by accurately controlling the flow of focus, thereby avoiding focus loss due to accidental touch or unnecessary operation, thereby improving the user's response speed and accuracy when operating the screen control. In this way, the present invention effectively ensures the consistency of touch interaction with user intention, making the user more intuitive and smooth during the operation process, thereby improving the user experience.

[0036] In order to achieve the above-mentioned purpose, a computer program product of an embodiment of the fifth aspect of the present invention stores a computer program, and when the computer program is executed, the screen interaction method described in the above embodiment is implemented.

[0037] According to the computer program product of the embodiment of the present invention, by executing the screen interaction method described in the above embodiment, it is possible to realize automatic linkage of the operation focus, ensure the synchronization of the execution of the touch event on the target control and the operation focus, make the user operation more intuitive and smooth, thereby improving the user experience.

[0038] In order to achieve the above-mentioned purpose, a vehicle according to a sixth aspect of an embodiment of the present invention comprises the electronic device described in the above embodiment, or the intelligent device described in the above embodiment.

[0039] According to the vehicle of the embodiment of the present invention, the electronic device or smart device inside thereof adopts the screen interaction method described in the above embodiment, and by responding to a screen touch event and performing operation focus linkage processing on the target control, it can ensure that when the user executes the screen touch event, the operation focus on the target control can always be synchronized with the execution of the screen touch event. This linkage processing mechanism automatically adjusts the operation focus by accurately controlling the flow of focus, thereby avoiding focus loss due to accidental touch or unnecessary operation, thereby improving the user's response speed and accuracy when operating the screen control. Through this method, the present invention effectively ensures the consistency of touch interaction with user intention, making the user more intuitive and smooth during operation, thereby improving the user experience.

[0040] Additional aspects and advantages of the present invention will be given in part in the following description and in part will be obvious from the following description, or will be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The above and / or additional aspects and advantages of the present invention will become apparent and easily understood from the description of the embodiments in conjunction with the following drawings, in which: Figure 1 is a flow chart of a screen interaction method according to an embodiment of the present invention; Figure 2 is a schematic diagram of a banner page and an indicator control for switching banner pages according to an embodiment of the present invention; Figure 3 is an overall flow chart of a screen interaction method according to an embodiment of the present invention; Figure 4 is a block diagram of an electronic device according to an embodiment of the present invention; Figure 5 is a block diagram of a smart device according to an embodiment of the present invention; Figure 6 is a block diagram of a smart device according to yet another embodiment of the present invention; Figure 7 is a block diagram of a vehicle according to one embodiment of the present invention; Figure 8 is a block diagram of a vehicle according to yet another embodiment of the present invention.

[0042] Reference numerals: Vehicle 100; Smart device 101; Electronic device 1; touch screen 2; controller 3; Processor 11; Memory 12. DETAILED DESCRIPTION

[0043] Embodiments of the present invention are described in detail below. The embodiments described with reference to the accompanying drawings are exemplary. Embodiments of the present invention are described in detail below.

[0044] Reference below Figure 1-Figure 3 A screen interaction method according to an embodiment of the present invention is described.

[0045] Figure 1 is a flow chart of a screen interaction method according to an embodiment of the present invention. Figure 1 As shown, the screen interaction method of the embodiment of the present invention at least includes the following steps S1.

[0046] S1, in response to a screen touch event, the target control corresponding to the screen touch event performs operation focus linkage processing and executes the screen touch event.

[0047] In some embodiments, a screen touch event may refer to various interactive behaviors generated by a user by touching the screen, including but not limited to click, slide, double-click, long press, drag, etc. In the interaction of smart devices, a screen touch event is an input form that matches the user's intention, which reflects the direct interaction intention between the user and the device. Therefore, the role of the screen touch event is to transmit the user's operation intention to the device so that the device responds accordingly based on these inputs. Each screen touch event represents a specific operation that the user wants to perform on the device (such as selection, modification, scrolling, etc.). Accurate identification and timely response of screen touch events are the key to improving the device interaction experience. In an embodiment of the present invention, implementing this solution on an Android TV screen can achieve simultaneous support for touch and TV focus, allowing the user's experience on the TV screen to reach the experience level of an Android touch tablet.

[0048] In some embodiments, the screen touch event is identified by the sensor module of the touch screen, and a corresponding event signal is generated and transmitted to the processing unit of the device. Specifically, when the user performs a touch operation on the screen, the sensor module of the touch screen can detect the specific location of the touch on the screen (for example, a certain coordinate point on the screen), pressure, sliding trajectory, and duration of the touch, and convert this information into a screen touch event signal, which is sent to the processing unit of the device for processing.

[0049] In some embodiments, the target control may refer to an element or component in the user interaction interface, an object that the user operates through a screen touch event. The type and function of the target control depends on the user's operation and the design of the interface. The role of the target control is to provide an interface for the user to interact with the device, so that the user can control the behavior and response of the device through physical touch.

[0050] In some embodiments, the operation focus linkage processing may refer to the system automatically adjusting the position and state of the operation focus according to the type of screen touch event and the nature of the target control, thereby achieving more intuitive and smooth user interaction. The purpose of the operation focus linkage processing is to ensure that the operation focus can flow correctly and intelligently between target controls in different operation modes (such as remote control focus loss, touch operation), avoid confusion or interruption in the focus flow process, and ensure that the user's operation intention is accurately identified.

[0051] In some embodiments, before the target control corresponding to the screen touch event performs operation focus linkage processing and executes the screen touch event, the screen interaction method further includes: determining that the target control is a control that can receive focus in the screen touch mode.

[0052] Specifically, all target controls can be set to receive focus (focusableInTouchMode=true). In Android devices such as Android TV screens, focusableInTouchMode is a property that indicates whether a view can receive operation focus in touch mode. When this property is set to true, the view can respond to touch operations and obtain operation focus. For example, when the user clicks the control, the control can obtain operation focus and perform corresponding operations (such as click events).

[0053] Therefore, when all controls that can receive the operation focus have focusableInTouchMode set to true, it is ensured that in the touch operation mode, these controls can respond and receive the operation focus in time without first moving the operation focus to the control through other means (such as the remote control). This setting improves the user's interactive experience in the touch operation mode, making it reach or approach the touch level of tablet devices. This is because in the touch operation mode, each interactive target control can instantly obtain the operation focus, rather than relying on the remote control operation to switch the focus, thereby realizing the automatic linkage between touch and focus flow, so that the touch operation and focus switching are coordinated. This can avoid the user's unnecessary operations in the touch operation mode due to the operation focus not following the touch, thereby improving the intuitiveness of the operation and the smoothness of the user experience.

[0054] According to the screen interaction method of an embodiment of the present invention, by responding to a screen touch event and performing operation focus linkage processing on the target control, it can ensure that when the user executes the screen touch event, the operation focus on the target control can always be synchronized with the execution of the screen touch event. This linkage processing mechanism automatically adjusts the operation focus by accurately controlling the flow of the operation focus, thereby avoiding the loss of focus due to accidental touch or unnecessary operation, thereby improving the response speed and accuracy of the user when operating the screen control. Through this method, the present invention effectively ensures the consistency of touch interaction with user intention, making the user more intuitive and smooth during the operation process, thereby improving the user experience. Therefore, the screen interaction method of the present invention realizes accurate and smooth interaction in complex control operations through the synchronous execution of focus linkage processing and screen touch events, and effectively solves the problem of user operation inconvenience caused by improper management of the current operation focus.

[0055] In some embodiments, the screen interaction method further includes: determining the touch operation type of the screen touch event on the target control, and the target control performs operation focus linkage processing according to the touch operation type. Among them, the touch operation type may include but is not limited to operations such as clicking, sliding, and long pressing. Each touch operation type corresponds to a different user interaction intention, and the system needs to accurately judge the touch type to make an appropriate focus linkage response. The touch operation type can be determined by acquiring the touch signal through the hardware interface or sensor of the touch screen, and then parsing and identifying the signal.

[0056] In some embodiments, the touch operation type includes a click operation. The target control performs operation focus linkage processing according to the touch operation type, including: the target control performs focus processing corresponding to the click operation.

[0057] Among them, click operation is the most common type of touch interaction, which can refer to the user gently pressing a control (such as a button, text box, icon, etc.) on the screen once with a finger and releasing it immediately. Click operation can mean that the user selects a control and wants to activate the function it represents or trigger a corresponding event.

[0058] In some embodiments, the focus acquisition process may mean that after a click operation, the system ensures that the target control obtains the operation focus and performs corresponding processing at the focus position. For example: when clicking on a button, the system can ensure that the button obtains the operation focus and activates the function of the button. When clicking in a text box, the system positions the operation focus in the text box so that the user can start typing. When clicking on a picture or video control, the operation focus can be concentrated on the control to trigger operations such as zooming in, viewing in detail, or playing.

[0059] In some embodiments, the purpose of the focus acquisition process is to ensure that the click operation successfully identifies the target control and accurately sets the operation focus to the control so that the control can respond to further user operations. Through focus linkage processing, the system can ensure that the operation focus and the user's click operation are synchronized, making the user experience smoother and more intuitive.

[0060] In some embodiments, the target control that obtains the operation focus may provide certain visual feedback, such as changing the border color, background color, or adding highlighting, to prompt the user that the control is currently activated.

[0061] In some embodiments, the target control is configured with a Touch Listener interface, and when the target control listens to a touch event of a click operation through the TouchListener interface, the target control obtains the operation focus.

[0062] Among them, the Touch Listener interface is a software interface used to monitor and capture touch events generated by the user on the screen. By implementing or configuring the Touch Listener interface, the target control can sense various touch events, such as clicks, long presses, and slides. This configuration can be achieved in many ways, such as implementing the interface in a programming language, defining touch event processing logic through a callback function, or enabling touch monitoring in an application development platform. When the target control listens to a click operation through the Touch Listener interface, the trigger logic will perform "focus processing", that is, the control becomes the current target control and obtains the operation focus.

[0063] In some embodiments, developers can set a Touch Listener for any View object so that corresponding operations can be performed when the user touches the View. By implementing the onTouch() method of the Touch Listener interface, developers can capture various information of screen touch events, such as touch position, action, and duration, so as to implement some interactive functions, such as clicking, dragging, zooming, sliding, etc.

[0064] In some embodiments, the working principle of TouchListener is based on a monitoring mechanism. When the user touches the screen, the system can call the onTouch() method and pass the detailed information of the screen touch event to the method. Developers can perform corresponding screen touch event processing according to the touch action (such as "press", "move", "lift", etc.) in the onTouch() method. For example, when a click operation is detected, the target control will obtain the operation focus and perform the corresponding action.

[0065] In some embodiments, the Touch Listener interface is not only used for simple click events, but can also be extended to handle complex touch operations. For example, when implementing the drag function in a custom View, the developer can listen to the screen touch event through the TouchListener interface, and update the position of the control according to the movement of the finger in the onTouch() method to achieve the drag effect.

[0066] In some embodiments, the touch operation type includes a sliding operation. The target control performs operation focus linkage processing according to the touch operation type, including: the target control performs focus removal processing corresponding to the sliding operation.

[0067] Among them, a sliding operation is a common gesture in which a user moves a finger on the screen to scroll, switch, or browse content in an interface. This operation involves continuous movement of a finger in horizontal, vertical, or other directions, which is recognized as a sliding gesture and is used to control the focus state or content position change in the interface.

[0068] In some embodiments, the focus process may refer to the operation focus flowing or moving between interface controls during the sliding process, so that the user can see different controls being selected one by one or the operation focus moving along the sliding path during the sliding operation. In some interfaces, the focus process may be similar to moving between different target controls by pressing the Tab key or using the arrow keys. This feature not only enables the user to intuitively perceive the change of the operation focus following the sliding operation, but also performs cleanup operations such as saving user input or validating input data when necessary.

[0069] Therefore, through the focus process, users can clearly perceive the movement of the operation focus and the change of the selected position during the sliding operation, ensuring that the sliding operation is synchronized with the interface response. This mechanism is particularly important when the interface is complex and contains multiple interactive controls, helping users to browse or operate smoothly without losing focus.

[0070] In some embodiments, the target control is a child control in a list parent control. The parent control may be a list-shaped slidable control, that is, a control that can browse content by sliding gestures. Such controls are commonly found in lists, scroll views, or paging controls in various applications, and users can view more items by sliding.

[0071] In some embodiments, the list parent control can be a RecyclerView. Among them, RecyclerView is a control officially provided by Android for displaying large lists of data. Compared with ListView, it has better performance and flexibility. RecyclerView implements flexible data binding and layout management through the Adapter mode, and supports multiple layout methods, such as linear layout, grid layout, and waterfall layout. It uses LayoutManager to quickly implement the effects of ListView, GridView, and waterfall flow, and can set horizontal and vertical display. RecyclerView also provides animation effects to make data addition and deletion more dynamic. In use, RecyclerView needs to be defined in a layout file and specify the width and height of its parent container to match the parent container. Since RecyclerView is not a built-in control in the system SDK, developers need to add its support through dependent libraries. In addition, RecyclerView reuses views through the ViewHolder mechanism to improve the efficiency of list rendering.

[0072] In some embodiments, the list parent control can also be a ListView, which can display items using four different views. With the ListView control, users can organize items into columns with or without column headers and display accompanying icons and text. The display of items can be controlled by the View property, such as standard icons, small icons, list, or report view. Developers can also use the LabelWrap property to control the line wrapping display of labels associated with list items, or manage the item sorting and the appearance of selected items.

[0073] In some embodiments, a list parent control may contain multiple child controls, each of which may be a separate item (eg, entry, item, or component) in the list parent control, and the layout and display of these child controls may be slide-controlled.

[0074] In some embodiments, the target control performs focus removal processing in response to a sliding operation, including: when the sliding operation corresponds to an operation of sliding the target control out of the touch range of the list parent control, the target control responds to the sliding operation, and after the target control moves out of the touch range of the list parent control, there is no visible operation focus on the screen.

[0075] In some embodiments, the screen interaction method further includes: after the target control slides out of the touch range of the list parent control, in response to any signal of the remote control, any child control in the list parent control obtains the operation focus.

[0076] The remote control's arbitrary key signal may refer to any input signal sent by the user through any key on the remote control that can be recognized and processed by the device. The remote control's arbitrary key may be a direction key, a confirmation key, a return key, a home key, a volume control key, a numeric key, or other key positions.

[0077] In some embodiments, after receiving a signal from the remote control, the system can select one of the child controls (such as list items, buttons, or other interactive controls) in the list parent control and assign it the operation focus according to the preset focus control logic. The transfer of the operation focus allows the user to continue to interact with other controls after the target control slides out of the touch range of the list parent control without touching or repositioning the interface. The main function of this design is that on a touch screen, when the target control or child control slides out of the touch range of the slidable control, the originally interactive operation focus will disappear, which may prevent the user from performing further operations. At this time, any key signal of the remote control can quickly reposition the operation focus to a child control in the list parent control, avoiding confusion caused by the user not being able to find the operation focus, and there is no need to re-slide or manually search for the operation focus.

[0078] In some embodiments, any child control may refer to any child control within the parent control of the list. The way in which the operation focus is transferred to these child controls depends on the input of the remote control signal (such as the direction key, the confirmation key, etc.) and the preset focus control rules. The operation focus transfer can jump to the next or previous control of the current target control in sequence, or the operation focus can be set directly to the first or last child control of the list through rules, or transferred to a specified control according to specific logic. Through this design, users can achieve flexible focus management when operating the interface, and maintain a smooth and coherent operation experience regardless of the interaction situation.

[0079] In some embodiments, the target control performs a focus removal process corresponding to the sliding operation, further comprising: when the sliding operation corresponds to an operation of moving the target control within the touch range of the list parent control, the operation focus remains on the target control, and the list parent control responds to the sliding operation. This design can improve the user experience, so that the user does not need to reselect the focus when sliding the content, especially in scenarios where continuous focus on a specific item is required (such as a video playlist or option browsing), thereby improving the user's interaction continuity and convenience.

[0080] In some embodiments, the target control includes a plurality of indicator controls of a page switching component, the page switching component further includes a plurality of banner pages, and the plurality of indicator controls are arranged corresponding to the plurality of banner pages; Among them, the page switching component can be a custom ViewPager. It allows users to switch between multiple Views by sliding left and right gestures. This makes ViewPager a common control for implementing horizontal paging interfaces, such as the welcome page of an application, an image browser, or a carousel. In ViewPager, multiple Views (such as pictures, texts, or custom views) can be filled as pages. Users can switch these pages by sliding gestures, thus experiencing a page-turning effect. The setPageTransformer() method is used to set the switching animation effect for ViewPager. Using this method, developers can customize the transition animation when switching pages to make page switching more vivid and interesting. For example, fade-in and fade-out effects, rotation animations, and scaling animations can be implemented. ViewPager uses Adapter to manage and bind the View to be displayed. The adapter acts as a bridge between the data source and ViewPager, and it defines how pages are created and destroyed. Similar to ListView or GridView, ViewPager also relies on adapters to fill content. PagerAdapter is a specific adapter for ViewPager, which provides methods that need to be overridden, such as instantiateItem() and destroyItem(), to dynamically create and delete pages. Through PagerAdapter, developers can flexibly define page content and implement sliding switching logic.

[0081] In some embodiments, common forms of indicator controls may include paging indicators, dots, bar indicators, or other forms of visual elements, which provide visual feedback based on the user's switching of pages. Each indicator control corresponds to a banner page. For example, in a carousel containing three banner pages, three indicator controls represent these three pages. As the user slides, the indicator control can be dynamically updated to reflect the banner page currently viewed by the user.

[0082] In some embodiments, a banner page is a common form of online advertising that can be located at the top of a web page or on the homepage to attract the user's attention and guide clicks. The banner page can be a dynamic or static image with a high degree of visual appeal, and is often used on e-commerce websites, information websites, etc. to increase website traffic and user interaction.

[0083] In some embodiments, the target control performs a focus-out process corresponding to the sliding operation, including: when the sliding operation corresponds to the action of switching multiple banner pages, controlling the flow of multiple indicator controls to obtain the operation focus according to the switched banner page. Specifically, the switching of the operation focus follows the logic of page switching: when the user switches to the next or previous banner page through a sliding operation, the system can update the operation focus according to the switched page to ensure that the user can always see that the indicator control corresponding to the current page is in a state of obtaining the operation focus. In this way, the user can clearly know the page location he is on through visual cues. For example, when the user slides from banner page 1 to banner page 2, the indicator control corresponding to banner page 1 will lose the operation focus, and the indicator control corresponding to banner page 2 will obtain the operation focus. This control method of the flow of operation focus can ensure that the user always knows the location of the current page and maintains the focus association between pages through interaction.

[0084] In some embodiments, Figure 2 As shown, ViewPager is used for banner (banner ads or pages) switching, and this control and its sub-page controls are customized to be non-focusable, that is, they cannot receive the focus of the remote control or touch as the operation focus object. On the contrary, the indicator control at the bottom of the page is set to be focusable, which means that the operation focus can flow between the indicator controls at the bottom of the page, and when the user uses the remote control or other input devices to operate, the operation focus can switch smoothly between the indicator controls. At the same time, combined with the page switching listener of ViewPager, when the operation focus switches, the page will also switch automatically, thereby realizing the linkage update of the operation focus and the page.

[0085] In general, the touch screen operation experience of the present invention is basically similar to that of an Android tablet, and the user can perform various operations by touching the screen, such as clicking, sliding, etc. This touch mode is very common in modern tablet devices. The user interacts directly with the screen through fingers, and the device responds to the corresponding screen touch events. Although the touch screen operation is similar to the experience of an Android tablet, in some scenarios, the system can handle the flow of operation focus (i.e., the transfer of operation focus between different controls). This flow of operation focus occurs in some specific interaction scenarios. For example, when using a remote control, the operation focus may be transferred from the touch screen mode to the area controlled by the remote control. This means that the operation focus is not only limited to touch operations, but can also be switched to the flow of operation focus controlled by the remote control when necessary.

[0086] However, even if the focus of the operation changes in touch screen mode, this change of focus does not affect the user's touch screen operation experience. Touch screen operation still proceeds as expected, and the focus of the operation changes to coordinate the connection between touch screen and remote control operation. In other words, the existence of the focus of the operation does not make the user feel confused or incoherent, but allows the two control methods (touch screen and remote control) to switch seamlessly.

[0087] Therefore, throughout the interaction process, the operation focus is always within the expected and controllable range, and there will be no focus drift or unclear focus state. The system can ensure that the operation focus is always within the area that the user can understand and control, enhancing the user's operation perception.

[0088] In some embodiments, determining the touch operation type of the screen touch event includes: monitoring the screen touch event stream, and determining the target control and the touch operation type of the screen touch event on the target control according to the screen touch event stream.

[0089] Specifically, a touch event stream can refer to a continuous sequence of events generated when a user interacts with the screen. The system can listen to these touch event streams by implementing the Touch Listener interface. Each event in a touch event stream contains detailed information, such as the time, action type, and location data of the touch. For example, when a user presses the screen with their finger, the system can record the coordinates of the touch point, the timestamp, and the touch action type (such as a press event).

[0090] Furthermore, when the screen touch event stream is monitored, the system needs to determine the target control operated by the user. The target control can refer to the interface element that the user actually interacts with, such as a button, picture, text box, or scroll bar. The system determines the location of the touch through the coordinate information in the touch event stream, and determines which control is the target of the user's touch based on the coordinates. For example, when the user's finger slides across the screen, the system infers the control operated by the user based on the touch location. If the touch area is within the button range, the button is the target control.

[0091] At the same time, according to the screen touch event flow, the system can determine the touch operation type of the screen touch event on the target control, which can include a variety of common interaction methods, such as click, slide, long press, etc. Different touch operation types can trigger different screen responses.

[0092] In some embodiments, the screen touch event stream includes a down event. When a down event arrives, the innermost focusable control on the event transmission path of the down event is determined as the target control. The down event may refer to a touch event generated by the system when a user presses a finger on the touch screen. The down event is the first event in the screen touch event stream, which marks the first contact between the user and the screen.

[0093] In some embodiments, the event transmission path may refer to the path of the event from the initial touch point to each control when the screen touch event occurs. The path reflects the order in which the screen touch event is transmitted from the touch point of the screen to each control layer by layer. In actual operation, the down event can be transmitted according to the hierarchical structure from the touch point to each control on the screen. The screen touch event can start from the outermost container control (such as the parent control) and pass inward layer by layer until it touches the innermost control. In a multi-layer control layout, the screen touch event can be propagated between controls according to the hierarchical relationship of the controls (i.e., whether the control is in the upper or lower layer). The system can determine which control can receive the operation focus during the transmission process.

[0094] In some embodiments, the innermost focusable control may refer to the innermost control on the event transmission path and having focus responsiveness. The focus responsiveness of a control is determined by whether it is clickable or selectable, and also depends on the hierarchical relationship and display state of the control.

[0095] Specifically, when the user's finger presses the screen, the system first identifies the specific location of the touch point, and then traverses from the outer layer of the screen to the inner layer of the screen along the path of the touch point according to the coordinates of the touch point. During the traversal process, the system generates an event transfer path, which includes all the controls that the touch point passes through. From the event transfer path, the system determines and selects the innermost control that can respond to the focus request as the target control.

[0096] In some embodiments, the screen touch event stream also includes a move event, and the move event is after the down event. Determining the target control and the touch operation type of the screen touch event on the target control according to the screen touch event stream includes: when the move event meets the click operation condition, the touch operation type of the screen touch event on the target control is a click operation.

[0097] Among them, the move event may refer to a sequence of events generated when the user's finger moves on the screen after the down event. The move event may include continuous touch point coordinates and timestamp information to record the movement trajectory of the finger on the screen. Specifically, after the user presses the screen, if the finger moves on the screen, the system can continuously capture and record move events. The system calculates the movement trajectory of the user's finger based on the touch point coordinates and timestamp of the move event. If the move event meets the click operation conditions, the system determines the touch operation type as a click operation. After receiving the click operation, the target control can perform corresponding operations according to the preset interaction logic, such as triggering a button click, selecting a control, or popping up a function window.

[0098] In some embodiments, the target control is a sub-control on the event transmission path of the down event, that is, in the transmission path of the screen touch event, the target control is a control located at a deeper level (inner level) in the hierarchical structure. This limitation emphasizes the hierarchical relationship of the event, ensuring that the selection of the target control is accurate and consistent with the actual operation intention of the user. Figure 1 The click operation conditions include that the move event does not act on the parent control on the event transfer path of the down event and is within the click touch range of the target control.

[0099] In some embodiments, the click touch range may be a virtual area of ​​the target control on the screen, and the user's move event will be considered as a valid click on the target control only if it is within the area.

[0100] Specifically, when a user triggers a move event, the scope of the event should not exceed the area where the target control is located, that is, the touch track cannot extend to the parent control range of the target control. In other words, the move operation needs to be limited to the target control and its range to improve the accuracy of control recognition and avoid misjudgment due to the finger sliding to the parent control range. By limiting the click range of child controls, the user experience of screen interaction is improved to ensure that the user's operation intention can be accurately recognized and responded to.

[0101] In some embodiments, the target control and the touch operation type of the screen touch event on the target control are determined according to the screen touch event flow, and further include: when the move event satisfies the sliding operation condition, the touch operation type of the screen touch event on the target control is a sliding operation. The sliding operation condition can be used to clarify the user's intention, distinguish the sliding operation from other operation types by analyzing the characteristics of the move event, and ensure that the sliding operation is only triggered under specific conditions, thereby improving the interactive experience.

[0102] In some embodiments, the sliding operation condition includes the move event exceeding the click touch range of the target control. Specifically, the click touch range is the key basis for the system to distinguish between click operations and sliding operations. When the move event is always within the click touch range, the system may recognize it as a click operation, and once the move event exceeds the range, it may be judged as a sliding operation.

[0103] In some embodiments, the screen touch event stream also includes an up event, which may be an event triggered when the user lifts his finger after completing a touch operation. The up event follows the move event, and it is the last event in the screen touch event stream, marking the end of the current touch operation. Therefore, when the up event arrives, the target control has been clearly determined. The system processes the target control accordingly based on the final touch operation type (such as click, slide, etc.).

[0104] In some embodiments, when an up event arrives, the target control listens to the trigger signal for performing operation focus linkage processing and executing screen touch events. Specifically, when the user presses the screen, the system triggers a down event and locks the target control according to the event transmission path. If the user moves his finger on the screen, the system will trigger a move event, and the system determines the type of touch operation (such as click or slide) based on the movement trajectory. When the user releases his finger, the up event is triggered, marking the end of the touch operation. The system passes the up event to the target control, and the target control can perform focus linkage processing according to the touch operation type. In addition, after receiving the up event, the target control can also trigger a preset operation signal. For example: clicking a button triggers a page jump signal, or sliding a card triggers an animation play signal.

[0105] In some embodiments, down events, move events, and up events are distributed layer by layer in an order from the outside to the inside through the system's dispatchTouchEvent method. Among them, ‌dispatchTouchEvent‌ is an important method in Android, which is used to distribute screen touch events. When a screen touch event occurs, this method can be called to determine whether the current event should be handled by the current view (view) or whether it should be passed to the child view for further processing. The dispatchTouchEvent method belongs to the View class and is used to handle the distribution of screen touch events. This method is first called to determine whether the current view can handle the event. If the current view can handle it, it returns true, indicating that the event has been handled; if it cannot be handled, it returns false and passes the event to the parent view until a view that can handle the event is found.

[0106] In some embodiments, the transmission path of the screen touch event is from Activity to Window, and then to View. Specifically, when a screen touch event is generated, it is first passed to the dispatchTouchEvent method of Activity, then the Activity passes the event to Window, and finally the Window passes the event to the top-level View. In the View hierarchy, events can be passed from outside to inside (parent control (View) to child control (View)) until there is a View that can handle the event.

[0107] Among them, Activity is a component in an Android application, which is used to represent a separate user interface (UI). Each Activity can represent an independent interface on a screen, and the content that the user interacts with is managed by the Activity. An application can contain multiple Activities, and the user switches between different Activities to change the content on the screen. Activity is responsible for starting, pausing, and destroying the application interface. It provides lifecycle methods (such as onCreate(), onStart(), onPause(), etc.) to manage the UI and handle user input. In the process of transmitting screen touch events, the role of Activity is to receive down events, move events, and up events from the system, and pass these events to Window through its dispatchTouchEvent method.

[0108] In some embodiments, Window in Android represents a window on a display screen and is responsible for managing the displayed content. Each Activity has a Window, which is a container displayed on the screen and can be regarded as a visual representation of the Activity. Window is responsible for drawing views to the screen and managing events that interact with the user. Each Window has an event delivery chain. When a touch event occurs, Window is responsible for passing these events to the UI component (View) hierarchy until the event is processed by a View. In the process of event delivery, the main responsibility of Window is to pass the screen touch event to the View layer, or in some cases, intercept and process the event (such as event distribution or consumption).

[0109] In some embodiments, the screen interaction method further includes: when the screen touch event flow meets the click mistouch judgment condition, the target control does not obtain the operation focus and does not respond to the click operation. Among them, the click mistouch may refer to the user's touch operation failing to meet the expected click condition, which may be due to environmental factors during touch, finger sliding, mis-touching other parts of the screen, or mis-operation on the touch screen. For example, when the user tries to click a button, he accidentally slides or lightly touches the wrong area, causing the touch event to be unable to be correctly identified as a valid click operation.

[0110] In some embodiments, the click false touch judgment condition is a standard set by judging the characteristics of the screen touch event, and these standards are used to distinguish between normal click operations and false touches. By setting the click false touch judgment condition, in a normal click operation, when a user clicks a control, the target control can obtain the operation focus and can perform operations related to the target control. However, when a false touch is triggered, the target control will not obtain the operation focus, which means that the target control will not become the current focus control and the user cannot interact with it. This mechanism helps to improve the stability of the system and prevent unnecessary responses caused by false touches.

[0111] In some embodiments, the click accidental touch determination condition includes at least one of the following: First, the move event exceeds the click and touch range of the target control.

[0112] Second, the target control is a child control, the parent control of the target control is in a slidable state and the move event corresponds to a sliding action in the first direction, and the first direction is the slidable direction of the parent control. Third, the target control is a child control, the parent control of the target control is in a slidable state and the move event corresponds to an action of sliding in a second direction, and the second direction is a non-slidable direction of the parent control.

[0113] In some embodiments, when the move event exceeds the click touch range of the target control, the target control does not obtain the operation focus and does not respond to the click operation.

[0114] In some embodiments, when the parent control of the target control is in a slidable state and the move event corresponds to an action of sliding in a first direction, the parent control responds to the sliding event corresponding to the move event, and the target control does not obtain the operation focus and does not respond to the click operation. This can avoid triggering the sliding of the parent control and the click operation of the target control at the same time. Even if the user's finger touches the target control, the target control will not respond to the click operation. In addition, the target control will not obtain the focus at this time, ensuring that the sliding event can be correctly assigned to the parent control without unnecessary focus switching, thereby providing a more accurate interactive experience.

[0115] In some embodiments, when the parent control of the target control is in a slidable state and the move event corresponds to an action of sliding in the second direction, the parent control does not respond to the sliding event corresponding to the move event. At this time, it is also possible to determine whether the target control responds to the click operation and obtains the operation focus by judging whether the action of sliding in the second direction corresponding to the move event exceeds the click touch range of the target control. If it exceeds the click touch range of the target control, the target control does not respond to the click operation and does not obtain the operation focus. If it does not exceed the click touch range of the target control, the target control responds to the click operation and obtains the operation focus.

[0116] In some embodiments, the present invention is effective only for controls that can obtain operation focus and have click monitoring set. For controls that do not meet this condition, touch events are neither intercepted nor consumed, which means that no click operation or focus switching will be performed.

[0117] Figure 3 is an overall flow chart of a screen interaction method according to an embodiment of the present invention. Figure 3 As shown, the overall process of the screen interaction method includes at least the following steps S10-S16.

[0118] S10, in response to a screen touch event, determining a touch operation type of the screen touch event on a target control.

[0119] S11, determine whether the touch operation type is a sliding operation, if so, proceed to step S12, if not, proceed to step S13.

[0120] S12, the target control performs a focus removal process corresponding to the sliding operation.

[0121] S13, monitoring the screen touch event flow consisting of down events, move events and up events.

[0122] S14, determine whether the move event meets the click operation condition, if it does, go to step S15, if not, go to step S16.

[0123] S15, determining that the touch operation type is a click operation, and performing focus processing on the target control corresponding to the click operation.

[0124] S16, the touch operation type is neither a slide operation nor a click operation, and no response is given.

[0125] In general, by judging the type of touch operation, the system can intelligently distinguish different types of touch events (such as clicks, slides, etc.), so as to handle each operation in a targeted manner. According to the type of touch operation, the system further processes the corresponding screen touch event and performs operation focus linkage processing on the target control. In this process, the system can dynamically adjust the flow of operation focus according to the different types of touch operations to ensure that the operation focus can flow reasonably between different controls. Through this linkage mechanism, the loss of focus caused by accidental touch or unnecessary operation is avoided, the consistency of touch interaction with user intention is ensured, and user operation is more intuitive and smooth, thereby improving the user experience.

[0126] In some embodiments, the screen interaction method of the embodiment of the present invention is applicable to Android TV screens. The method can support touch and TV focus functions at the same time. For example, for click touch, the TV screen can achieve a single click to make the clicked control focus and respond to the click event. For sliding touch, for example, scenario 1: the focus is on an itemView (project view) of RecyclerView, slide the recyclerView, and slide the focus itemView out of the screen range. At this time, there is no visible focus on the screen. Press any direction key or other key on the remote control, and the focus automatically returns to the first itemView visible in the recyclerView; for another example, scenario 2: for ViewPager and the bottom focus indicator, when the touch slide ViewPager switches pages, the bottom focus indicator also transfers the focus according to the switching of the ViewPager page, indicating the current ViewPager display page. And. The two interaction modes can be switched smoothly, providing a friendly user experience. In touch mode, the user's operating experience can reach the same level as that of an Android touch tablet, so that the user can flexibly choose to use touch or remote control for operation, which improves the convenience and comfort of interaction.

[0127] In other embodiments, the screen interaction method of the embodiment of the present invention is also applicable to the entire smart cockpit platform, which includes a central control screen, a co-pilot screen, a rear screen, and all integrated TV tablets. TV focus and screen touch can all be supported. In some embodiments, a remote control can be integrated into the steering wheel. The screens of the entire platform can be operated by remote control like a TV, and screen touch at the shielding level can be supported. In addition, using the screen interaction method of the above embodiment, the user's operating experience of the screen of the entire platform in touch mode can reach the same level as that of an Android touch tablet, and the user can flexibly choose to use touch or remote control for operation, which improves the convenience and comfort of interaction between each screen in the cockpit.

[0128] Reference below Figure 4 An electronic device according to an embodiment of the present invention is described.

[0129] Figure 4 is a block diagram of an electronic device according to an embodiment of the present invention, such as Figure 4 As shown, the electronic device 1 according to the embodiment of the present invention includes at least one processor 11 and a memory 12 .

[0130] In some embodiments, at least one processor 11 may be one processor 11, or may be two processors 11, three processors 11, five processors 11, or multiple processors 11. The processor 11 may be a single-core or multi-core processor 11, responsible for executing the screen interaction method in the memory 12. The processor 11 may be a central processing unit (CPU), a graphics processing unit (GPU), or a digital signal processor (DSP) in the electronic device 1. It depends on the design and purpose of the electronic device 1.

[0131] In some embodiments, the memory 12 is a device for storing data and programs, and may be a random access memory (RAM), a read-only memory (ROM), a flash memory or other storage medium. It is communicatively connected to at least one processor 11 to provide computing programs and store runtime data.

[0132] In some embodiments, the memory 12 stores a computer program that can be executed by at least one processor 11, and the at least one processor 11 implements the screen interaction method described in the above embodiment when executing the computer program.

[0133] According to the electronic device 1 of the embodiment of the present invention, at least one processor 11 executes a computer program that implements the screen interaction method described in the above embodiment, and by responding to a screen touch event and performing operation focus linkage processing on the target control, it can ensure that when the user executes the screen touch event, the operation focus on the target control can always be synchronized with the execution of the screen touch event. This linkage processing mechanism automatically adjusts the operation focus by accurately controlling the flow of focus, thereby avoiding the loss of focus due to accidental touch or unnecessary operation, thereby improving the user's response speed and accuracy when operating the screen control. In this way, the present invention effectively ensures the consistency of touch interaction with user intention, making the user more intuitive and smooth during the operation process, thereby improving the user experience.

[0134] The embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed, the screen interaction method described in the above embodiment is implemented. The specific implementation process of the screen interaction method can refer to the description of the above embodiment.

[0135] According to the computer-readable storage medium of an embodiment of the present invention, the screen interaction method described in the above embodiment is adopted to realize automatic linkage of operation focus, ensure the synchronization of execution of touch events on target controls and operation focus, make user operations more intuitive and smooth, thereby improving user experience.

[0136] Reference below Figure 5-Figure 6 A smart device according to an embodiment of the present invention is described.

[0137] Figure 5 is a block diagram of an intelligent device according to an embodiment of the present invention. Figure 5 As shown, the smart device 101 includes the electronic device 1 described in the above embodiment, and the processor 11 in the electronic device 1 can execute the program related to the screen interaction method described in the above embodiment. Its function is to process the user's touch operation, respond to the interface according to the predefined interaction rules, and control the focus linkage, control response and other behaviors.

[0138] or, Figure 6 is a block diagram of an intelligent device according to another embodiment of the present invention. Figure 6 As shown, the smart device 101 includes a touch screen 2 and a controller 3, and the controller 3 is connected to the touch screen 2 to execute the screen interaction method described in the above embodiment. For example, the controller 3 can receive a touch signal from the touch screen 2, identify the operation type (click, slide, long press, etc.), and perform focus management, page switching, etc. according to the screen interaction method.

[0139] In some embodiments, the smart device 101 may be an electronic device 1 with a screen interaction function, such as a smart TV. The smart TV may be equipped with a large touch screen 2 or a remote control for interaction, and may perform a variety of screen interaction operations through a processor 11 or a controller 3, such as sliding pages, clicking to select, or long pressing to perform specific operations. The smart TV enables users to conveniently browse and select different content, such as channels, applications, and settings, through the screen interaction method of the above embodiment.

[0140] According to the smart device 101 of the embodiment of the present invention, the controller 3 is connected to the touch screen 2, and by executing the screen interaction method described in the above embodiment, by responding to a screen touch event and performing operation focus linkage processing on the target control, it can ensure that when the user executes the screen touch event, the operation focus on the target control can always be synchronized with the execution of the screen touch event. This linkage processing mechanism automatically adjusts the operation focus by accurately controlling the flow of focus, avoiding the loss of focus due to accidental touch or unnecessary operation, thereby improving the user's response speed and accuracy when operating the screen control. In this way, the present invention effectively ensures the consistency of touch interaction with user intention, making the user more intuitive and smooth during the operation process, thereby improving the user experience.

[0141] The embodiment of the present invention further provides a computer program product, which stores a computer program. When the computer program is executed, the screen interaction method described in the above embodiment is implemented.

[0142] In some embodiments, a computer program product may refer to a medium containing computer program codes, which, once loaded and executed, can implement specific functions or methods. In the present invention, the computer program product stores the screen interaction methods described in the above embodiments, which involve processing, judging and responding to the user's screen touch events on a touch screen device.

[0143] According to the computer program product of the embodiment of the present invention, by executing the screen interaction method described in the above embodiment, it is possible to realize automatic linkage of the operation focus, ensure the synchronization of the execution of the touch event on the target control and the operation focus, make the user operation more intuitive and smooth, thereby improving the user experience.

[0144] Reference below Figure 7-Figure 8 A vehicle according to an embodiment of the present invention is described.

[0145] Figure 7 is a block diagram of a vehicle according to an embodiment of the present invention, such as Figure 7As shown, the vehicle 100 includes the electronic device 1 described in the above embodiment, and the processor 11 in the electronic device 1 can handle various tasks, including data input, signal processing, decision logic, etc. In the screen interaction method, the function of the processor 11 is to generate control instructions according to screen touch events, screen inputs, etc., and determine how the screen responds to user inputs.

[0146] Figure 8 is a block diagram of a vehicle according to yet another embodiment of the present invention, Figure 8 As shown, the vehicle 100 includes the smart device 101 described in the above embodiment. After receiving the data from the touch screen 2, the controller 3 in the smart device 101 can parse the data and execute the corresponding screen interaction method according to the computer program. For example, the controller can determine whether the touch is within the valid touch area and whether it meets the condition of false touch.

[0147] In some embodiments, vehicle 100 is equipped with a full smart cockpit platform, which includes a central control screen, a co-pilot screen and a rear screen, supports TV focus and screen touch, and the steering wheel with an integrated remote control can switch between remote control and touch operations, and supports shielded level screen touch.

[0148] According to the vehicle 100 of the embodiment of the present invention, the electronic device 1 or smart device 101 inside thereof adopts the screen interaction method described in the above embodiment, and by responding to a screen touch event and performing operation focus linkage processing on the target control, it can ensure that when the user executes the screen touch event, the operation focus on the target control can always be synchronized with the execution of the screen touch event. This linkage processing mechanism automatically adjusts the operation focus by accurately controlling the flow of focus, avoiding the loss of focus due to accidental touch or unnecessary operation, thereby improving the user's response speed and accuracy when operating the screen control. In this way, the present invention effectively ensures the consistency of touch interaction with user intention, making the user more intuitive and smooth during the operation process, thereby improving the user experience.

[0149] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example.

[0150] Although the embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the claims and their equivalents.

Claims

1. A screen interaction method, characterized in that: include: In response to a screen touch event, a target control corresponding to the screen touch event performs operation focus linkage processing and executes the screen touch event.

2. The screen interaction method according to claim 1, characterized in that: The screen interaction method further includes: Determine the touch operation type of the screen touch event on the target control; The target control performs operation focus linkage processing according to the touch operation type.

3. The screen interaction method according to claim 2, characterized in that: The touch operation type includes a click operation; The target control performs operation focus linkage processing according to the touch operation type, including: the target control performs focus acquisition processing corresponding to the click operation.

4. The screen interaction method according to claim 3, characterized in that: The target control is configured with a Touch Listener interface; When the target control monitors the touch event of the click operation through the Touch Listener interface, the operation focus is obtained.

5. The screen interaction method according to claim 2, characterized in that: The touch operation type includes a sliding operation; The target control performs operation focus linkage processing according to the touch operation type, including: the target control performs focus removal processing corresponding to the sliding operation.

6. The screen interaction method according to claim 5, characterized in that: The target control is a child control in the list parent control; The target control performs a focus removal process corresponding to the sliding operation, including: When the sliding operation corresponds to an operation of sliding the target control out of the touch range of the list parent control, the target control responds to the sliding operation, and after the target control moves out of the touch range of the list parent control, there is no visible operation focus on the screen.

7. The screen interaction method according to claim 6, characterized in that: The screen interaction method further includes: After the target control slides out of the touch range of the list parent control, in response to any signal of the remote controller, any child control in the list parent control obtains the operation focus.

8. The screen interaction method according to claim 6, characterized in that: The target control performs a focus removal process corresponding to the sliding operation, further comprising: When the sliding operation corresponds to an operation of moving the target control within the touch range of the list parent control, the operation focus remains on the target control, and the list parent control responds to the sliding operation.

9. The screen interaction method according to claim 5, characterized in that: The target control includes a plurality of indicator controls of a page switching component, the page switching component also includes a plurality of banner pages, and the plurality of indicator controls are arranged corresponding to the plurality of banner pages; The target control performs a focus removal process corresponding to the sliding operation, including: When the sliding operation corresponds to an action of switching the plurality of banner pages, the plurality of indicator controls are controlled to transfer according to the switched banner page to obtain the operation focus.

10. The screen interaction method according to any one of claims 2 to 9, characterized in that: Determining the touch operation type of the screen touch event includes: Monitor screen touch event stream; The target control and the touch operation type of the screen touch event on the target control are determined according to the screen touch event flow.

11. The screen interaction method according to claim 10, characterized in that: The screen touch event stream includes a down event; When the down event arrives, the innermost focusable control on the event transfer path of the down event is determined as the target control.

12. The screen interaction method according to claim 11, characterized in that: The screen touch event stream also includes a move event, and the move event is after the down event; Determining the target control and the touch operation type of the screen touch event on the target control according to the screen touch event flow includes: When the move event meets the click operation condition, the touch operation type of the screen touch event on the target control is a click operation.

13. The screen interaction method according to claim 12, characterized in that: The target control is a sub-control on the event transfer path of the down event; The click operation condition includes that the move event does not act on a parent control on the event transfer path of the down event and is located within the click touch range of the target control.

14. The screen interaction method according to claim 12, characterized in that: Determining the target control and the touch operation type of the screen touch event on the target control according to the screen touch event flow, further comprising: When the move event meets the sliding operation condition, the touch operation type of the screen touch event on the target control is a sliding operation.

15. The screen interaction method according to claim 14, characterized in that: The sliding operation condition includes that the move event exceeds the click touch range of the target control.

16. The screen interaction method according to claim 12, characterized in that: The screen touch event stream also includes an up event, and the up event is after the move event; When the up event arrives, the target control monitors the trigger signal for performing operation focus linkage processing and executing the screen touch event.

17. The screen interaction method according to claim 12, characterized in that: The screen interaction method further includes: When the screen touch event flow meets the click accidental touch determination condition, the target control does not acquire the operation focus and does not respond to the click operation.

18. The screen interaction method according to claim 17, characterized in that: The click accidental touch determination condition includes at least one of the following: The move event exceeds the click and touch range of the target control; The target control is a child control, the parent control of the target control is in a slidable state and the move event corresponds to an action of sliding in a first direction, and the first direction is the slidable direction of the parent control; The target control is a child control, the parent control of the target control is in a slidable state, and the move event corresponds to an action of sliding in a second direction, where the second direction is a non-slidable direction of the parent control.

19. The screen interaction method according to claim 18, characterized in that: The screen interaction method further includes: When the parent control of the target control is in a slidable state and the move event corresponds to a sliding action in a first direction, the parent control responds to a sliding event corresponding to the move event; Alternatively, when the parent control of the target control is in a slidable state and the move event corresponds to a sliding action in the second direction, the parent control does not respond to a sliding event corresponding to the move event.

20. The screen interaction method according to any one of claims 1 to 9, characterized in that: Before the target control corresponding to the screen touch event performs operation focus linkage processing and executes the screen touch event, the screen interaction method further includes: determining that the target control is a control that can receive focus in the screen touch mode.

21. An electronic device, characterized in that: include: at least one processor; a memory communicatively coupled to the at least one processor; The memory stores a computer program that can be executed by the at least one processor, and when the at least one processor executes the computer program, the screen interaction method described in any one of claims 1-20 is implemented.

22. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed, the screen interaction method described in any one of claims 1-20 is implemented.

23. A smart device, characterized in that: The smart device comprises the electronic device according to claim 21; Alternatively, the smart device includes a touch screen and a controller, and the controller is connected to the touch screen and is used to execute the screen interaction method described in any one of claims 1-20.

24. A computer program product, characterized in that The computer program product stores a computer program, and when the computer program is executed, the screen interaction method according to any one of claims 1 to 20 is implemented.

25. A vehicle, characterized in that: The vehicle includes the electronic device according to claim 21 or the smart device according to claim 23.

Images