WO2023245526A1

WO2023245526A1 - Desktop element operation method, electronic device and intelligent interaction tablet

Info

Publication number: WO2023245526A1
Application number: PCT/CN2022/100601
Authority: WO
Inventors: 王家宇
Original assignee: 广州视源电子科技股份有限公司; 广州视源创新科技有限公司
Priority date: 2022-06-23
Filing date: 2022-06-23
Publication date: 2023-12-28
Also published as: CN116420138A

Abstract

A desktop element operation method, an electronic device, and an intelligent interaction tablet. The desktop element operation method provides a software development kit, and the software development kit is used for providing a functional interface in a desktop process. The desktop element operation method comprises: monitoring a trigger event for a desktop element (S31), the trigger event representing an event that triggers an element process corresponding to the desktop element to perform operation control on the desktop element; and, if the trigger event is detected, the element process corresponding to the desktop element determining operation control matching the type of the trigger event and calling a functional interface to execute the corresponding operation control on the desktop element by means of a desktop process (S32). In the method, the desktop element has relatively rich operation control functions.

Description

Desktop element operating method, electronic device and intelligent interactive tablet

Technical field

The invention relates to the field of display technology, and in particular to a desktop element operating method, an electronic device and an intelligent interactive tablet.

Background technique

The intelligent interactive tablet is an integrated device that uses touch technology to control the content displayed on the display tablet and realize human-computer interaction. It is widely used in fields such as education and teaching, corporate meetings, and commercial displays.

At present, smart interactive tablets are generally equipped with the Android operating system. The Android operating system provides functional interfaces to developers, allowing third-party applications to register desktop elements to the desktop process and display the registered desktop elements through the desktop. However, the operation control function for desktop elements is relatively simple.

Contents of the invention

In view of this, embodiments of the present invention provide a desktop element operating method, an electronic device, an intelligent interactive tablet, and a computer-readable storage medium, and the desktop elements have rich operating control functions.

In one aspect, the present invention provides a desktop element operating method and a software development toolkit, which is used to provide functional interfaces in the desktop process; the method includes:

Monitor triggering events for desktop elements, where the triggering events represent events that trigger the element process corresponding to the desktop element to operate and control the desktop element;

If the trigger event is monitored, the element process corresponding to the desktop element determines the operation control that matches the type of the trigger event, and calls the functional interface to execute the corresponding operation on the desktop element through the desktop process. operational control.

In some embodiments, the functional interface includes an operation interface, and the triggering event includes an element triggering event received by the desktop element, and the element triggering event is monitored by the desktop process, wherein,

If the desktop process monitors the element trigger event, it returns a trigger message to the element process. The trigger message includes a trigger type identifier, and the trigger type identifier represents the type of the element trigger event;

The element process determines the operation control that matches the trigger type identifier, and calls the operation interface to perform corresponding operation control on the desktop element through the desktop process.

In some embodiments, before the desktop process listens to the element trigger event, the method further includes:

The element process registers the element triggering event that needs to be monitored to the desktop process, and the desktop process monitors the registered element triggering event.

In some embodiments, the functional interface includes a listening interface, and the element triggering events include at least one of touch events, key events, input events, focus change events, and click events for desktop elements;

Registering the element-triggered events that need to be monitored to the desktop process includes:

If the element triggering event is at least one of a touch event, a key event, an input event, and a focus change event, the element process calls the listening interface and registers the element triggering event that needs to be monitored in the desktop process;

If the element triggering event is a click event, the element process calls the system's native software development tool kit to register the click triggering event in the desktop process.

In some embodiments, before the element process registers the element trigger event that needs to be monitored to the desktop process, the method further includes:

Register the desktop element in the desktop process so that the desktop element is displayed by the desktop process, where:

The element process calls the system's native software development tool kit to register the desktop element in the desktop process; or

The functional interface provided by the software development toolkit includes a registration interface. The element process calls the registration interface, and the software development toolkit calls the system's native software development toolkit, and registers everything in the desktop process. Desktop elements.

In some embodiments, when there are multiple desktops and the desktop process listens to the registered element triggering an event, the method further includes:

The desktop process determines the desktop identifier of the desktop where the desktop element that receives the element trigger event is located, sets the desktop identifier in the trigger message, and returns it to the element process, so that the element process can The desktop identification determines the operation control matching the trigger type identification for the desktop element of the corresponding desktop.

In some embodiments, the element process corresponding to the desktop element determines the operation control that matches the type of the trigger event, including:

Determining, by the element process, the current element state of the desktop element;

Based on the current element state and based on the type of the triggering event, an operation control for adjusting the desktop element from the current element state to the next element state is determined.

On the other hand, the present invention also provides an electronic device. The electronic device provides a software development toolkit, and the software development toolkit is used to provide a functional interface in a desktop process; the electronic device includes:

The event listening module monitors triggering events for desktop elements, where the triggering event represents an event that triggers the element process corresponding to the desktop element to operate and control the desktop element;

Desktop operation module, if the trigger event is monitored, the element process corresponding to the desktop element determines the operation control that matches the type of the trigger event, and calls the functional interface to control the operation of the trigger event through the desktop process. Desktop elements perform corresponding operational controls.

The event listening module is specifically configured to: if the desktop process monitors the element trigger event, return a trigger message to the element process, where the trigger message includes a trigger type identifier, and the trigger type identifier represents the element trigger. type of event;

The desktop operation module is specifically configured to: the element process determine the operation control that matches the trigger type identifier, and call the operation interface to perform corresponding operation control on the desktop element through the desktop process.

In some embodiments, before the desktop process listens to the element trigger event, the event listening module is also used to:

The event monitoring module is specifically used for:

In some embodiments, before the element process registers the element-triggered event that needs to be monitored to the desktop process, the event listening module is also used to:

In some embodiments, when there are multiple desktops and the desktop process listens to the registered element triggering an event, the event listening module is also used to:

In some embodiments, the desktop operation module is specifically used to:

Another aspect of the present invention also provides a computer-readable storage medium. The computer-readable storage medium is used to store a computer program. When the computer program is executed by a processor, the method as described above is implemented.

On the other hand, the present invention also provides an intelligent interactive tablet. The intelligent interactive tablet includes a processor and a memory. The memory is used to store a computer program. When the computer program is executed by the processor, the above-mentioned functions are implemented. Methods.

In the technical solutions provided by the above embodiments of the present application, by providing a software development toolkit, the element process corresponding to the desktop element determines the operation control that matches the type of the triggering event, and it is possible to trigger the desktop element through a variety of triggering events. Execute operation control, and different types of trigger events can have corresponding operation controls respectively. The operation control functions of desktop elements are richer.

Description of the drawings

The features and advantages of the present invention will be more clearly understood by referring to the accompanying drawings, which are schematic and should not be construed as limiting the invention in any way, in which:

Figure 1 shows a schematic diagram of desktop elements on a desktop;

Figure 2 shows a schematic flow chart of some technologies for operating and controlling desktop elements;

Figure 3 shows a schematic flowchart of a desktop element operating method provided by an embodiment of the present application;

Figure 4 shows a schematic flow chart for operating and controlling desktop elements provided by one embodiment of the present application;

Figure 5 shows a detailed schematic diagram of the desktop element "Message" in Figure 4;

Figure 6 shows a schematic structural diagram of an electronic device provided by an embodiment of the present application;

Figure 7 shows a schematic structural diagram of an intelligent interactive tablet provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments These are some embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative efforts fall within the scope of protection of the present invention.

Before explaining the technical solution of this application, desktop elements will be explained first. Please refer to Figure 1, which is a schematic diagram of desktop elements on a desktop. Generally speaking, desktop elements can be content displayed through the desktop, including but not limited to the interface of software tools displayed on the desktop, application startup icons, and application folders composed of several application startup icons. wait. For example, in Figure 1, the content displayed as Application 1, Application 2, time and date, information, and buttons can be collectively referred to as desktop elements. Among them, the content displayed as application 1 and application 2 can be the startup icon of the application. Click the startup icon to start the corresponding application process. The content displayed as time and date, information, and buttons can be the interface of a software tool displayed on the desktop. Through the interface of the software tool, you can view the time, date, information, or perform key operations on the desktop. In some embodiments, desktop processes may provide operational control over desktop elements. For example, the desktop process can control the arrangement position, display color, etc. of desktop elements on the desktop.

Generally, desktop elements can be divided into two categories. One type may be desktop elements provided by desktop processes, such as application startup icons and application folders composed of several application startup icons. The functionality of this type of desktop element is provided by the desktop process. Desktop processes can actively control this type of desktop elements. In Figure 1, launch icons shown as Application 1 and Application 2 may be first type desktop elements. The other type is desktop elements that are registered by other element processes in the desktop process and displayed on the desktop. The functions of such desktop elements are provided by the element process and are not directly related to the desktop process. The desktop process can operate and control desktop elements based on the information provided by the element process. For example, assuming that the element process corresponding to desktop element 1 is element process 1, and element process 1 needs to update the display color of desktop element 1 to blue, element process 1 can send the blue information to the desktop process, and the desktop process will update the display color of desktop element 1 to blue. The blue information sent by 1 updates the display color of desktop element 1 to blue. In Figure 1, the content identified as time and date, buttons and information can be the second type of desktop elements. The desktop elements described in the technical solution of this application are the second type of desktop elements.

Please refer to Figure 2, which is a schematic flowchart of some technologies for operating and controlling desktop elements. In Figure 2, element processes include, for example, time and date processes, information processes, and key processes. Each element process can call the system's native software development tool kit to register desktop elements in the desktop process to display desktop elements through the desktop. Among them, the system-native software development kit refers to the software development kit native to the operating system, which can be called by the element process and interact with the desktop process to realize the registration of desktop elements. In some embodiments, the operating system can be the Android operating system, and the system's native software development kit can also be called Android SDK.

In some technologies, after the desktop process displays the desktop elements registered by the element process on the desktop, the user can click on the desktop elements on the desktop. Desktop elements can respond accordingly to the user's click operations. For example, taking the desktop element "Information" in Figure 2 as an example, after the user performs a click operation on the desktop element "Information", the desktop element can refresh the displayed information. Here, the information refresh operation performed by the desktop element "information" is the response made by the desktop element "information" to the user's click operation. Among them, the process of the desktop element responding to the user's click operation can be as follows: after the desktop process monitors the user's click operation on the desktop element, the click operation is fed back to the element process, and the element process determines the needs of the desktop element. In response, the system's native software development tool kit is called to send the information required for the desktop element response to the desktop process. The desktop process updates the desktop elements based on the information sent by the element process, thereby responding to the user's click operation. to respond. Continue to take the desktop element "information" in Figure 2 above as an example. After the desktop process monitors the user's click on the desktop element "Information", it feeds back the click operation to the information process. The information process determines that the information displayed on the desktop element "Information" needs to be refreshed, and sends the target information to be displayed on the desktop element "Information" To the desktop process, the desktop process updates the information currently displayed by the desktop element "information" to the target information. It is understandable that different desktop elements can respond differently to the user's click operation. For example, after the user clicks on desktop element A, the display color of the desktop element can be updated. After the user clicks on desktop element B, the display color of the desktop element can be updated. , which can update the display content of desktop elements. In this way, the user can operate and control the desktop elements by clicking on the desktop elements, such as controlling the display content of the desktop elements and controlling the display color of the desktop elements.

Among these technologies, users can only operate and control desktop elements through click operations, and other operations on desktop elements cannot operate and control desktop elements. For example, when performing a sliding operation on a desktop element, the desktop element cannot be operated and controlled. The operation control functions of desktop elements are relatively simple.

To this end, this application proposes a desktop element operation method. This method provides a customized software development toolkit based on the system's native software development toolkit, which can enrich the operation and control functions of desktop elements. Among them, the software development kit is used to provide a functional interface in the desktop process, and the functional interface can be called by the element process. The element process calls this functional interface to interact with the desktop process and operate and control the desktop elements through the desktop process.

See Figure 3 and Figure 4. Figure 3 is a schematic flowchart of a desktop element operating method provided by an embodiment of the present application. Figure 4 is a schematic flowchart of operating and controlling desktop elements according to an embodiment of the present application. The desktop element operation method can be applied to the intelligent interactive tablet, including step S31 and step S32.

Step S31: Monitor triggering events for desktop elements, where the triggering event represents an event that triggers an element process corresponding to the desktop element to operate and control the desktop element.

In some embodiments, the triggering event may refer to an event that triggers the element process to call the system's native software development kit or a customized software development kit to operate and control the desktop element through the desktop process. The operation control performed on the desktop elements may be that the element process responds to the triggering event and operates the display content, position, appearance, etc. of the desktop elements. Detailed explanation is given below.

In some embodiments, the triggering event may include an element triggering event received by a desktop element. Element trigger events can be operation events for desktop elements. The element triggering event may include at least one of a touch event, a key event, an input event, a focus change event, and a click event for the desktop element. Different operation events can be triggered by elements belonging to different types. By triggering events for different types of elements, different operations can be controlled on desktop elements. Specifically:

Touch events can refer to sliding events performed by the user in the area where the desktop element is located. For details, please refer to Figure 5, which is a detailed schematic diagram of the desktop element "message" in Figure 4. In FIG. 5 , the desktop element “message” may include a sliding area 51 and a message area 52 . Among them, there is a sliding block 511 in the sliding area 51 . The user selects the sliding block 511 and slides it in the sliding area 51, which can cause the sliding block 511 to slide up and down in the sliding area 51, and then the message displayed in the message area 52 can be updated. Here, the sliding operation performed by the user in the sliding area 51 can be regarded as a sliding event performed in the area where the desktop element is located. Updating the message displayed in the message area 52 may be an operation control performed on the desktop element in response to a sliding event. In addition, in addition to sliding in the sliding area, the user can also perform sliding operations in the message area 52 to update the messages in the message area 52 .

Key events can refer to events monitored by the desktop process after key operations are performed on these devices when operating and controlling desktop elements through devices such as remote controls. Please continue to refer to FIG. 5 , assuming that the user can control the selected message in the message area 52 by operating the up and down buttons of the remote control. In Figure 5, the currently selected message is the first message in the message area 52. When the user presses the downward button on the remote control, the remote controller can send a downward signal to the intelligent interactive tablet, and then the currently selected message in the message area 52 can be adjusted to the message following the first message, for example The currently selected message adjusts the 2nd or 3rd message. Here, the desktop process listens to this downward signal, which can mean that the desktop process listens to the key event. Adjusting the currently selected message in the message area 52 to the message following the first message may be an operational control of the desktop elements in response to a key event.

Input events can refer to input operation events performed by the user in the area where the desktop element is located; focus change events can refer to events where the focus of the area where the desktop element is located changes. Please continue to Figure 5. In Figure 5, the desktop element "Message" may also include an input area 53. In the input area 53, the user can input query conditions, so that the message area 52 displays messages that satisfy the query conditions. Here, the user's action of inputting query conditions in the input area 53 can represent an input event. The message area 52 displays messages that meet the query conditions, indicating the operation control of the desktop elements in response to the input event.

The focus change event can refer to the event that the focus of the area where the desktop element is located changes. Specifically, the focus can be a selection box located in the area where the desktop element is located. The selection box is located at a certain position, indicating that the content at that position is selected. For example, in Figure 5, the focus of the message area 52 is currently located at the first message, which means that the message at this position is selected. If the focus moves to the second message, it means that the second message is selected. Depending on the focus change, different message details can be displayed. For example, when the focus moves to the first message, the area where the first message is located is expanded, and the detailed information of the first message is displayed in the expanded area. When the focus moves to the second message, the area where the second message is located is expanded, and the detailed information of the second message is displayed in the expanded area. Here, the focus changes before different messages, which can represent a focus change event. Displaying details of the focused message can represent operational controls on desktop elements in response to focus change events.

