Soft keyboard event scheduling method and device, equipment and storage medium thereof

Abstract

The invention belongs to the technical field of operation and maintenance management, and relates to a soft keyboard event scheduling method and device, equipment and a storage medium thereof. The soft keyboard event is monitored through the preset event monitor, and the corresponding soft keyboard event is executed by adopting the event proxy function mode according to the monitoring result, so that the soft keyboard event is reasonably scheduled in the event manager, the monitor and the proxy processing mode, and later unified maintenance and management by operation and maintenance personnel are facilitated. The soft keyboard event scheduling method is applied to soft keyboard event scheduling and management in a financial or medical online business processing platform, the soft keyboard event can be reasonably scheduled, and operation and maintenance personnel can conveniently carry out later unified maintenance and management.

Description

Technical Field

[0001] This application relates to the field of operation and maintenance management technology, and is applied to the optimization and improvement of online service products in finance or healthcare. It relates to a soft keyboard event scheduling method, device, equipment and its storage medium. Background Technology

[0002] Currently, in interface operation software, a common scenario is that the UI needs to be changed according to the appearance or hiding of the keyboard, such as the input box following the top of the keyboard.

[0003] Since keyboard notifications are global across the entire operating software, it is common to encounter situations where keyboard events from page B are received in the keyboard listener callback of page A, leading to chaotic listener management and hindering maintenance personnel from performing subsequent maintenance. Summary of the Invention

[0004] The purpose of this application is to provide a soft keyboard event scheduling method, apparatus, device and its storage medium to avoid chaotic soft keyboard monitoring management. By uniformly managing soft keyboard events, it also facilitates maintenance personnel in later maintenance and management.

[0005] Firstly, embodiments of this application provide a soft keyboard event scheduling method, which adopts the following technical solution:

[0006] A soft keyboard event dispatching method includes the following steps:

[0007] Initialize the soft keyboard event manager, wherein the soft keyboard event manager includes a first manager, which integrates the overall events of the soft keyboard in the parent container component, including the overall display event or the overall insertion event of the soft keyboard in the parent container component;

[0008] Listen for soft keyboard events using a pre-defined event listener;

[0009] When the soft keyboard is detected to be displayed or inserted in the parent container component, determine whether the soft keyboard service application is currently in a closed state.

[0010] If the soft keyboard service program is not currently in a closed state, a preset alarm event will be initiated to trigger a service alarm.

[0011] If the soft keyboard service program is currently in a closed state, a start-up overall display event or an overall insertion event is triggered from the first manager, and a preset soft keyboard event delegate function is called back in the corresponding overall event;

[0012] The parameter information required when the soft keyboard is fully displayed or inserted is passed to the soft keyboard event delegate function to display or insert the soft keyboard in the parent container component. The parameter information required when the soft keyboard is fully displayed or inserted includes: the height information, width information, style information, and position information of the soft keyboard.

[0013] Secondly, embodiments of this application also provide a soft keyboard event scheduling device, which adopts the following technical solution:

[0014] A soft keyboard event scheduling device, comprising:

[0015] An initialization module is used to initialize the soft keyboard event manager, wherein the soft keyboard event manager includes a first manager, which integrates the overall events of the soft keyboard in the parent container component. The overall events include the overall display event or the overall insertion event of the soft keyboard in the parent container component.

[0016] The event listener module is used to listen for soft keyboard events through preset event listeners;

[0017] The first judgment module is used to determine whether the soft keyboard service program is currently in a closed state when it hears the overall display event or overall insertion event of the soft keyboard in the parent container component.

[0018] The first branch processing module is used to initiate a preset alarm event to provide a service alarm if the soft keyboard service program is not currently in a closed state.

[0019] The second branch processing module is used to trigger a start-up overall display event or an overall insertion event from the first manager if the soft keyboard service program is currently in a closed state, and to call back a preset soft keyboard event proxy function in the corresponding overall event;

[0020] The first parameter passing scheduling module is used to pass the parameter information that needs to be carried when the soft keyboard is displayed or inserted as a whole to the soft keyboard event delegate function, so as to display or insert the soft keyboard in the parent container component. The parameter information that needs to be carried when the soft keyboard is displayed or inserted as a whole includes: the height information, width information, style information, and position information of the soft keyboard.

[0021] Thirdly, embodiments of this application also provide a computer device that adopts the technical solution described below:

[0022] A computer device includes a memory and a processor, wherein the memory stores computer-readable instructions, and the processor executes the computer-readable instructions to implement the steps of the soft keyboard event scheduling method described above.

[0023] Fourthly, embodiments of this application also provide a computer-readable storage medium, which adopts the technical solutions described below:

[0024] A computer-readable storage medium storing computer-readable instructions, which, when executed by a processor, implement the steps of the soft keyboard event scheduling method described above.

[0025] Compared with the prior art, the embodiments of this application have the following main advantages:

