CN116420138A - Desktop element operation method, electronic equipment and intelligent interaction panel - Google Patents
Desktop element operation method, electronic equipment and intelligent interaction panel Download PDFInfo
- Publication number
- CN116420138A CN116420138A CN202280006530.XA CN202280006530A CN116420138A CN 116420138 A CN116420138 A CN 116420138A CN 202280006530 A CN202280006530 A CN 202280006530A CN 116420138 A CN116420138 A CN 116420138A
- Authority
- CN
- China
- Prior art keywords
- desktop
- event
- triggering
- operation control
- interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 324
- 230000003993 interaction Effects 0.000 title abstract description 10
- 230000008569 process Effects 0.000 claims abstract description 282
- 238000012544 monitoring process Methods 0.000 claims abstract description 34
- 230000006870 function Effects 0.000 claims abstract description 21
- 230000008859 change Effects 0.000 claims description 26
- 238000004590 computer program Methods 0.000 claims description 6
- 230000002452 interceptive effect Effects 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 10
- 230000004044 response Effects 0.000 description 9
- FFBHFFJDDLITSX-UHFFFAOYSA-N benzyl N-[2-hydroxy-4-(3-oxomorpholin-4-yl)phenyl]carbamate Chemical compound OC1=C(NC(=O)OCC2=CC=CC=C2)C=CC(=C1)N1CCOCC1=O FFBHFFJDDLITSX-UHFFFAOYSA-N 0.000 description 4
- 238000012545 processing Methods 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 239000003086 colorant Substances 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Abstract
A desktop element operation method, electronic equipment and an intelligent interaction tablet are provided, wherein 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 the following steps: monitoring a triggering event aiming at a desktop element (S31), wherein the triggering event represents an event for controlling the operation of the desktop element by an element process corresponding to the triggering desktop element; if the trigger event is monitored, the element process corresponding to the desktop element determines the operation control matched with the type of the trigger event, and invokes the functional interface to execute the corresponding operation control on the desktop element through the desktop process (S32). In the method, the operation control functions of desktop elements are rich.
Description
Technical Field
The invention relates to the technical field of display, in particular to a desktop element operation method, electronic equipment and an intelligent interaction panel.
Background
The intelligent interaction panel is integrated equipment for controlling the content displayed on the display panel and realizing man-machine interaction operation through a touch technology, and is widely applied to the fields of education and teaching, enterprise conferences, commercial display and the like.
At present, an Android operating system is commonly mounted on the intelligent interaction panel. The Android operating system provides a functional interface for a developer, allows a third party application to register desktop elements for a desktop process, and displays the registered desktop elements through a desktop, but has a single operation control function for the desktop elements.
Disclosure of Invention
In view of the above, the embodiments of the present invention provide a desktop element operation method, an electronic device, an intelligent interaction tablet, and a computer readable storage medium, where operation control functions of desktop elements are rich.
The invention provides a desktop element operation method, and provides a software development kit, wherein the software development kit is used for providing a functional interface in a desktop process; the method comprises the following steps:
monitoring a triggering event aiming at a desktop element, wherein the triggering event characterizes an event for triggering an element process corresponding to the desktop element to perform operation control on the desktop element;
if the triggering event is monitored, determining operation control matched with the type of the triggering event by an element process corresponding to the desktop element, calling the functional interface, and executing corresponding operation control on the desktop element by the desktop process.
In some embodiments, the functional interface comprises an operational interface, the trigger event comprises an element trigger event received by the desktop element, the element trigger event being listened to by the desktop process, wherein,
if the desktop process monitors the element triggering event, returning a triggering message to the element process, wherein the triggering message comprises a triggering type identifier, and the triggering type identifier characterizes the type of the element triggering event;
and the element process determines the operation control matched with the trigger type identification, invokes the operation interface and executes corresponding operation control on the desktop element through the desktop process.
In some embodiments, before the desktop process listens for the element triggering event, the method further comprises:
registering the element triggering event to be monitored to the desktop process by the element process, and monitoring the registered element triggering event through the desktop process.
In some embodiments, the functional interface comprises a listening interface, the element triggering event comprising at least one of a touch event, a key event, an input event, a focus change event, and a click event for a desktop element;
Registering the element triggering event to be monitored to the desktop process comprises the following steps:
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 monitoring interface, and the element triggering event needing to be monitored is registered in the desktop process;
and if the element triggering event is a clicking event, the element process calls a software development kit of a system native, and the clicking triggering event is registered in the desktop process.
In some embodiments, before the element process registers the element trigger event to be monitored to the desktop process, the method further includes:
registering the desktop element in the desktop process to display the desktop element through the desktop process, wherein:
the element process calls a system native software development kit, and the desktop element is registered in the desktop process; or (b)
The function interface provided by the software development kit comprises a registration interface, the element process calls the registration interface, the software development kit of the system native software development kit is called by the software development kit, and the desktop element is registered in the desktop process.
In some embodiments, in the case where there are multiple desktops, after the desktop process monitors the registered element trigger event, the method further comprises:
the desktop process determines a desktop identifier of a desktop where the desktop element receiving the element triggering event is located, sets the desktop identifier in the triggering message, and returns the desktop identifier to the element process, so that the element process determines operation control matched with the triggering type identifier according to the desktop identifier aiming at the desktop element of the corresponding desktop.
In some embodiments, the determining, by the element process corresponding to the desktop element, an operation control matching the type of the trigger event includes:
determining, by the element process, a current element state of the desktop element;
based on the current element state, determining operation control for adjusting the desktop element from the current element state to a next element state based on the type of the trigger event.
The invention also provides the electronic equipment, and the electronic equipment provides a software development kit which is used for providing a functional interface in a desktop process; the electronic device includes:
The event monitoring module monitors a triggering event aiming at a desktop element, wherein the triggering event characterizes an event for triggering an element process corresponding to the desktop element to perform operation control on the desktop element;
and the desktop operation module is used for determining operation control matched with the type of the trigger event by an element process corresponding to the desktop element if the trigger event is monitored, calling the functional interface and executing corresponding operation control on the desktop element by the desktop process.
In some embodiments, the functional interface comprises an operational interface, the trigger event comprises an element trigger event received by the desktop element, the element trigger event being listened to by the desktop process, wherein,
the event monitoring module is specifically configured to: if the desktop process monitors the element triggering event, returning a triggering message to the element process, wherein the triggering message comprises a triggering type identifier, and the triggering type identifier characterizes the type of the element triggering event;
the desktop operation module is specifically configured to: and the element process determines the operation control matched with the trigger type identification, invokes the operation interface and executes corresponding operation control on the desktop element through the desktop process.
In some embodiments, before the desktop process listens for the element triggering event, the event listening module is further configured to:
registering the element triggering event to be monitored to the desktop process by the element process, and monitoring the registered element triggering event through the desktop process.
In some embodiments, the functional interface comprises a listening interface, the element triggering event comprising at least one of a touch event, a key event, an input event, a focus change event, and a click event for a desktop element;
the event monitoring module is specifically configured to:
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 monitoring interface, and the element triggering event needing to be monitored is registered in the desktop process;
and if the element triggering event is a clicking event, the element process calls a software development kit of a system native, and the clicking triggering event is registered in the desktop process.
In some embodiments, before the element process registers the element triggering event to be monitored to the desktop process, the event monitoring module is further configured to:
Registering the desktop element in the desktop process to display the desktop element through the desktop process, wherein:
the element process calls a system native software development kit, and the desktop element is registered in the desktop process; or (b)
The function interface provided by the software development kit comprises a registration interface, the element process calls the registration interface, the software development kit of the system native software development kit is called by the software development kit, and the desktop element is registered in the desktop process.
In some embodiments, in a case where there are a plurality of desktops, after the desktop process monitors the registered element triggering event, the event monitoring module is further configured to:
the desktop process determines a desktop identifier of a desktop where the desktop element receiving the element triggering event is located, sets the desktop identifier in the triggering message, and returns the desktop identifier to the element process, so that the element process determines operation control matched with the triggering type identifier according to the desktop identifier aiming at the desktop element of the corresponding desktop.
In some embodiments, the desktop operation module is specifically configured to:
Determining, by the element process, a current element state of the desktop element;
based on the current element state, determining operation control for adjusting the desktop element from the current element state to a next element state based on the type of the trigger event.
In a further aspect the invention provides a computer readable storage medium for storing a computer program which, when executed by a processor, implements a method as described above.
In another aspect, the present invention also provides a smart interactive tablet comprising a processor and a memory for storing a computer program which, when executed by the processor, implements a method as described above.
According to the technical scheme provided by the embodiments, the operation control matched with the type of the trigger event is determined by the element process corresponding to the desktop element by providing the software development kit, so that the execution of the operation control on the desktop element can be triggered by a plurality of trigger events, and different types of trigger events can respectively have corresponding operation control. The operation control function of the desktop elements is richer.
Drawings
The features and advantages of the present invention will be more clearly understood by reference to the accompanying drawings, which are illustrative and should not be construed as limiting the invention in any way, in which:
FIG. 1 illustrates a desktop element diagram on a desktop;
FIG. 2 illustrates a flow diagram of some techniques for operational control of desktop elements;
FIG. 3 is a flow diagram of a desktop element operation method according to an embodiment of the present application;
FIG. 4 illustrates a flow diagram for operational control of desktop elements provided by one embodiment of the present application;
FIG. 5 shows a detailed schematic diagram of the desktop element "message" in FIG. 4;
FIG. 6 shows a schematic structural diagram of an electronic device provided in an embodiment of the present application;
fig. 7 shows a schematic structural diagram of an intelligent interaction tablet according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments. All other embodiments, based on the embodiments of the invention, which a person skilled in the art would obtain without making any inventive effort, are within the scope of the invention.
Before explaining the technical scheme of the application, desktop elements are explained first. Please refer to fig. 1, which is a diagram illustrating desktop elements on a desktop. In general, a desktop element may be content that is displayed through a desktop, including but not limited to an interface of a software tool displayed on the desktop, a launch icon of an application, an application folder that is a combination of launch icons of several applications, and the like. For example, in fig. 1, the content displayed as application 1, application 2, time date, information, buttons may be collectively referred to as desktop elements. The content displayed as application 1 and application 2 may be a start icon of the application. Clicking the start icon may start the corresponding application process. The content displayed as time date, information, buttons may be an interface of a software tool displayed on a desktop. Through the interface of the software tool, the time date, information or key operation can be checked on the desktop. In some embodiments, a desktop process may have operational control over desktop elements. For example, the desktop process may control the placement of desktop elements on the desktop, display colors, and the like.
In general, desktop elements can be divided into two categories. One type may be desktop elements provided by a desktop process, such as launch icons for applications, application folders that are composed of a combination of launch icons for several applications. The functionality of the desktop elements is provided by the desktop process. The desktop process can actively perform operation control on the desktop elements. In fig. 1, the launch icons displayed as application 1 and application 2 may be a first type of desktop element. Another type is a desktop element that is registered by other element processes at the desktop process and displayed at the desktop. The functions of the desktop elements are provided by the element process and have no direct relation with the desktop process. The desktop process can perform operation control on the desktop element according to the information provided by the element process. For example, assuming that the element process corresponding to the desktop element 1 is the element process 1, the element process 1 needs to update the display color of the desktop element 1 to blue, and then the element process 1 may send blue information to the desktop process, and the desktop process updates the display color of the desktop element 1 to blue according to the blue information sent by the element process 1. In fig. 1, the content identified as time date, button, and information may be a second type of desktop element. The desktop elements in the technical scheme of the application are the second type desktop elements.
Referring to fig. 2, a flow chart of operation control of desktop elements according to some techniques is shown. In fig. 2, the element process includes, for example, a time date process, an information process, and a key process. Each element process can respectively call a software development kit of the system native, and the desktop elements are registered in the desktop process so as to display the desktop elements through the desktop. The system native software development kit refers to a native software development kit of an operating system, and the native software development kit can be called by an element process and interact with a desktop process to realize the registration of desktop elements. In some embodiments, the operating system may be an Android operating system, and a system native software development kit may also be referred to as an Android SDK.
In some techniques, after a desktop process displays a desktop element registered by an element process on the desktop, a user may perform a click operation on the desktop element on the desktop. For a click operation by a user, the desktop element may respond accordingly. For example, taking the desktop element "information" in fig. 2 as an example, after the user performs a click operation on the desktop element "information", the desktop element may refresh the displayed information once. Here, the operation of refreshing the information by the desktop element "information" is the response of the desktop element "information" to the clicking operation of the user. Wherein, for the click operation of the user, the process of responding to the desktop element can be as follows: after the desktop process monitors the clicking operation of the user on the desktop element, the clicking operation is fed back to the element process, the element process determines the response required to be made by the desktop element, and invokes a system native software development kit, information required by the desktop element response is sent to the desktop process, and the desktop process updates the desktop element according to the information sent by the element process, so that the clicking operation of the user is responded. Continuing with the desktop element "info" example in FIG. 2 above. After the desktop process monitors that a user clicks the desktop element information, the clicking operation is fed back to the information process, the information process determines that information displayed by the desktop element information needs to be refreshed, target information to be displayed by the desktop element information is sent to the desktop process, and the desktop process updates the information currently displayed by the desktop element information into target information. It can be understood that, for the clicking operation of the user, different desktop elements can respond differently, for example, after the user clicks on the desktop element a, the display color of the desktop element can be updated, and after the user clicks on the desktop element B, the display content of the desktop element can be updated. Thus, the user can perform operation control on the desktop element by clicking the desktop element, such as controlling the display content of the desktop element and controlling the display color of the desktop element.
In the technologies, only the operation control of the desktop element by a click operation method is supported, and other operations aiming at the desktop element cannot perform operation control on the desktop element. For example, when a sliding operation is performed on a desktop element, operation control cannot be performed on the desktop element. The operation control function of the desktop elements is single.
Therefore, the application provides a desktop element operation method. The method provides a self-defined software development kit on the basis of a system native software development kit, so that the operation control function of desktop elements can be richer. The software development kit is used for providing a functional interface in the desktop process, and the functional interface can be called by the element process. The element process calls the functional interface, can perform information interaction with the desktop process, and performs operation control on the desktop element through the desktop process.
Please refer to fig. 3 and fig. 4. Fig. 3 is a flowchart of a desktop element operation method according to an embodiment of the present application. FIG. 4 is a flow chart of operation control of desktop elements according to an embodiment of the present application. The desktop element operation method can be applied to the intelligent interactive tablet, and comprises the steps S31 and S32.
Step S31, monitoring a triggering event aiming at the desktop element, wherein the triggering event characterizes an event for triggering an element process corresponding to the desktop element to perform operation control on the desktop element.
In some embodiments, the trigger event may refer to an event that triggers the element process to invoke a system native software development kit or a custom software development kit, which performs operational control on the desktop element through the desktop process. Performing operation control on the desktop element may be that the element process performs operation control on display content, position, appearance, etc. of the desktop element in response to the trigger event. The following is a detailed description.
In some embodiments, the trigger event may include an element trigger event received by a desktop element. The element triggering event may be an operational event for a desktop element. 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 a desktop element. Different operational events may belong to different types of element triggering events. For different types of element triggering events, different operation control can be performed on the desktop elements. Specifically:
A touch event may refer to a sliding event performed by a user in the area where the desktop element is located. Referring specifically to fig. 5, a detailed schematic diagram of the desktop element "message" in fig. 4 is shown. In fig. 5, the desktop element "message" may include a sliding region 51 and a message region 52. Wherein a slider 511 is present in the sliding region 51. The user selects the sliding block 511 and slides in the sliding area 51, so that the sliding block 511 can be driven to slide up and down in the sliding area 51, and the message displayed in the message area 52 can be updated. Here, the sliding operation performed by the user in the sliding area 51 may be a sliding event performed in the area where the desktop element is located. The updating of the message displayed in the message area 52 may be an operational control performed on the desktop element in response to a sliding event. In addition, in addition to sliding in the sliding area, the user may also perform a sliding operation in the message area 52, thereby updating the message of the message area 52.
The key event may refer to an event that is monitored by a desktop process after a key operation is performed on a device such as a remote controller when the device performs operation control on a desktop element. With continued reference to fig. 5, assume that the user can control the message in which the message area 52 is selected by operating the up-down keys of the remote control. In fig. 5, the currently selected message is message 1 of message area 52. When the user presses the down button on the remote control, the remote control may send a down signal to the smart interactive pad, and then may adjust the currently selected message in the message area 52 to be the 1 st message down message, such as adjusting the currently selected message to be the 2 nd message or the 3 rd message. Here, the desktop process listening for this down signal may indicate that the desktop process is listening for a key event. The adjustment of the currently selected message in the message area 52 to the message 1 down may be an operational control of the desktop element in response to a key event.
The input event may refer to an input operation event executed by a user in an area where a desktop element is located; the focus change event may refer to an event in which the focus of the area in which the desktop element is located changes. Please continue to refer to fig. 5. In fig. 5, the desktop element "message" may also include an input field 53. In the input area 53, the user can input a query condition, causing the message area 52 to display a message satisfying the query condition. Here, the action of the user inputting the query condition in the input area 53 may represent one input event. The message area 52 displays a message satisfying the query condition, indicating operational control of the desktop element in response to an input event.
The focus change event may refer to an event in which the focus of the area in which the desktop element is located changes. Specifically, the focus may be a selection box located in the area where the desktop element is located. The selection box is located at a location and content representing the location is selected. For example, in FIG. 5, the focal point of message area 52 is currently located at message 1, indicating that the message at that location is selected. If the focus moves to message 2, it means that message 2 is selected. Detailed information of different messages can be displayed according to the change of the focus. For example, when the focus is moved to the 1 st message, the area where the 1 st message is located is enlarged, and detailed information of the 1 st message is displayed in the enlarged area. When the focus moves to the 2 nd message, the area where the 2 nd message is located is enlarged, and detailed information of the 2 nd message is displayed in the enlarged area. Here, the focus changes before a different message, which may represent one focus change event. The detailed information of the message in which the focus is located is displayed, and may represent operation control performed on the desktop element in response to the focus change event.
Click events may refer to events in which a user performs a click operation in the area where the desktop element is located. Please continue to refer to fig. 5. In fig. 5, it is assumed that a user clicks on a certain message, such as a second message, in the message area 52, and detailed information of the message may be displayed in the message area 52. Here, the action of clicking a message by the user in the message area 52 may be a click event. The message area 52 displays detailed information of the message, representing operation control of the desktop element in response to the click event.
Please refer to fig. 4. In some embodiments, element triggering events for desktop elements may be listened to by the desktop process. The desktop process can feed back the monitored touch event to the element process, the element process determines the operation control to be executed for the desktop element according to the element trigger event, and invokes a system native software development kit or a function interface of a custom software development kit, sends information related to the operation control to the desktop process, and the desktop process performs operation control on the desktop element according to the received information. For example, refer to fig. 5 in combination. After the user clicks the 2 nd message in the message area 52 of the desktop element "information", the desktop process may feed back the clicking operation performed by the user and the message identifier of the message clicked by the user to the information process, and the information process invokes the function interface of the custom software development kit, sends the detailed information of the 2 nd 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, an element trigger event that needs to be monitored may be specified separately for each desktop element. For example, for a desktop element "key", focus change events and key events received by the desktop element need to be concerned, and then whether focus change events and key events received by the desktop element are received can be monitored; for the desktop element "information", attention needs to be paid to the focus change event, the touch event and the key event received by the desktop element, and whether the focus change event, the touch event and the key event are received by the desktop element can be monitored. For the element triggering event to be monitored of each desktop element, before the desktop process monitors the element triggering event, the element process registers the element triggering event to be monitored to the desktop process, and monitors the registered element triggering event through the desktop process.
In particular, the functional interface may comprise a listening interface. The listening interfaces may include, but are 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 determining the element triggering event to be monitored, the element process can call a corresponding monitoring interface, register the element triggering event to be monitored to the desktop process, and monitor the corresponding element triggering event by the desktop process. For example, the information process may call a monitoring interface of a focus change event, a monitoring interface of a touch event, and a monitoring interface of a key event, register the focus change event, the touch event, and the key event to the desktop process, and monitor whether the desktop element "information" is received by the desktop process; the key process can respectively call a monitoring interface of the focus change event and a monitoring interface of the key event, register the focus change event and the key event to the desktop process, and monitor whether the desktop element key is received by the desktop process. After the desktop process monitors the registered element triggering event, the element triggering event is fed back to the element process in an interface callback mode.
It is to be appreciated that the trigger event can include, but is not limited to, the element trigger event described above. In some embodiments, the trigger event may also include a time trigger event. The time-triggered event may be an event of whether the time monitored by the element process reaches a preset time. For example, when the element process monitors that the time is 1 am every day, a system native software development kit or a custom software development kit is called, and the desktop element is controlled through the desktop process. The time trigger event may be of a different type of trigger event than the element trigger event described above.
Step S32, if the triggering event is monitored, determining the operation control matched with the type of the triggering event by the element process corresponding to the desktop element, calling the functional interface, and executing the corresponding operation control on the desktop element by the desktop process.
In some embodiments, an element process may have a matching relationship of trigger event types to operation control. There may be matching operational controls for each type of trigger event for the same element process, respectively. Table 1 exemplifies the matching relationship of trigger event types and operation controls in the message process.
Table 1 matching relationship between trigger event type and operation control
As can be seen from table 1, by classifying the trigger events, based on the matching relationship between the trigger event type and the operation control, the operation control on the desktop element can be triggered by multiple trigger events, and different types of trigger events can respectively have corresponding operation control. The operation control function of the desktop elements is richer.
In some embodiments, the functional interface comprises an operation interface. The operation interface includes, but is not limited to, an interface for setting up the desktop element to be displayed dynamically, an interface for controlling the display or hiding of the desktop element. After the element process determines the operation control for the desktop element, a corresponding operation interface is called, and the operation control is carried out on the desktop element through the desktop process.
In some embodiments, for element trigger events, different types of element trigger events may have different trigger type identifications. The trigger type identifier characterizes the type of element trigger event. If the desktop process monitors the element triggering event, a triggering message is returned to the element process, and the triggering message comprises a triggering type identifier. The element process determines the operation control matched with the trigger type identification, and invokes the operation interface to execute the corresponding operation control on the desktop element through the desktop process. Therefore, by carrying the trigger type identifier in the trigger message, the element process can distinguish the types of the element trigger events, and further, the operation control matched with the types of the element trigger events can be determined.
In some embodiments, determining, by the element process corresponding to the desktop element, an operation control matching the type of the trigger event may specifically include: determining a current element state of the desktop element by an element process; and determining an operation control for adjusting the desktop element from the current element state to the next element state based on the type of the trigger event. The element state may refer to a display state of the desktop element on the desktop, including, but not limited to, display content, display location, display shape, display color of the desktop element. A trigger event may trigger an adjustment of at least one element state of a desktop element, i.e., from a current element state to a next element state. For example, the desktop element is adjusted from the current display position a to the next display position B. When the element process determines the operation control matched with the type of the trigger event, the next element state of the desktop element can be determined according to the type of the trigger event, and then the operation control for adjusting the desktop element from the current element state to the next element state is determined. For example, after a key event is received by the desktop element "message", the desktop process feeds back the key event to the element process, and the element process determines that the focal position of the desktop element in the next element state should be located at a message position separated by two messages below the current focal position according to the type of the trigger event, so that operation control for switching the focal point from the current focal position to the next focal position can be determined, an operation interface is invoked, the next focal position is sent to the desktop process, and the focal point of the desktop element is switched to the next focal position through the desktop process.
In some embodiments, when there are multiple desktops, the desktop process is further configured to determine a desktop identifier of a desktop where the desktop element that receives the element triggering event is located, set the desktop identifier in the triggering message, and return the desktop identifier to the element process, so that the element process determines, according to the desktop identifier, an operation control that is matched with the triggering type identifier for the desktop element of the corresponding desktop. Specifically, for the same element process, desktop elements corresponding to different desktops may have different states. For the message process, it is possible that a message list including input contents is displayed in the desktop element "message" in the desktop 1, and the updated message list is displayed in the desktop element "message" in the desktop 2. If a touch event is received in each of the desktop 1 and desktop 2, the content in the desktop element "message" is refreshed, it will be understood that the refresh content in the two desktops is different. Therefore, the desktop identifier is carried in the triggering message returned to the element process by the desktop process, so that the scheme has better adaptability.
In some embodiments of the present application, by providing a software development kit, determining, by an element process corresponding to a desktop element, an operation control matching a type of a trigger event, performing the operation control on the desktop element by triggering a plurality of trigger events may be implemented, and different types of trigger events may have corresponding operation controls, respectively. The operation control function of the desktop elements is richer.
In some embodiments, the custom software development kit may not need to develop a listening interface for click events, considering that the system native software development kit already has the functionality to register click events to the desktop process. When registering an element triggering event to be monitored to a desktop process, the element process can register the event according to the following logic:
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 a monitoring interface, and the element triggering event needing to be monitored is registered in the desktop process.
If the element triggering event is a clicking event, the element process calls a software development kit of the system native, and the clicking triggering event is registered in the desktop process.
Similarly, considering that the system native software development kit already has a function of registering a desktop element in a desktop process, before the element process registers an element triggering event to be monitored to the desktop process, the desktop element may be registered in the desktop process by the following method:
the element process calls a system native software development toolkit, and a desktop element is registered in the desktop process; or in the case that the function interface provided by the custom software development kit comprises a registration interface, the element process can call the registration interface, and the custom software development kit calls the system native software development kit to register the desktop element in the desktop process.
In general, in the functions already possessed by the system native software development kit, the custom software development kit can directly call the system native software development kit by an element process or the custom software development kit without performing related software development, and execute related functions. Thus, the purposes of reducing code development and code redundancy are achieved.
Fig. 6 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 for providing a functional interface in a desktop process, wherein the electronic device comprises:
the event monitoring module monitors a triggering event aiming at a desktop element, wherein the triggering event characterizes an event for triggering an element process corresponding to the desktop element to perform operation control on the desktop element;
and the desktop operation module is used for determining operation control matched with the type of the trigger event by an element process corresponding to the desktop element if the trigger event is monitored, calling the functional interface and executing corresponding operation control on the desktop element by the desktop process.
In some embodiments, the functional interface comprises an operational interface, the trigger event comprises an element trigger event received by the desktop element, the element trigger event being listened to by the desktop process, wherein,
the event monitoring module is specifically configured to: if the desktop process monitors the element triggering event, returning a triggering message to the element process, wherein the triggering message comprises a triggering type identifier, and the triggering type identifier characterizes the type of the element triggering event;
the desktop operation module is specifically configured to: and the element process determines the operation control matched with the trigger type identification, invokes the operation interface and executes corresponding operation control on the desktop element through the desktop process.
In some embodiments, before the desktop process listens for the element triggering event, the event listening module is further configured to:
registering the element triggering event to be monitored to the desktop process by the element process, and monitoring the registered element triggering event through the desktop process.
In some embodiments, the functional interface comprises a listening interface, the element triggering event comprising at least one of a touch event, a key event, an input event, a focus change event, and a click event for a desktop element;
The event monitoring module is specifically configured to:
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 monitoring interface, and the element triggering event needing to be monitored is registered in the desktop process;
and if the element triggering event is a clicking event, the element process calls a software development kit of a system native, and the clicking triggering event is registered in the desktop process.
In some embodiments, before the element process registers the element triggering event to be monitored to the desktop process, the event monitoring module is further configured to:
registering the desktop element in the desktop process to display the desktop element through the desktop process, wherein:
the element process calls a system native software development kit, and the desktop element is registered in the desktop process; or (b)
The function interface provided by the software development kit comprises a registration interface, the element process calls the registration interface, the software development kit of the system native software development kit is called by the software development kit, and the desktop element is registered in the desktop process.
In some embodiments, in a case where there are a plurality of desktops, after the desktop process monitors the registered element triggering event, the event monitoring module is further configured to:
the desktop process determines a desktop identifier of a desktop where the desktop element receiving the element triggering event is located, sets the desktop identifier in the triggering message, and returns the desktop identifier to the element process, so that the element process determines operation control matched with the triggering type identifier according to the desktop identifier aiming at the desktop element of the corresponding desktop.
In some embodiments, the desktop operation module is specifically configured to:
determining, by the element process, a current element state of the desktop element;
based on the current element state, determining operation control for adjusting the desktop element from the current element state to a next element state based on the type of the trigger event.
Referring to fig. 7, an embodiment of the present application further provides an intelligent interactive tablet, where the intelligent interactive tablet includes a processor and a memory, and the memory is configured to store a computer program, and when the computer program is executed by the processor, implement the desktop element operation method described above.
The processor may be a central processing unit (Central Processing Unit, CPU). The processor may also be any other general purpose processor, digital signal processor (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof.
The memory, as a non-transitory computer readable storage medium, may 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 embodiments of the present invention. The processor executes various functional applications of the processor and data processing, i.e., implements the methods of the method embodiments described above, by running non-transitory software programs, instructions, and modules stored in memory.
The memory may include a memory program area and a memory data area, wherein the memory program area may store an operating system, at least one application program required for a function; the storage data 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 implementations, the memory optionally includes memory remotely located relative to the processor, the remote memory being connectable to the processor through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
Although embodiments of the present invention have been described in connection with the accompanying drawings, various modifications and variations may be made by those skilled in the art without departing from the spirit and scope of the invention, and such modifications and variations fall within the scope of the invention as defined by the appended claims.
Claims (16)
1. A desktop element operation method is characterized by providing a software development kit, wherein the software development kit is used for providing a functional interface in a desktop process; the method comprises the following steps:
monitoring a triggering event aiming at a desktop element, wherein the triggering event characterizes an event for triggering an element process corresponding to the desktop element to perform operation control on the desktop element;
if the triggering event is monitored, determining operation control matched with the type of the triggering event by an element process corresponding to the desktop element, calling the functional interface, and executing corresponding operation control on the desktop element by the desktop process.
2. The method of claim 1, wherein the functional interface comprises an operations interface, the triggering event comprises an element triggering event received by the desktop element, the element triggering event being listened to by the desktop process, wherein,
If the desktop process monitors the element triggering event, returning a triggering message to the element process, wherein the triggering message comprises a triggering type identifier, and the triggering type identifier characterizes the type of the element triggering event;
and the element process determines the operation control matched with the trigger type identification, invokes the operation interface and executes corresponding operation control on the desktop element through the desktop process.
3. The method of claim 2, wherein before the desktop process listens for the element triggering event, the method further comprises:
registering the element triggering event to be monitored to the desktop process by the element process, and monitoring the registered element triggering event through the desktop process.
4. The method of claim 3, wherein the functional interface comprises a listening interface, the element triggering event comprising at least one of a touch event, a key event, an input event, a focus change event, and a click event for a desktop element;
registering the element triggering event to be monitored to the desktop process comprises the following steps:
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 monitoring interface, and the element triggering event needing to be monitored is registered in the desktop process;
and if the element triggering event is a clicking event, the element process calls a software development kit of a system native, and the clicking triggering event is registered in the desktop process.
5. The method of claim 3, wherein before the element process registers the element trigger event to be listened to the desktop process, the method further comprises:
registering the desktop element in the desktop process to display the desktop element through the desktop process, wherein:
the element process calls a system native software development kit, and the desktop element is registered in the desktop process; or (b)
The function interface provided by the software development kit comprises a registration interface, the element process calls the registration interface, the software development kit of the system native software development kit is called by the software development kit, and the desktop element is registered in the desktop process.
6. The method of claim 2, wherein, in the case where there are multiple desktops, after the desktop process overhears the registered element trigger event, the method further comprises:
the desktop process determines a desktop identifier of a desktop where the desktop element receiving the element triggering event is located, sets the desktop identifier in the triggering message, and returns the desktop identifier to the element process, so that the element process determines operation control matched with the triggering type identifier according to the desktop identifier aiming at the desktop element of the corresponding desktop.
7. The method of claim 1, wherein the determining, by the element process corresponding to the desktop element, an operational control that matches the type of the trigger event comprises:
determining, by the element process, a current element state of the desktop element;
based on the current element state, determining operation control for adjusting the desktop element from the current element state to a next element state based on the type of the trigger event.
8. An electronic device, wherein the electronic device provides a software development kit for providing a functional interface in a desktop process; the electronic device includes:
The event monitoring module monitors a triggering event aiming at a desktop element, wherein the triggering event characterizes an event for triggering an element process corresponding to the desktop element to perform operation control on the desktop element;
and the desktop operation module is used for determining operation control matched with the type of the trigger event by an element process corresponding to the desktop element if the trigger event is monitored, calling the functional interface and executing corresponding operation control on the desktop element by the desktop process.
9. The electronic device of claim 8, wherein the functional interface comprises an operational interface, the trigger event comprises an element trigger event received by the desktop element, the element trigger event being listened to by the desktop process, wherein,
the event monitoring module is specifically configured to: if the desktop process monitors the element triggering event, returning a triggering message to the element process, wherein the triggering message comprises a triggering type identifier, and the triggering type identifier characterizes the type of the element triggering event;
the desktop operation module is specifically configured to: and the element process determines the operation control matched with the trigger type identification, invokes the operation interface and executes corresponding operation control on the desktop element through the desktop process.
10. The electronic device of claim 9, wherein the event listening module is further to, prior to the desktop process listening for the element triggering event:
registering the element triggering event to be monitored to the desktop process by the element process, and monitoring the registered element triggering event through the desktop process.
11. The electronic device of claim 10, wherein the functional interface comprises a listening interface, the element triggering event comprising at least one of a touch event, a key event, an input event, a focus change event, and a click event for a desktop element;
the event monitoring module is specifically configured to:
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 monitoring interface, and the element triggering event needing to be monitored is registered in the desktop process;
and if the element triggering event is a clicking event, the element process calls a software development kit of a system native, and the clicking triggering event is registered in the desktop process.
12. The electronic device of claim 10, wherein the event listening module is further to, prior to the element process registering the element trigger event to be listened to with the desktop process:
Registering the desktop element in the desktop process to display the desktop element through the desktop process, wherein:
the element process calls a system native software development kit, and the desktop element is registered in the desktop process; or (b)
The function interface provided by the software development kit comprises a registration interface, the element process calls the registration interface, the software development kit of the system native software development kit is called by the software development kit, and the desktop element is registered in the desktop process.
13. The electronic device of claim 9, wherein, in the case where there are multiple desktops, the desktop process, after hearing the registered element trigger event, the event listening module is further to:
the desktop process determines a desktop identifier of a desktop where the desktop element receiving the element triggering event is located, sets the desktop identifier in the triggering message, and returns the desktop identifier to the element process, so that the element process determines operation control matched with the triggering type identifier according to the desktop identifier aiming at the desktop element of the corresponding desktop.
14. The electronic device of claim 8, wherein the desktop operation module is specifically configured to:
determining, by the element process, a current element state of the desktop element;
based on the current element state, determining operation control for adjusting the desktop element from the current element state to a next element state based on the type of the trigger event.
15. A computer readable storage medium for storing a computer program which, when executed by a processor, implements the method of any one of claims 1 to 7.
16. A smart interactive tablet, characterized in that it comprises a processor and a memory for storing a computer program which, when executed by the processor, implements the method according to any one of claims 1 to 7.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2022/100601 WO2023245526A1 (en) | 2022-06-23 | 2022-06-23 | Desktop element operation method, electronic device and intelligent interaction tablet |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116420138A true CN116420138A (en) | 2023-07-11 |
Family
ID=87049662
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202280006530.XA Pending CN116420138A (en) | 2022-06-23 | 2022-06-23 | Desktop element operation method, electronic equipment and intelligent interaction panel |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN116420138A (en) |
| WO (1) | WO2023245526A1 (en) |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109491731B (en) * | 2018-09-07 | 2022-03-22 | 咪咕文化科技有限公司 | Control method and device for suspension button and storage medium |
| WO2020248172A1 (en) * | 2019-06-12 | 2020-12-17 | 深圳市大疆创新科技有限公司 | Functional module invoking method, device and computer readable storage medium |
| US11188397B2 (en) * | 2019-10-18 | 2021-11-30 | Splunk Inc. | Mobile application for an information technology (IT) and security operations application |
| CN115022695B (en) * | 2021-03-04 | 2023-09-19 | 聚好看科技股份有限公司 | Display device and Widget control display method |
| CN113094123A (en) * | 2021-03-23 | 2021-07-09 | 北京达佳互联信息技术有限公司 | Method and device for realizing functions in application program, electronic equipment and storage medium |
-
2022
- 2022-06-23 WO PCT/CN2022/100601 patent/WO2023245526A1/en unknown
- 2022-06-23 CN CN202280006530.XA patent/CN116420138A/en active Pending
Also Published As
| Publication number | Publication date |
|---|---|
| WO2023245526A1 (en) | 2023-12-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6640909B2 (en) | Theme display method and related devices | |
| CN109062479B (en) | Split screen application switching method and device, storage medium and electronic equipment | |
| CN106201219B (en) | The quick call method of function of application and system | |
| CA3053980A1 (en) | Task management based on instant communication message | |
| CN104158972A (en) | Method for calling third-party application in conversation process and user terminal | |
| CN101834960A (en) | System and method for accessing internet protocol phone based applications | |
| CN112162807A (en) | Function execution method and device | |
| CN105468238A (en) | File icon display method and device and equipment | |
| CN112199146A (en) | Interface switching method and device and electronic equipment | |
| CN109983428B (en) | Application operation method and device | |
| CN110381192B (en) | Virtual key control method and mobile terminal | |
| CN110851036A (en) | Parameter adjusting method and device for electrical equipment and storage medium | |
| CN110162249A (en) | A kind of control application program image target method and device, equipment and storage medium | |
| CN112286611B (en) | Icon display method and device and electronic equipment | |
| CN116420138A (en) | Desktop element operation method, electronic equipment and intelligent interaction panel | |
| CN102917320A (en) | Method and device for transmitting voice message | |
| CN102648617A (en) | Mobile terminal device and mobile terminal device function setting method | |
| CN111104035A (en) | Display interface control method, device, equipment and computer readable storage medium | |
| CN113872849B (en) | Message interaction method and device and electronic equipment | |
| CN111741164B (en) | Sound mode switching method and device and computer readable storage medium | |
| CN114397989A (en) | Parameter value setting method and device, electronic equipment and storage medium | |
| CN104951222A (en) | Alarm clock control method and terminal | |
| CN112328197A (en) | Multi-screen display method and device and storage medium | |
| CN114868104A (en) | Mobile terminal control method, mobile terminal, and computer-readable storage medium | |
| CN111352548A (en) | Message notification method, device, terminal device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |