WO2023245526A1 - Procédé de fonctionnement d'élément de bureau, dispositif électronique et tablette d'interaction intelligente - Google Patents

Procédé de fonctionnement d'élément de bureau, dispositif électronique et tablette d'interaction intelligente Download PDF

Info

Publication number
WO2023245526A1
WO2023245526A1 PCT/CN2022/100601 CN2022100601W WO2023245526A1 WO 2023245526 A1 WO2023245526 A1 WO 2023245526A1 CN 2022100601 W CN2022100601 W CN 2022100601W WO 2023245526 A1 WO2023245526 A1 WO 2023245526A1
Authority
WO
WIPO (PCT)
Prior art keywords
desktop
event
trigger
events
software development
Prior art date
Application number
PCT/CN2022/100601
Other languages
English (en)
Chinese (zh)
Inventor
王家宇
Original Assignee
广州视源电子科技股份有限公司
广州视源创新科技有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 广州视源电子科技股份有限公司, 广州视源创新科技有限公司 filed Critical 广州视源电子科技股份有限公司
Priority to PCT/CN2022/100601 priority Critical patent/WO2023245526A1/fr
Priority to CN202280006530.XA priority patent/CN116420138A/zh
Publication of WO2023245526A1 publication Critical patent/WO2023245526A1/fr

Links

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

Definitions

  • 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.
  • 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.
  • 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.
  • the operation control function for desktop elements is relatively simple.
  • 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.
  • 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;
  • 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 functional interface includes an operation interface
  • the triggering event includes an element triggering event received by the desktop element
  • the element triggering event is monitored by the desktop process
  • 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 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 functional interface includes a listening interface
  • 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:
  • the element process calls the listening interface and registers the element triggering event that needs to be monitored in the desktop process;
  • the element process calls the system's native software development tool kit to register the click triggering event in the desktop process.
  • the method before the element process registers the element trigger event that needs to be monitored to the desktop process, the method further includes:
  • the element process calls the system's native software development tool kit to register the desktop element in the desktop process;
  • 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 functional interface provided by the software development toolkit.
  • the method 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.
  • the element process corresponding to the desktop element determines the operation control that matches the type of the trigger event, including:
  • an operation control for adjusting the desktop element from the current element state to the next element state is determined.
  • 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 functional interface includes an operation interface
  • the triggering event includes an element triggering event received by the desktop element
  • the element triggering event is monitored by the desktop process
  • 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 event listening module before the desktop process listens to the element trigger 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 functional interface includes a listening interface
  • the element triggering events include at least one of touch events, key events, input events, focus change events, and click events for desktop elements
  • the event monitoring module is specifically used for:
  • the element process calls the listening interface and registers the element triggering event that needs to be monitored in the desktop process;
  • the element process calls the system's native software development tool kit to register the click triggering event in the desktop process.
  • the event listening module is also used to:
  • the element process calls the system's native software development tool kit to register the desktop element in the desktop process;
  • 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 functional interface provided by the software development toolkit.
  • the event listening module is also used 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 desktop operation module is specifically used to:
  • an operation control for adjusting the desktop element from the current element state to the next element state is determined.
  • 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.
  • 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.
  • the computer program is executed by the processor, the above-mentioned functions are implemented. Methods.
  • 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.
  • 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
  • FIG. 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.
  • 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.
  • the content displayed as Application 1, Application 2, time and date, information, and buttons can be collectively referred to as desktop elements.
  • 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.
  • desktop processes may provide operational control over desktop elements.
  • the desktop process can control the arrangement position, display color, etc. of desktop elements on the desktop.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the operating system can be the Android operating system, and the system's native software development kit can also be called Android SDK.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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”
  • 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.
  • the display color of the desktop element can be updated.
  • the display color of the desktop element can be updated.
  • the display color of the desktop element can be updated. , which can update the display content of desktop elements.
  • 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.
  • desktop elements 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Figure 5 is a detailed schematic diagram of the desktop element "message” in Figure 4.
  • the desktop element “message” may include a sliding area 51 and a message area 52 .
  • 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.
  • 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.
  • the user 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.
  • the currently selected message is the first message in the message area 52.
  • 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.
  • 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.
  • the desktop element "Message" may also include an input area 53.
  • the user can input query conditions, so that the message area 52 displays messages that satisfy the query conditions.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 .
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • triggering events may include, but are not limited to, the above element triggering events.
  • 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.
  • element processes may have a matching relationship between trigger event types and operation controls.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the desktop process 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.
  • 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.
  • 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.
  • the customized software development kit does not need to develop a listening interface for click events.
  • 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:
  • the element process calls the listening interface and registers the element trigger event that needs to be monitored in the desktop process.
  • the element process calls the system's native software development tool kit to register the click trigger event in 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.
  • 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.
  • 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, and the software development kit is used to provide functional interfaces in the 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 functional interface includes an operation interface
  • the triggering event includes an element triggering event received by the desktop element
  • the element triggering event is monitored by the desktop process
  • 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 event listening module before the desktop process listens to the element trigger 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 functional interface includes a listening interface
  • the element triggering events include at least one of touch events, key events, input events, focus change events, and click events for desktop elements
  • the event monitoring module is specifically used for:
  • the element process calls the listening interface and registers the element triggering event that needs to be monitored in the desktop process;
  • the element process calls the system's native software development tool kit to register the click triggering event in the desktop process.
  • the event listening module is also used to:
  • the element process calls the system's native software development tool kit to register the desktop element in the desktop process;
  • 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 functional interface provided by the software development toolkit.
  • the event listening module is also used 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 desktop operation module is specifically used to:
  • an operation control for adjusting the desktop element from the current element state to the next element state is determined.
  • 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.
  • 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.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • Chips such as programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or combinations of these types of chips.
  • 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

Procédé de fonctionnement d'élément de bureau, dispositif électronique et tablette d'interaction intelligente. Le procédé de fonctionnement d'élément de bureau fournit un kit de développement de logiciel, et le kit de développement de logiciel est utilisé pour fournir une interface fonctionnelle dans un processus de bureau. Le procédé de fonctionnement d'élément de bureau consiste à : surveiller un événement de déclenchement pour un élément de bureau (S31), l'événement de déclenchement représentant un événement qui déclenche un processus d'élément correspondant à l'élément de bureau pour réaliser une commande de fonctionnement sur l'élément de bureau ; et, si l'événement de déclenchement est détecté, déterminer, par le processus d'élément correspondant à l'élément de bureau, une commande de fonctionnement correspondant au type de l'événement de déclenchement et appeler une interface fonctionnelle pour exécuter la commande de fonctionnement correspondante sur l'élément de bureau au moyen d'un processus de bureau (S32). Dans le procédé, l'élément de bureau comprend des fonctions de commande de fonctionnement relativement riches.
PCT/CN2022/100601 2022-06-23 2022-06-23 Procédé de fonctionnement d'élément de bureau, dispositif électronique et tablette d'interaction intelligente WO2023245526A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2022/100601 WO2023245526A1 (fr) 2022-06-23 2022-06-23 Procédé de fonctionnement d'élément de bureau, dispositif électronique et tablette d'interaction intelligente
CN202280006530.XA CN116420138A (zh) 2022-06-23 2022-06-23 一种桌面元素操作方法、电子设备以及智能交互平板

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/100601 WO2023245526A1 (fr) 2022-06-23 2022-06-23 Procédé de fonctionnement d'élément de bureau, dispositif électronique et tablette d'interaction intelligente

Publications (1)

Publication Number Publication Date
WO2023245526A1 true WO2023245526A1 (fr) 2023-12-28

Family

ID=87049662

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/100601 WO2023245526A1 (fr) 2022-06-23 2022-06-23 Procédé de fonctionnement d'élément de bureau, dispositif électronique et tablette d'interaction intelligente

Country Status (2)

Country Link
CN (1) CN116420138A (fr)
WO (1) WO2023245526A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109491731A (zh) * 2018-09-07 2019-03-19 咪咕文化科技有限公司 一种悬浮按钮的控制方法、装置及存储介质
CN111684420A (zh) * 2019-06-12 2020-09-18 深圳市大疆创新科技有限公司 功能模块的调用方法、设备、计算机可读存储介质
US20210117251A1 (en) * 2019-10-18 2021-04-22 Splunk Inc. Mobile application for an information technology (it) and security operations application
CN113094123A (zh) * 2021-03-23 2021-07-09 北京达佳互联信息技术有限公司 应用程序中功能的实现方法、装置、电子设备和存储介质
CN114510170A (zh) * 2021-03-04 2022-05-17 聚好看科技股份有限公司 一种组件展示方法及显示设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109491731A (zh) * 2018-09-07 2019-03-19 咪咕文化科技有限公司 一种悬浮按钮的控制方法、装置及存储介质
CN111684420A (zh) * 2019-06-12 2020-09-18 深圳市大疆创新科技有限公司 功能模块的调用方法、设备、计算机可读存储介质
US20210117251A1 (en) * 2019-10-18 2021-04-22 Splunk Inc. Mobile application for an information technology (it) and security operations application
CN114510170A (zh) * 2021-03-04 2022-05-17 聚好看科技股份有限公司 一种组件展示方法及显示设备
CN113094123A (zh) * 2021-03-23 2021-07-09 北京达佳互联信息技术有限公司 应用程序中功能的实现方法、装置、电子设备和存储介质

Also Published As

Publication number Publication date
CN116420138A (zh) 2023-07-11

Similar Documents

Publication Publication Date Title
JP6640909B2 (ja) テーマ表示方法および関連装置
CN109062479B (zh) 分屏应用切换方法、装置、存储介质和电子设备
CN108205430B (zh) 双屏移动终端、相应操控方法及存储介质
CN110515510B (zh) 数据处理方法、装置、设备及存储介质
US20170024086A1 (en) System and methods for detection and handling of focus elements
CN110286978B (zh) 窗口层级切换的方法、装置、设备和存储介质
WO2022063165A1 (fr) Procédé et appareil d'exécution de fonction
US20180224997A1 (en) Method and system for one-handed operations of mobile terminal
WO2021036926A1 (fr) Procédé d'affichage et dispositif électronique
US11507244B2 (en) Window adjustment method, window adjustment device and mobile terminal
WO2018086454A1 (fr) Procédé et dispositif de traitement de données de page
CN109683739B (zh) 调整操作界面的方法和装置，存储介质和电子设备
WO2023098732A1 (fr) Procédé et appareil d'interaction entre dispositifs, dispositif électronique, et support de stockage
CN113051493A (zh) 应用程序展示方法、装置、存储介质以及终端
US20240231576A9 (en) Control method and apparatus for displaying multimedia content, electronic device and medium
CN106528284B (zh) 应用程序配置方法、装置及终端设备
WO2019019158A1 (fr) Procédé et dispositif pour faire fonctionner une application
US11048409B2 (en) Method and apparatus for executing function of fixed virtual keys of mobile terminal with a single hand, and mobile terminal
WO2024099102A1 (fr) Procédé et appareil d'affichage de commande, dispositif électronique et support d'enregistrement lisible
CN112286611B (zh) 图标显示方法、装置和电子设备
WO2023245526A1 (fr) Procédé de fonctionnement d'élément de bureau, dispositif électronique et tablette d'interaction intelligente
CN109064527B (zh) 动态配置动画的实现方法、装置、存储介质及安卓终端
US20240095141A1 (en) Displaying information flow
CN113872849B (zh) 消息交互方法、装置及电子设备
CN106375190B (zh) 一种即时通讯软件界面拆分与合并的显示方法及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22947301

Country of ref document: EP

Kind code of ref document: A1