A click event can refer to an event in which the user performs a click operation on the area where the desktop element is located. Please continue to see Figure 5. In FIG. 5 , assuming that the user clicks on a certain message in the message area 52 , for example, clicks on the second message, the detailed information of the message can be displayed in the message area 52 . Here, the user's action of clicking on a certain message in the message area 52 can be a click event. The message area 52 displays the detailed information of the message, indicating the operation control performed on the desktop element in response to the click event.

See Figure 4. In some embodiments, element-triggered events for desktop elements may be listened to by a desktop process. The desktop process can feed back the monitored touch events to the element process. The element process triggers the event based on the element, determines the operation control that needs to be performed on the desktop element, and calls the system's native software development kit or customized software development kit. The functional interface sends information related to operation control to the desktop process, and the desktop process operates and controls the desktop elements based on the received information. For example, see Figure 5 in conjunction. After the user clicks the second message in the message area 52 of the desktop element "Information", the desktop process can feed back the click operation performed by the user and the message identifier of the message clicked by the user to the information process, and the information process calls the customized software development tool kit The functional interface sends the detailed information of the second message to the desktop process, and updates the content displayed in the message area 52 through the desktop process.

In some embodiments, considering the characteristics of different desktop elements, the element trigger events that need to be monitored can be specified for each desktop element. For example, for the desktop element "key press", you need to pay attention to the focus change events and key press events received by the desktop element. You can only monitor whether the desktop element receives focus change events and key press events; and for the desktop element "information" For example, if you need to pay attention to the focus change events, touch events, and key events received by the desktop element, you can only monitor whether the desktop element receives focus change events, touch events, and key events. For the element trigger events that need to be monitored for each desktop element, before the desktop process monitors the element trigger events, the element process can register the element trigger events that need to be monitored to the desktop process, and the registered element trigger events can be monitored through the desktop process.

Specifically, the functional interface may include a listening interface. The listening interface may include, but is not limited to, a listening interface for touch events, a listening interface for key events, a listening interface for input events, a listening interface for focus change events, and a listening interface for click events. After the element process determines the element trigger event that needs to be monitored, it can call the corresponding listening interface and register the element trigger event that needs to be monitored to the desktop process, and the desktop process monitors the corresponding element trigger event. For example, the information process can call the listening interface for focus change events, the listening interface for touch events, and the listening interface for key events respectively, and register the focus change events, touch events, and key events to the desktop process, and the desktop process will "information" the desktop elements. Whether to monitor the received events; and the key process can call the monitoring interface of the focus change event and the listening interface of the key event respectively, register the focus change event and key event to the desktop process, and the desktop process will "key press" the desktop element. "Whether the events are received and monitored. After the desktop process monitors the registered element trigger event, it feeds the element trigger event back to the element process through an interface callback.

It can be understood that triggering events may include, but are not limited to, the above element triggering events. In some embodiments, trigger events may also include time trigger events. The time-triggered event can be an event monitored by the element process whether the time reaches the preset time. For example, when the element process monitors that the time is 1 a.m. every day, the system's native software development kit or customized software development kit is called to operate and control the desktop elements through the desktop process. Time-triggered events can be different types of trigger events than the above element-triggered events.

Step S32, if a trigger event is monitored, the element process corresponding to the desktop element determines the operation control that matches the type of the trigger event, and calls the functional interface to perform corresponding operation control on the desktop element through the desktop process.

In some embodiments, element processes may have a matching relationship between trigger event types and operation controls. For the same element process, each type of trigger event can have matching operation controls. Table 1 exemplifies the matching relationship between trigger event types and operation controls in the message process.

Table 1 Matching relationship between trigger event types and operation controls

As can be seen from Table 1, by classifying trigger events and based on the matching relationship between trigger event types and operational controls, multiple trigger events can be used to trigger operational controls on desktop elements, and different types of trigger events can have corresponding operational control. The operation control functions of desktop elements are richer.