[0026] The soft keyboard event scheduling method described in this application initializes a soft keyboard event manager; listens for soft keyboard events using a preset event listener; and executes the corresponding soft keyboard events using an event proxy function pattern based on the listening results. This achieves rational scheduling of soft keyboard events under the event manager, listener, and proxy processing modes, facilitating unified maintenance and management by operations and maintenance personnel. Applying this soft keyboard event scheduling method to the soft keyboard event scheduling and management of online business processing platforms in the financial or medical fields enables rational scheduling of soft keyboard events, further facilitating unified maintenance and management by operations and maintenance personnel. Attached Figure Description

[0027] To more clearly illustrate the solutions in this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0028] Figure 1 This is an exemplary system architecture diagram to which this application can be applied;

[0029] Figure 2 This is a flowchart of an embodiment of a soft keyboard event scheduling method according to this application;

[0030] Figure 3 This is a flowchart of another embodiment of a soft keyboard event scheduling method according to this application;

[0031] Figure 4 This is a flowchart of another embodiment of a soft keyboard event scheduling method according to this application;

[0032] Figure 5 This is a flowchart of another embodiment of a soft keyboard event scheduling method according to this application;

[0033] Figure 6This is a flowchart illustrating a specific embodiment of the soft keyboard event response result judgment and processing in the soft keyboard event scheduling method.

[0034] Figure 7 This is a schematic diagram of one embodiment of a soft keyboard event scheduling device according to this application;

[0035] Figure 8 This is a schematic diagram of the structure of one embodiment of the computer device according to this application. Detailed Implementation

[0036] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the terminology used herein in the specification of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "comprising" and "having," and any variations thereof, in the specification, claims, and foregoing drawings of this application, are intended to cover non-exclusive inclusion. The terms "first," "second," etc., in the specification, claims, or foregoing drawings of this application are used to distinguish different objects, not to describe a particular order.

[0037] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0038] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.

[0039] like Figure 1 As shown, system architecture 100 may include terminal device 101, network 102, and server 103. Terminal device 101 may be a laptop 1011, tablet 1012, or mobile phone 1013. Network 102 is used as a medium to provide a communication link between terminal device 101 and server 103. Network 102 may include various connection types, such as wired, wireless communication links, or fiber optic cables.

[0040] Users can use terminal device 101 to interact with server 103 via network 102 to receive or send messages, etc. Various communication client applications can be installed on terminal device 101, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social media platform software, etc.

[0041] Terminal device 101 can be various electronic devices with a display screen and support web browsing. In addition to laptop computer 1011, tablet computer 1012 or mobile phone 1013, terminal device 101 can also be e-book reader, MP3 player (Moving Picture Experts Group Audio Layer III), MP4 player (Moving Picture Experts Group Audio Layer IV), laptop computer and desktop computer, etc.

[0042] Server 103 can be a server that provides various services, such as a backend server that provides support for the pages displayed on terminal device 101.

[0043] It should be noted that the soft keyboard event scheduling method provided in this application embodiment is generally executed by a server, and correspondingly, a soft keyboard event scheduling device is generally set in the server.

[0044] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0045] Continue to refer Figure 2 The diagram illustrates a flowchart of an embodiment of a soft keyboard event scheduling method according to this application. The soft keyboard event scheduling method includes the following steps:

[0046] Step 201: Initialize the soft keyboard event manager.

[0047] The soft keyboard event manager includes a first manager, which integrates the overall events of the soft keyboard in the parent container component. The overall events include the overall display event or the overall insertion event of the soft keyboard in the parent container component.

[0048] In this embodiment, the soft keyboard specifically refers to an interface keyboard displayed within the target interface that allows for clickable input. For example, the interface keyboard that pops up in an intelligent customer service dialogue interface or an after-sales service chat interface.

[0049] By initializing the soft keyboard event manager and combining it with the event manager to manage soft keyboard events, it is possible to uniformly manage events such as the use and display of the soft keyboard, which is beneficial for maintenance personnel to carry out later maintenance and management.

[0050] Step 202: Listen for soft keyboard events using a preset event listener.

[0051] In this embodiment, the step of listening to soft keyboard events through a preset event listener is specifically implemented by listening to the soft keyboard event manager through the event listener, thereby enabling the listening of all soft keyboard events in the soft keyboard event manager.

[0052] Step 203: When the overall display event or overall insertion event of the soft keyboard in the parent container component is detected, determine whether the soft keyboard service program is currently in a closed state.

[0053] In this embodiment, if the soft keyboard service program is not currently in a closed state, it means that the soft keyboard service program is providing relevant soft keyboard services to the current interface, that is, the soft keyboard is displayed in the current interface; if the soft keyboard service program is currently in a closed state, it means that the soft keyboard service program is not providing relevant soft keyboard services to the current interface, that is, the soft keyboard is not displayed in the current interface.

[0054] Step 204: If the soft keyboard service program is not currently in a closed state, then a preset alarm event is initiated to issue a service alarm.

[0055] Specifically, if the soft keyboard service program is not currently in a closed state, it means that the soft keyboard service program is providing relevant soft keyboard services to the current interface, that is, the soft keyboard is already displayed in the current interface. At this time, the preset alarm event is activated to provide service alarms. It is not to execute error alarms, but to provide alarm reminders for changes in the display status of the soft keyboard in the current interface, such as changes in the display position in the interface, changes in the inserted parent container component, etc.

[0056] Step 205: If the soft keyboard service program is currently in a closed state, trigger a start-up overall display event or an overall insertion event from the first manager, and call back the preset soft keyboard event delegate function in the corresponding overall event.

[0057] Specifically, if the soft keyboard service program is currently in a closed state, it means that the soft keyboard service program is not providing relevant soft keyboard services on the current interface, that is, the soft keyboard is not displayed on the current interface. At this time, a start overall display event or an overall insertion event is triggered from the first manager, and a preset soft keyboard event delegate function is called back in the corresponding overall event to display the soft keyboard on the current interface in the form of an event delegate function.

[0058] Step 206: Pass the parameter information required when the soft keyboard is displayed or inserted as a whole into the soft keyboard event delegate function so as to display or insert the soft keyboard in the parent container component.

[0059] The parameters that the soft keyboard needs to carry when it is displayed or inserted as a whole include: the height, width, style, and position of the soft keyboard.

[0060] Specifically, by passing the relevant parameter information required for the display or insertion of the soft keyboard into the soft keyboard event delegate function, the soft keyboard can be displayed or inserted into the current interface.

[0061] In this embodiment, a soft keyboard event manager is initialized; soft keyboard events are monitored through preset event listeners; and corresponding soft keyboard events are executed using an event proxy function pattern based on the monitoring results. This achieves rational scheduling of soft keyboard events under the event manager, listener, and proxy processing modes, facilitating unified maintenance and management by operations and maintenance personnel. Applying this soft keyboard event scheduling method to the soft keyboard event scheduling and management of online business processing platforms in the financial or medical fields enables rational scheduling of soft keyboard events, further facilitating unified maintenance and management by operations and maintenance personnel.

[0062] In this embodiment, the overall event also includes the overall hiding event or overall closing event of the soft keyboard in the parent container component.

[0063] Continue to refer Figure 3 The diagram illustrates a flowchart of another embodiment of a soft keyboard event scheduling method according to this application. After step 202 is executed, the soft keyboard event scheduling method further includes the following steps:

[0064] Step 301: When the overall hidden event or overall closed event of the soft keyboard in the parent container component is detected, determine whether the soft keyboard service program is currently in a closed state.

[0065] Step 302: If the soft keyboard service program is currently in a closed state, then a preset alarm event is initiated to trigger a service alarm.

[0066] Specifically, if the soft keyboard service program is currently in a closed state, it means that the soft keyboard service program is not providing relevant soft keyboard services on the current interface, that is, the soft keyboard is not displayed on the current interface. At this time, a preset alarm event is initiated to issue a service alarm, which is an event scheduling error alarm. For example, an erroneous event scheduling command occurs when the soft keyboard service program is currently in a closed state.

[0067] Step 303: If the soft keyboard service program is not currently in a closed state, trigger a start-up overall hiding event or an overall shutdown event from the first manager, and call back the preset soft keyboard event delegate function in the corresponding overall event;

[0068] Step 304: Pass the parameter information required when the soft keyboard is completely hidden or closed to the soft keyboard event delegate function, so as to hide or close the soft keyboard in the parent container component.

[0069] The parameters that the soft keyboard needs to carry when it is completely hidden or completely turned off include at least: the stop status parameters of the soft keyboard service program and the control parameters when the soft keyboard is not displayed on the page.

[0070] It should be understood that the above Figure 3 The event dispatching method shown in the image is to simply close or hide the corresponding soft keyboard in the current interface as a whole, without involving the parent container component of the soft keyboard to close or hide.

[0071] Continue to refer Figure 4 The diagram illustrates a flowchart of another embodiment of a soft keyboard event scheduling method according to this application. After step 202 is executed, the soft keyboard event scheduling method further includes the following steps:

[0072] Step 401: When the overall close event or overall hide event corresponding to the parent container component where the soft keyboard is located is detected, determine whether the soft keyboard service program is currently in a closed state.

[0073] Specifically, the overall close event or overall hide event corresponding to the parent container component can be an event other than the soft keyboard event manager. The event listener used can be the same listener that listens for soft keyboard events, or it can be a different listener that listens for soft keyboard events.

[0074] Step 402: If the soft keyboard service program is currently in a closed state, then execute the overall close event or overall hide event corresponding to the parent container component.

[0075] Step 403: If the soft keyboard service program is not currently in a closed state, call the overall hide event or overall close event corresponding to the soft keyboard from the first manager, and add the overall hide event or overall close event corresponding to the soft keyboard as a child event to the overall close event or overall hide event corresponding to the parent container component.

[0076] Specifically, Figure 4 The processing steps provided in the document specify the event scheduling when the soft keyboard, as a child component, is hidden or closed as a child component when the parent container component containing the soft keyboard is completely closed or hidden.

[0077] In this embodiment, the soft keyboard event manager also includes a second manager, which integrates local events of the soft keyboard. Specifically, the local events can be understood as local processing events generated when a key on the soft keyboard is clicked, that is, events that do not involve overall scheduling of the soft keyboard, such as: clicking the 'a' key on the soft keyboard, typing on the soft keyboard, clicking to switch the input case mode of the soft keyboard, etc.

[0078] Continue to refer Figure 5 The diagram illustrates a flowchart of another embodiment of a soft keyboard event scheduling method according to this application. After step 202 is executed, the soft keyboard event scheduling method further includes the following steps:

[0079] Step 501: When a local event of the soft keyboard is detected, determine whether the soft keyboard service program is currently in the program startup state.

[0080] Step 502: If the soft keyboard service program is not currently in the program startup state, then a preset alarm event is initiated to issue a service alarm.

[0081] Specifically, if the soft keyboard service program is not currently in the program startup state, but the soft keyboard is displayed on the current interface and partial event operations can be performed, it indicates that the soft keyboard service program has encountered an obvious error or execution disorder. The service alarm here is an error alarm to prompt the server to troubleshoot the soft keyboard service program.

[0082] Step 503: If the soft keyboard service program is currently in the program startup state, then trigger the startup of the corresponding local event from the second manager, and call back the preset soft keyboard local event delegate function in the local event;

[0083] Specifically, if the soft keyboard service program is currently in the program startup state, when a local event is triggered, it is also triggered in proxy mode through the event manager, which facilitates comprehensive management of local events and is beneficial for maintenance personnel to perform later maintenance, operation log reverse lookup and management.

[0084] Step 504: Pass the parameter information required for the implementation of the local event to the soft keyboard local event delegate function to complete the local operation on the soft keyboard. The parameter information required for the local event includes: page response, page feedback and / or page change information after the local event operation is executed.

[0085] In this embodiment, the step of listening to soft keyboard events through a preset event listener specifically includes: using a KVC listening mechanism to listen to the soft keyboard events. Specifically, the KVC listening mechanism uses the NSKeyValueObserving protocol to listen for changes in the soft keyboard object's properties, thereby achieving the listening of soft keyboard events. Specifically, the NSKeyValueObserving protocol is used to listen for changes in the soft keyboard object's properties in the event manager, thereby achieving the listening of all events in the first and second managers.

[0086] In this embodiment, the step of passing the parameter information required when displaying or inserting the soft keyboard as a whole into the soft keyboard event delegate function to display or insert the soft keyboard in the parent container component further includes: when displaying or inserting the soft keyboard in the parent container component, setting the display or insertion mode of the soft keyboard in the parent container component to block-level mode, specifically, updating the display attribute field of the soft keyboard to the block field by updating the settings.

[0087] Specifically, when displaying the soft keyboard as a whole or inserting event operations, the soft keyboard is treated as a whole by setting the CSS style of the interface, thus avoiding affecting the operation of other interface components.

[0088] In this embodiment, after executing the step of passing the parameter information required for displaying or inserting the soft keyboard as a whole into the soft keyboard event delegate function to display or insert the soft keyboard in the parent container component, the method further includes: identifying the position display state of the soft keyboard in the parent container component according to preset state control parameters, wherein the position display state includes a fixed position display state and a floating position display state; if the position display state of the soft keyboard in the parent container component is a fixed position display state, then the delegate function corresponding to the fixed position display setting of the soft keyboard is called back, and the corresponding fixed position parameters are passed into the delegate function; if the position display state of the soft keyboard in the parent container component is a floating position display state, then the delegate function corresponding to the floating position display setting of the soft keyboard is called back, and the corresponding floating position parameters are passed into the delegate function.

[0089] Specifically, after the soft keyboard is displayed as a whole or inserted into the current interface, it can be set to either a fixed-position display state or a floating-position display state within the parent container component based on preset display state control fields. In the fixed-position display state, for example, the soft keyboard is always displayed at the bottom of the current interface, meaning its position does not change with other operations on the interface; its position is fixed relative to the entire current interface. In the floating-position display state, for example, the soft keyboard's display adaptively floats and adjusts according to the actual changes in the interface as other operations occur. This achieves soft keyboard display control based on the actual processing of the interface, making the soft keyboard display more flexible and adaptable.

[0090] In this embodiment, the step of passing the parameter information required when the soft keyboard is completely hidden or completely closed to the soft keyboard event delegate function in order to hide or close the soft keyboard in the parent container component further includes: when hiding or closing the soft keyboard in the parent container component, setting the hiding or closing method of the soft keyboard in the parent container component to block level mode, specifically, updating the display attribute field of the soft keyboard to the block field by updating the settings.

[0091] Specifically, when performing overall hiding or disabling operations on the soft keyboard, the soft keyboard is treated as a whole and processed as a single block through CSS style settings, thus avoiding any impact on other UI components.

[0092] Continue to refer Figure 6 In some specific implementations, the soft keyboard event scheduling method described in this embodiment further includes a step of judging and processing the soft keyboard event response results. Figure 6 This is a flowchart illustrating a specific embodiment of the soft keyboard event response result judgment and processing in the soft keyboard event scheduling method, including the following steps:

[0093] Step 601: Identify the soft keyboard event response result feedback information set in the preset UI text display control and / or UI text receiving control, wherein the set soft keyboard event response result feedback information is preset feedback information;

[0094] Specifically, the UI text receiving control includes the UITextField control in iOS development; the UI text display control includes the UITextView control in iOS development.

[0095] Step 602: After the target soft keyboard event response ends, receive the actual feedback information;

[0096] Step 603: Compare the actual feedback information with the preset feedback information, and based on the comparison result, identify whether the target soft keyboard event was successfully responded to;

[0097] Step 604: If the target soft keyboard event is successfully responded to, proceed to the next program operation according to the next execution instruction;

[0098] Specifically, the next execution instruction is the next processing instruction generated within the current interface.

[0099] Step 605: If the target soft keyboard event response fails, then the target soft keyboard event response is retried.

[0100] Specifically, if the target soft keyboard event response fails, a certain number of response retries are set first, and the target soft keyboard event response is retried; if the response still fails after a certain number of retries, a preset alarm event can be initiated to issue a service alarm.

[0101] In this embodiment, a soft keyboard event manager is initialized; soft keyboard events are monitored through preset event listeners; and corresponding soft keyboard events are executed using an event proxy function pattern based on the monitoring results. This achieves rational scheduling of soft keyboard events under the event manager, listener, and proxy processing modes, facilitating unified maintenance and management by operations and maintenance personnel. Applying this soft keyboard event scheduling method to the soft keyboard event scheduling and management of online business processing platforms in the financial or medical fields enables rational scheduling of soft keyboard events, further facilitating unified maintenance and management by operations and maintenance personnel.

[0102] The embodiments of this application can acquire and process relevant data based on artificial intelligence technology. Artificial intelligence (AI) is the theory, method, technology, and application system that uses digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to obtain optimal results.

[0103] Foundational technologies in artificial intelligence generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing, operating / interactive systems, and mechatronics. AI software technologies mainly encompass computer vision, robotics, biometrics, speech processing, natural language processing, and machine learning / deep learning.

[0104] In this embodiment, a soft keyboard event manager is initialized; soft keyboard events are monitored through preset event listeners; and corresponding soft keyboard events are executed using an event proxy function pattern based on the monitoring results. This achieves rational scheduling of soft keyboard events under the event manager, listener, and proxy processing modes, facilitating unified maintenance and management by operations and maintenance personnel. Applying this soft keyboard event scheduling method to the soft keyboard event scheduling and management of online business processing platforms in the financial or medical fields enables rational scheduling of soft keyboard events, further facilitating unified maintenance and management by operations and maintenance personnel.

[0105] Further reference Figure 7 As a response to the above Figure 2 The implementation of the method shown in this application provides an embodiment of a soft keyboard event scheduling device, which is similar to... Figure 2 Corresponding to the method embodiments shown, this device can be specifically applied to various electronic devices.

[0106] like Figure 7 As shown, the soft keyboard event scheduling device 700 described in this embodiment includes: an initialization module 701, an event listening module 702, a first judgment module 703, a first branch processing module 704, a second branch processing module 705, and a first parameter passing scheduling module 706. Wherein:

[0107] An initialization module 701 is used to initialize the soft keyboard event manager, wherein the soft keyboard event manager includes a first manager, which integrates the overall events of the soft keyboard in the parent container component, including the overall display event or the overall insertion event of the soft keyboard in the parent container component;

[0108] The event listener module 702 is used to listen for soft keyboard events through a preset event listener;

[0109] The first judgment module 703 is used to determine whether the soft keyboard service program is currently in a closed state when it hears the overall display event or overall insertion event of the soft keyboard in the parent container component.

[0110] The first branch processing module 704 is used to initiate a preset alarm event to provide a service alarm if the soft keyboard service program is not currently in a closed state.

[0111] The second branch processing module 705 is used to trigger a start-up overall display event or an overall insertion event from the first manager if the soft keyboard service program is currently in a program closed state, and to call back a preset soft keyboard event proxy function in the corresponding overall event;

[0112] The first parameter passing scheduling module 706 is used to pass the parameter information that needs to be carried when the soft keyboard is displayed or inserted as a whole to the soft keyboard event delegate function, so as to display or insert the soft keyboard in the parent container component. The parameter information that needs to be carried when the soft keyboard is displayed or inserted as a whole includes: the height information, width information, style information, and position information of the soft keyboard.

[0113] This application initializes a soft keyboard event manager; listens for soft keyboard events through preset event listeners; and executes the corresponding soft keyboard events using an event proxy function pattern based on the listening results. This achieves rational scheduling of soft keyboard events under the event manager, listener, and proxy processing modes, facilitating unified maintenance and management by operations and maintenance personnel. Applying this soft keyboard event scheduling method to the soft keyboard event scheduling and management of online business processing platforms in the financial or medical fields enables rational scheduling of soft keyboard events, further facilitating unified maintenance and management by operations and maintenance personnel.

[0114] In this embodiment, the soft keyboard event scheduling device 700 further includes a second judgment module, a third branch processing module, a fourth branch processing module, and a second parameter transmission scheduling module. Wherein:

[0115] The second judgment module is used to determine whether the soft keyboard service program is currently in a closed state when the overall hidden event or overall closed event of the soft keyboard in the parent container component is detected.

[0116] The third branch processing module is used to initiate a preset alarm event to provide a service alarm if the soft keyboard service program is currently in a closed state.

[0117] The fourth branch processing module is used to trigger a start-up overall hiding event or an overall shutdown event from the first manager if the soft keyboard service program is not currently in a program closed state, and to call back the preset soft keyboard event proxy function in the corresponding overall event;

[0118] The second parameter passing scheduling module is used to pass the parameter information that needs to be carried when the soft keyboard is completely hidden or completely closed to the soft keyboard event delegate function, so as to hide or close the soft keyboard in the parent container component. The parameter information that needs to be carried when the soft keyboard is completely hidden or completely closed includes at least: the stop status parameter of the soft keyboard service program and the control parameters when the soft keyboard is not displayed on the page.

[0119] In this embodiment, the soft keyboard event scheduling device 700 further includes a third judgment module, a fifth branch processing module, and a sixth branch processing module. Wherein:

[0120] The third judgment module is used to determine whether the soft keyboard service program is currently in a closed state when it listens to the overall close event or overall hide event corresponding to the parent container component where the soft keyboard is located.

[0121] The fifth branch processing module is used to execute the overall shutdown event or overall hide event corresponding to the parent container component if the soft keyboard service program is currently in a closed state.

[0122] The sixth branch processing module is used to, if the soft keyboard service program is not currently in a program closed state, call the overall hide event or overall close event corresponding to the soft keyboard from the first manager, and add the overall hide event or overall close event corresponding to the soft keyboard as a child event to the overall close event or overall hide event corresponding to the parent container component.

[0123] In this embodiment, the soft keyboard event scheduling device 700 further includes a fourth judgment module, a seventh branch processing module, an eighth branch processing module, and a third parameter transmission scheduling module. Wherein:

[0124] The fourth judgment module is used to determine whether the soft keyboard service program is currently in the program startup state when a local event of the soft keyboard is detected.

[0125] The seventh branch processing module is used to initiate a preset alarm event to provide a service alarm if the soft keyboard service program is not currently in the program startup state.

[0126] The eighth branch processing module is used to trigger the start of a corresponding local event from the second manager if the soft keyboard service program is currently in the program startup state, and to call back a preset soft keyboard local event proxy function in the local event.

[0127] The third parameter passing scheduling module is used to pass the parameter information that the local event implementation needs to carry to the soft keyboard local event proxy function to complete the local operation on the soft keyboard. The parameter information that the local event needs to carry includes: page response, page feedback and / or page change information after the local event operation is executed.

[0128] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing related hardware through computer-readable instructions. These computer-readable instructions can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the methods described above. The aforementioned storage medium can be a non-volatile storage medium such as a magnetic disk, optical disk, or read-only memory (ROM), or random access memory (RAM).

[0129] It should be understood that although the steps in the flowcharts of the accompanying drawings are shown in sequence as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the flowcharts of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0130] To address the aforementioned technical problems, embodiments of this application also provide a computer device. Please refer to [link / reference needed]. Figure 8 , Figure 8 This is a basic structural block diagram of the computer device in this embodiment.

[0131] The computer device 8 includes a memory 8a, a processor 8b, and a network interface 8c that are interconnected via a system bus. It should be noted that... Figure 8 Only a computer device 8 with component memory 8a, processor 8b, and network interface 8c is shown. However, it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Those skilled in the art will understand that the computer device described herein is a device capable of automatically performing numerical calculations and / or information processing according to pre-set or stored instructions. Its hardware includes, but is not limited to, microprocessors, application-specific integrated circuits (ASICs), programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0132] The computer device can be a desktop computer, laptop, handheld computer, or cloud server, etc. The computer device can interact with the user via a keyboard, mouse, remote control, touchpad, or voice control.

[0133] The memory 8a includes at least one type of readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 8a may be an internal storage unit of the computer device 8, such as the hard disk or memory of the computer device 8. In other embodiments, the memory 8a may also be an external storage device of the computer device 8, such as a plug-in hard disk, smart memory card (SMC), secure digital (SD) card, flash memory card, etc. Of course, the memory 8a may include both internal storage units and external storage devices of the computer device 8. In this embodiment, the memory 8a is typically used to store the operating system and various application software installed on the computer device 8, such as computer-readable instructions for a soft keyboard event scheduling method. In addition, the memory 8a can also be used to temporarily store various types of data that have been output or will be output.

[0134] In some embodiments, the processor 8b may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip. The processor 8b is typically used to control the overall operation of the computer device 8. In this embodiment, the processor 8b is used to execute computer-readable instructions stored in the memory 8a or to process data, for example, to execute computer-readable instructions of the soft keyboard event scheduling method described above.

[0135] The network interface 8c may include a wireless network interface or a wired network interface, which is typically used to establish communication connections between the computer device 8 and other electronic devices.

[0136] The computer equipment proposed in this embodiment belongs to the field of operation and maintenance management technology and is applied in scenarios of optimizing and improving online service products in finance or healthcare. This application initializes a soft keyboard event manager; listens for soft keyboard events through a preset event listener; and executes the corresponding soft keyboard events using an event proxy function pattern based on the listening results. This achieves rational scheduling of soft keyboard events under the event manager, listener, and proxy processing modes, facilitating unified maintenance and management by operation and maintenance personnel. Applying this soft keyboard event scheduling method to the soft keyboard event scheduling and management in online business processing platforms for finance or healthcare enables rational scheduling of soft keyboard events, facilitating unified maintenance and management by operation and maintenance personnel.

[0137] This application also provides another embodiment, namely, providing a computer-readable storage medium storing computer-readable instructions that can be executed by a processor to cause the processor to perform the steps of the soft keyboard event scheduling method described above.

[0138] The computer-readable storage medium proposed in this embodiment belongs to the field of operation and maintenance management technology and is applied to the optimization and improvement of online service products in finance or healthcare. This application initializes a soft keyboard event manager; listens for soft keyboard events through a preset event listener; and executes the corresponding soft keyboard events using an event proxy function pattern based on the listening results. This achieves rational scheduling of soft keyboard events under the event manager, listener, and proxy processing modes, facilitating unified maintenance and management by operation and maintenance personnel. Applying this soft keyboard event scheduling method to the soft keyboard event scheduling and management in online business processing platforms for finance or healthcare enables rational scheduling of soft keyboard events, facilitating unified maintenance and management by operation and maintenance personnel.

[0139] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0140] Obviously, the embodiments described above are only some embodiments of this application, not all embodiments. The accompanying drawings show preferred embodiments of this application, but do not limit the patent scope of this application. This application can be implemented in many different forms; rather, the purpose of providing these embodiments is to make the disclosure of this application more thorough and comprehensive. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing specific embodiments, or make equivalent substitutions for some of the technical features. Any equivalent structures made using the content of this application's specification and drawings, directly or indirectly applied to other related technical fields, are similarly within the scope of patent protection of this application. Software tools or components not belonging to this company that appear in the embodiments of this application are merely illustrative examples and do not represent actual use.

Claims

1. A soft keyboard event scheduling method, characterized in that, Includes the following steps: Initialize the soft keyboard event manager, wherein the soft keyboard event manager includes a first manager, which integrates the overall events of the soft keyboard in the parent container component, including the overall display event or the overall insertion event of the soft keyboard in the parent container component; Listen for soft keyboard events using a pre-defined event listener; When the soft keyboard is detected to be displayed or inserted in the parent container component, determine whether the soft keyboard service application is currently in a closed state. If the soft keyboard service program is not currently in a closed state, a preset alarm event will be initiated to trigger a service alarm. If the soft keyboard service program is currently in a closed state, a start-up overall display event or an overall insertion event is triggered from the first manager, and a preset soft keyboard event delegate function is called back in the corresponding overall event; The parameter information required when the soft keyboard is fully displayed or inserted is passed to the soft keyboard event delegate function to display or insert the soft keyboard in the parent container component. The parameter information required when the soft keyboard is fully displayed or inserted includes: the height information, width information, style information, and position information of the soft keyboard.

2. The soft keyboard event scheduling method according to claim 1, characterized in that, The overall events also include the overall hiding event or overall closing event of the soft keyboard in the parent container component. After performing the step of listening for soft keyboard events through a preset event listener, the method further includes: When the soft keyboard is detected to be completely hidden or closed in the parent container component, determine whether the soft keyboard service application is currently in a closed state. If the soft keyboard service program is currently in a closed state, a preset alarm event will be initiated to trigger a service alarm. If the soft keyboard service program is not currently in a closed state, a start-up overall hiding event or an overall shutdown event is triggered from the first manager, and a preset soft keyboard event delegate function is called back in the corresponding overall event; The parameters required when the soft keyboard is completely hidden or closed are passed to the soft keyboard event delegate function to hide or close the soft keyboard in the parent container component. The parameters required when the soft keyboard is completely hidden or closed include at least: the stop status parameter of the soft keyboard service program and the control parameters when the soft keyboard is not displayed on the page.

3. The soft keyboard event scheduling method according to claim 1, characterized in that, After performing the step of listening for soft keyboard events through a preset event listener, the method further includes: When the overall close event or overall hide event of the parent container component where the soft keyboard is located is detected, determine whether the soft keyboard service program is currently in a closed state. If the soft keyboard service program is currently in a closed state, then execute the overall close event or overall hide event corresponding to the parent container component; If the soft keyboard service program is not currently in a closed state, the overall hide event or overall close event corresponding to the soft keyboard is called from the first manager, and the overall hide event or overall close event corresponding to the soft keyboard is added as a child event to the overall close event or overall hide event corresponding to the parent container component.

4. The soft keyboard event scheduling method according to claim 1, characterized in that, The soft keyboard event manager also includes a second manager, which integrates localized events of the soft keyboard. After performing the step of listening to soft keyboard events through a preset event listener, the method further includes: When a local event of the soft keyboard is detected, determine whether the soft keyboard service program is currently in the program startup state. If the soft keyboard service program is not currently in the program startup state, a preset alarm event will be initiated to issue a service alarm. If the soft keyboard service program is currently in the program startup state, the corresponding local event is triggered from the second manager, and the preset soft keyboard local event delegate function is called back in the local event; The parameter information required for the implementation of the local event is passed to the soft keyboard local event delegate function to complete the local operation on the soft keyboard. The parameter information required for the local event includes: page response, page feedback and / or page change information after the local event operation is executed.

5. The soft keyboard event scheduling method according to any one of claims 1 to 4, characterized in that, The step of listening to soft keyboard events through a preset event listener specifically includes: The KVC listening mechanism is used to listen for soft keyboard events. Specifically, the KVC listening mechanism uses the NSKeyValueObserving protocol to listen for changes in the soft keyboard object's properties, thereby enabling the listening for soft keyboard events.

6. The soft keyboard event scheduling method according to claim 1, characterized in that, The step of passing the parameter information required for displaying or inserting the soft keyboard as a whole into the soft keyboard event delegate function to display or insert the soft keyboard into the parent container component further includes: When displaying or inserting a soft keyboard in the parent container component, the display or insertion mode of the soft keyboard in the parent container component is set to block-level mode. Specifically, the display property field of the soft keyboard is updated to the block field in the update setting method. After passing the parameter information required for displaying or inserting the soft keyboard as a whole into the soft keyboard event delegate function to display or insert the soft keyboard into the parent container component, the method further includes: According to preset state control parameters, the position display state of the soft keyboard in the parent container component is identified, wherein the position display state includes a fixed position display state and a floating position display state; If the soft keyboard is in a fixed position display state in the parent container component, the corresponding delegate function for the fixed position display setting of the soft keyboard is called back, and the corresponding fixed position parameters are passed into the delegate function. If the soft keyboard is in a floating position display state within the parent container component, the corresponding delegate function for setting the soft keyboard's floating position display is called back, and the corresponding floating position parameters are passed to the delegate function.

7. The soft keyboard event scheduling method according to claim 1, characterized in that, The method further includes: Identify the soft keyboard event response result feedback information set in the preset UI text display control and / or UI text receiving control, wherein the set soft keyboard event response result feedback information is preset feedback information; After the target soft keyboard event response ends, receive the actual feedback information; Compare the actual feedback information with the preset feedback information, and based on the comparison result, identify whether the target soft keyboard event was successfully responded to; If the target soft keyboard event is successfully responded to, the next program operation will be performed according to the next execution instruction; If the target soft keyboard event response fails, the target soft keyboard event response will be retried.

8. A soft keyboard event scheduling device, characterized in that, include: An initialization module is used to initialize the soft keyboard event manager, wherein the soft keyboard event manager includes a first manager, which integrates the overall events of the soft keyboard in the parent container component. The overall events include the overall display event or the overall insertion event of the soft keyboard in the parent container component. The event listener module is used to listen for soft keyboard events through preset event listeners; The first judgment module is used to determine whether the soft keyboard service program is currently in a closed state when it hears the overall display event or overall insertion event of the soft keyboard in the parent container component. The first branch processing module is used to initiate a preset alarm event to provide a service alarm if the soft keyboard service program is not currently in a closed state. The second branch processing module is used to trigger a start-up overall display event or an overall insertion event from the first manager if the soft keyboard service program is currently in a closed state, and to call back a preset soft keyboard event proxy function in the corresponding overall event; The first parameter passing scheduling module is used to pass the parameter information that needs to be carried when the soft keyboard is displayed or inserted as a whole to the soft keyboard event delegate function, so as to display or insert the soft keyboard in the parent container component. The parameter information that needs to be carried when the soft keyboard is displayed or inserted as a whole includes: the height information, width information, style information, and position information of the soft keyboard.

9. A computer device, characterized in that, The device includes a memory and a processor, wherein the memory stores computer-readable instructions, and the processor executes the computer-readable instructions to implement the steps of the soft keyboard event scheduling method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the soft keyboard event scheduling method as described in any one of claims 1 to 7.

Images