In some embodiments, the functional interface includes an operational interface. The operation interface includes but is not limited to the interface for setting the dynamic display of desktop elements and the interface for controlling the display or hiding of desktop elements. After the element process determines the operation control for the desktop element, it calls the corresponding operation interface to perform operation control on the desktop element through the desktop process.

In some embodiments, for element triggering events, different types of element triggering events may have different trigger type identifiers. The trigger type identifies the type of event that the element triggers. If the desktop process listens to the element trigger event, it returns the trigger message to the element process. The trigger message includes the trigger type identifier. The element process determines the operation control that matches the trigger type identifier, and calls the operation interface to perform corresponding operation control on the desktop element through the desktop process. In this way, by carrying the trigger type identifier in the trigger message, the element process can distinguish the type of the element trigger event, and then determine the operation control that matches the type of the element trigger event.

In some embodiments, the element process corresponding to the desktop element determines the operation control that matches the type of the trigger event. Specifically, it may include: the element process determines the current element state of the desktop element; and based on the current element state, based on the trigger event The type of event that determines the operational control of adjusting a desktop element from the current element state to the next element state. Element status may refer to the display status of desktop elements on the desktop, including but not limited to the display content, display position, display shape, and display color of desktop elements. A trigger event can trigger the adjustment of at least one element state of the desktop element, that is, the adjustment from the current element state to the next element state. For example, adjust the desktop elements from the current placement A to the next placement B. When the element process determines the operation control that matches the type of the trigger event, it can determine the next element state of the desktop element according to the type of the trigger event, and then determine the operation control that adjusts the desktop element from the current element state to the next element state. . For example, after the desktop element "message" receives a key event, the desktop process feeds the key event back to the element process. Based on the type of the trigger event, the element process determines that the focus position of the desktop element in the next element state should be below the current focus position. At the message position separated by two messages, the operation control to switch the focus from the current focus position to the next focus position can be determined, and the operation interface is called to send the next focus position to the desktop process, and the desktop element is controlled by the desktop process. The focus switches to the next focus position.

In some embodiments, when there are multiple desktops, the desktop process is also used to determine the desktop ID of the desktop where the desktop element that receives the element trigger event is located, and sets the desktop ID in the trigger message and returns it to the element process. So that the element process determines the operation control matching the trigger type identifier for the desktop element of the corresponding desktop according to the desktop identifier. Specifically, for the same element process, the desktop elements corresponding to different desktops may have different states. Taking the message process as an example, in Desktop 1, the desktop element "Message" may display a message list including the input content, and in Desktop 2, the desktop element "Message" may display the latest message list after refreshing. If in desktop 1 and desktop 2, the desktop element "message" receives a touch event that refreshes the content in the desktop element "message", it is understandable that the refresh content on the two desktops is different. To this end, by carrying the desktop identifier in the trigger message returned by the desktop process to the element process, the solution is more adaptable.

In some embodiments of the present application, by providing a software development toolkit, the element process corresponding to the desktop element determines the operation control that matches the type of the trigger event, so that multiple trigger events can be used to trigger the execution of operation control on the desktop element. , and different types of trigger events can have corresponding operation controls respectively. The operation control functions of desktop elements are richer.

In some embodiments, considering that the system's native software development kit already has the function of registering click events to the desktop process, the customized software development kit does not need to develop a listening interface for click events. When the element process registers the element-triggered events that need to be monitored to the desktop process, it can register the event according to the following logic:

If the element trigger event is at least one of a touch event, a key event, an input event, and a focus change event, the element process calls the listening interface and registers the element trigger event that needs to be monitored in the desktop process.

If the element trigger event is a click event, the element process calls the system's native software development tool kit to register the click trigger event in the desktop process.

Similarly, considering that the system's native software development kit already has the function of registering desktop elements in the desktop process, before the element process registers the element trigger events that need to be monitored to the desktop process, the desktop can be registered in the desktop process through the following method element:

The element process calls the system's native software development kit to register desktop elements in the desktop process; or when the functional interface provided by the custom software development kit includes a registration interface, the element process can call the registration interface, which is controlled by a custom The software development kit calls the system's native software development kit and registers desktop elements in the desktop process.

In general, for the functions that the system's native software development kit already has, the custom software development kit can directly call the system's native software without the need for related software development. The element process or the customized software development kit can directly call the system's native software. Development toolkit to perform related functions. In this way, the purpose of reducing code development and code redundancy is achieved.

Please refer to FIG. 6 , which is a schematic structural diagram of an electronic device according to an embodiment of the present application. The electronic device provides a software development kit, and the software development kit is used to provide functional interfaces in the desktop process. The electronic device includes:

The event monitoring module is specifically used for:

In some embodiments, the desktop operation module is specifically used to:

Please refer to Figure 7. One embodiment of the present application also provides an intelligent interactive tablet. The intelligent interactive tablet includes a processor and a memory. The memory is used to store a computer program. When the computer program is executed by the processor, the above desktop element operating method is implemented.

The processor may be a central processing unit (Central Processing Unit, CPU). The processor can also be other general-purpose processors, Digital Signal Processor (DSP), Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other Chips such as programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or combinations of these types of chips.

As a non-transitory computer-readable storage medium, the memory can be used to store non-transitory software programs, non-transitory computer executable programs and modules, such as program instructions/modules corresponding to the methods in the embodiments of the present invention. The processor executes various functional applications and data processing of the processor by running non-transient software programs, instructions and modules stored in the memory, that is, implementing the method in the above method implementation.

The memory may include a program storage area and a data storage area, where the program storage area may store an operating system and an application program required for at least one function; the data storage area may store data created by the processor, etc. In addition, the memory may include high-speed random access memory and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, the memory optionally includes memory located remotely from the processor, and these remote memories may be connected to the processor through a network. Examples of the above-mentioned networks include but are not limited to the Internet, intranets, local area networks, mobile communication networks and combinations thereof.

Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the invention. Such modifications and variations are covered by the appended claims. within the limited scope.

Claims

A method for operating desktop elements, characterized in that a software development toolkit is provided, and the software development toolkit is used to provide functional interfaces in desktop processes; the method includes:

Monitor triggering events for desktop elements, where the triggering events represent events that trigger the element process corresponding to the desktop element to operate and control the desktop element;

If the trigger event is monitored, the element process corresponding to the desktop element determines the operation control that matches the type of the trigger event, and calls the functional interface to execute the corresponding operation on the desktop element through the desktop process. operational control.
The method of claim 1, wherein the functional interface includes an operation interface, the triggering event includes an element triggering event received by the desktop element, and the element triggering event is monitored by the desktop process, in,

If the desktop process monitors the element trigger event, it returns a trigger message to the element process. The trigger message includes a trigger type identifier, and the trigger type identifier represents the type of the element trigger event;

The element process determines the operation control that matches the trigger type identifier, and calls the operation interface to perform corresponding operation control on the desktop element through the desktop process.
The method of claim 2, wherein before the desktop process listens to the element trigger event, the method further includes:

The element process registers the element triggering event that needs to be monitored to the desktop process, and the desktop process monitors the registered element triggering event.
The method of claim 3, wherein the functional interface includes a listening interface, and the element triggering event includes at least one of a touch event, a key event, an input event, a focus change event, and a click event for desktop elements. ;

Registering the element-triggered events that need to be monitored to the desktop process includes:

If the element triggering event is at least one of a touch event, a key event, an input event, and a focus change event, the element process calls the listening interface and registers the element triggering event that needs to be monitored in the desktop process;

If the element triggering event is a click event, the element process calls the system's native software development tool kit to register the click triggering event in the desktop process.
The method of claim 3, wherein before the element process registers the element trigger event that needs to be monitored to the desktop process, the method further includes:

Register the desktop element in the desktop process so that the desktop element is displayed by the desktop process, where:

The element process calls the system's native software development tool kit to register the desktop element in the desktop process; or

The functional interface provided by the software development toolkit includes a registration interface. The element process calls the registration interface, and the software development toolkit calls the system's native software development toolkit, and registers everything in the desktop process. Desktop elements.
The method of claim 2, wherein when there are multiple desktops and the desktop process listens to the registered element trigger event, the method further includes:

The desktop process determines the desktop identifier of the desktop where the desktop element that receives the element trigger event is located, sets the desktop identifier in the trigger message, and returns it to the element process, so that the element process can The desktop identification determines the operation control matching the trigger type identification for the desktop element of the corresponding desktop.
The method of claim 1, wherein the element process corresponding to the desktop element determines the operation control that matches the type of the trigger event, including:

Determining, by the element process, the current element state of the desktop element;

Based on the current element state, based on the type of the trigger event, the operation control for adjusting the desktop element from the current element state to the next element state is determined.
An electronic device, characterized in that the electronic device provides a software development toolkit, and the software development toolkit is used to provide a functional interface in a desktop process; the electronic device includes:

The event listening module monitors triggering events for desktop elements, where the triggering event represents an event that triggers the element process corresponding to the desktop element to operate and control the desktop element;

Desktop operation module, if the trigger event is monitored, the element process corresponding to the desktop element determines the operation control that matches the type of the trigger event, and calls the functional interface to control the operation of the trigger event through the desktop process. Desktop elements perform corresponding operational controls.
The electronic device according to claim 8, wherein the functional interface includes an operation interface, the triggering event includes an element triggering event received by the desktop element, and the element triggering event is monitored by the desktop process. ,in,

The event listening module is specifically configured to: if the desktop process monitors the element trigger event, return a trigger message to the element process, where the trigger message includes a trigger type identifier, and the trigger type identifier represents the element trigger. type of event;

The desktop operation module is specifically configured to: the element process determine the operation control that matches the trigger type identifier, and call the operation interface to perform corresponding operation control on the desktop element through the desktop process.
The electronic device according to claim 9, characterized in that, before the desktop process listens to the element triggering event, the event listening module is also used to:

The element process registers the element triggering event that needs to be monitored to the desktop process, and the desktop process monitors the registered element triggering event.
The electronic device of claim 10, wherein the functional interface includes a listening interface, and the element triggering event includes at least one of touch events, key events, input events, focus change events, and click events for desktop elements. one;

The event monitoring module is specifically used for:

If the element triggering event is at least one of a touch event, a key event, an input event, and a focus change event, the element process calls the listening interface and registers the element triggering event that needs to be monitored in the desktop process;

If the element triggering event is a click event, the element process calls the system's native software development tool kit to register the click triggering event in the desktop process.
The electronic device according to claim 10, characterized in that, before the element process registers the element triggering event that needs to be monitored to the desktop process, the event listening module is also used to:

Register the desktop element in the desktop process so that the desktop element is displayed by the desktop process, where:

The element process calls the system's native software development tool kit to register the desktop element in the desktop process; or

The functional interface provided by the software development toolkit includes a registration interface. The element process calls the registration interface, and the software development toolkit calls the system's native software development toolkit, and registers everything in the desktop process. Desktop elements.
The electronic device of claim 9, wherein when there are multiple desktops and the desktop process monitors the registered element triggering an event, the event listening module is further configured to:

The desktop process determines the desktop identifier of the desktop where the desktop element that receives the element trigger event is located, sets the desktop identifier in the trigger message, and returns it to the element process, so that the element process can The desktop identification determines the operation control matching the trigger type identification for the desktop element of the corresponding desktop.
The electronic device according to claim 8, characterized in that the desktop operation module is specifically used for:

Determining, by the element process, the current element state of the desktop element;

Based on the current element state and based on the type of the triggering event, an operation control for adjusting the desktop element from the current element state to the next element state is determined.
A computer-readable storage medium, characterized in that the computer-readable storage medium is used to store a computer program. When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.
An intelligent interactive tablet, characterized in that the intelligent interactive tablet includes a processor and a memory, and the memory is used to store a computer program. When the computer program is executed by the processor, it implements claims 1 to 7 any of the methods described.