CN111752818B - Debugging method, debugging device and medium for application program - Google Patents
Debugging method, debugging device and medium for application program Download PDFInfo
- Publication number
- CN111752818B CN111752818B CN201910241915.4A CN201910241915A CN111752818B CN 111752818 B CN111752818 B CN 111752818B CN 201910241915 A CN201910241915 A CN 201910241915A CN 111752818 B CN111752818 B CN 111752818B
- Authority
- CN
- China
- Prior art keywords
- click
- debugging
- information
- user interface
- combination operation
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/362—Debugging of software
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The present disclosure provides a debugging method for an application. The debugging method comprises the following steps: receiving a first click combination operation of a user on a user interface of the application program, wherein the first click combination operation comprises one click or a plurality of continuous clicks, adjacent time intervals of the plurality of continuous clicks are smaller than a timeout threshold, and the clicking positions and/or clicking modes of each click in the first click combination operation are the same or different; and responding to the first click combination operation, and displaying first debugging information of the application program on the user interface, wherein the first debugging information corresponds to the first click combination operation, and the first debugging information is one of at least one debugging information of the application program. The disclosure also provides a debugging device and a medium for the application program.
Description
Technical Field
The present disclosure relates to the field of computer technology, and more particularly, to a debugging method, a debugging device, and a medium for an application program.
Background
In the prior art, when debugging an application program in some electronic devices (e.g., electronic billboards), it is generally required to connect the electronic device to a computer through a USB debugging interface (e.g., type-C interface), and then display the debugging information of the application program on a computer screen.
In implementing the concepts of the present disclosure, the inventors found that at least the following problems exist in the prior art: if the electronic device has no USB debug interface or is inconvenient to connect to a computer, the debug information of the application program therein cannot be obtained, and in this case, it is difficult to effectively debug the application program therein.
Disclosure of Invention
In view of this, the present disclosure provides a debugging method, a debugging device, and a medium that enable the debugging information of an application to be printed on the screen of an electronic device on which the application is running.
In a first aspect of the present disclosure, a debugging method for an application is provided. The debugging method comprises the following steps: receiving a first click combination operation of a user on a user interface of the application program, wherein the first click combination operation comprises one click or a plurality of continuous clicks, adjacent time intervals of the plurality of continuous clicks are smaller than a timeout threshold, and the clicking positions and/or clicking modes of each click in the first click combination operation are the same or different; and responding to the first click combination operation, and displaying first debugging information of the application program on the user interface, wherein the first debugging information corresponds to the first click combination operation, and the first debugging information is one of at least one debugging information of the application program.
According to an embodiment of the disclosure, in response to the first click combination operation, first debug information of the application program is displayed on the user interface, including obtaining attribute information of each click in the first click combination operation, where the attribute information includes information characterizing a click position and/or a click manner, and determining, based on a preset code mapping relationship, a code having a mapping relationship with the attribute information, so as to obtain a code corresponding to each click. Combining codes corresponding to each click in the first click combination operation to obtain a first code combination corresponding to the first click combination operation, and determining the first debugging information corresponding to the first code combination based on a mapping relation between a preset code combination and the debugging information; and displaying the first debugging information on the user interface.
According to an embodiment of the disclosure, obtaining attribute information of each click in the first click combination operation includes determining, for each click, information characterizing a click position of the each click according to an area to which the click position belongs in the user interface, wherein the user interface is divided into one or more areas, and/or determining information characterizing the click manner based on preset conditions satisfied by a duration of the each click.
According to an embodiment of the disclosure, the determining the information characterizing the click position according to the area of the click position of each click in the user interface includes dividing the user interface into four quadrants according to a cartesian coordinate system with a center of the user interface as an origin, and dividing the information of the quadrant in which the click position of each click is located as the information characterizing the click position. And determining information representing the clicking mode based on preset conditions met by the duration time of each click, wherein the information representing the clicking mode is determined to be a long press when the duration time of each click is greater than or equal to a preset duration time, or is determined to be a short press when the duration time of each click is less than the preset duration time.
According to an embodiment of the disclosure, the debugging method further includes configuring the coding mapping relation, and configuring a mapping relation between the coding combination and debugging information.
According to an embodiment of the present disclosure, the at least one debug information includes a debug log of the application, one or more parametric debug controls, and/or user-defined debug information.
According to an embodiment of the disclosure, the receiving the first click combination operation of the user on the user interface of the application program includes detecting a click operation of the user on the user interface, and dividing two clicks before and after an adjacent time interval is smaller than the timeout threshold into one click combination operation when the click operation is detected.
In a second aspect of the present disclosure, a debugging apparatus for an application is provided. The debugging device comprises a receiving module and a display module. The receiving module is used for receiving a first click combination operation of a user on a user interface of the application program, wherein the first click combination operation comprises one click or a plurality of continuous clicks, adjacent time intervals of the plurality of continuous clicks are smaller than a timeout threshold, and the clicking positions and/or clicking modes of each click in the first click combination operation are the same or different. The display module is used for responding to the first click combination operation and displaying first debugging information of the application program on the user interface, wherein the first debugging information corresponds to the first click combination operation, and the first debugging information is one of at least one piece of debugging information of the application program.
According to an embodiment of the disclosure, the display module is specifically configured to obtain attribute information of each click in the first click combination operation, where the attribute information includes information representing a click position and/or a click manner, determine, based on a preset code mapping relationship, a code having a mapping relationship with the attribute information, so as to obtain a code corresponding to each click, combine the codes corresponding to each click in the first click combination operation, obtain a first code combination corresponding to the first click combination operation, determine, based on a mapping relationship between a preset code combination and debug information, the first debug information corresponding to the first code combination, and display the first debug information on the user interface.
According to an embodiment of the disclosure, the obtaining attribute information of each click in the first click combination operation includes determining, for each click, information characterizing a click position of the each click according to an area to which the click position belongs in the user interface, where the user interface is divided into one or more areas, and/or determining information characterizing the click manner based on preset conditions satisfied by a duration of the each click.
According to an embodiment of the disclosure, the determining the information characterizing the click position according to the area of the click position of each click in the user interface includes dividing the user interface into four quadrants according to a cartesian coordinate system with a center of the user interface as an origin, and dividing the information of the quadrant in which the click position of each click is located as the information characterizing the click position. And determining information representing the clicking mode based on preset conditions met by the duration time of each click, wherein the information representing the clicking mode is determined to be a long press when the duration time of each click is greater than or equal to a preset duration time, or is determined to be a short press when the duration time of each click is less than the preset duration time.
According to an embodiment of the disclosure, the debugging device further includes a mapping relationship configuration module. The mapping relation configuration module is used for configuring the coding mapping relation and configuring the mapping relation between the coding combination and the debugging information.
According to an embodiment of the present disclosure, the at least one debug information includes a debug log of the application, one or more parametric debug controls, and/or user-defined debug information.
According to an embodiment of the disclosure, the receiving module is specifically configured to detect a click operation of a user on the user interface, and divide two clicks before and after an adjacent time interval is less than the timeout threshold into one click combination operation when the click operation is detected.
In a third aspect of the present disclosure, a debugging apparatus for an application is provided. The application program is an application program of an android system. The debugging device comprises a screen debugging component. The screen debugging component is a subclass of android View, and an interface for printing the at least one debugging information is integrated in the screen debugging component. Wherein the screen debugging component is configured to perform a debugging method as described above, wherein the first debugging information is printed on the user interface through the interface to enable presentation of the first debugging information in the user interface.
In a fourth aspect of the present disclosure, a debugging apparatus for an application is provided. The debugging device comprises one or more processors and a storage device for storing one or more programs. Wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the debugging method as described above.
In a fifth aspect of the present disclosure, a computer readable medium is provided having stored thereon executable instructions that, when executed by a processor, cause the processor to perform a debugging method as described above.
In a sixth aspect of the present disclosure, there is provided a computer program comprising computer executable instructions which when executed are adapted to carry out the method as described above.
According to the embodiment of the disclosure, the problem that debugging information of an application program in the electronic equipment cannot be obtained when the electronic equipment cannot be connected to a computer can be at least partially solved, and therefore the technical effect of more conveniently debugging the application program in the electronic equipment can be achieved.
According to some embodiments of the present disclosure, debug information of an application program in an electronic device is displayed in a user interface of the application program, so that the debug information can be printed on a screen of the electronic device, thereby facilitating a debugger to view the debug information in real time, helping the debugger to more accurately locate a problem of the application program and more specifically determine a debug policy, and improving debug efficiency of the debugger.
According to some embodiments of the present disclosure, the trigger condition for presenting the debug information in the user interface of the application is that the user performs a corresponding click-to-combine operation on the user interface of the application. Specifically, the click combination operation obtains a corresponding code combination through built-in logic, and then the code combination is mapped to corresponding debugging information, and then the display of the debugging information is triggered. According to the embodiment of the disclosure, on the one hand, the complexity of the code can ensure that a malicious destructor who does not know the code can hardly trigger the presentation of the corresponding debug information in a violent exhaustion manner. On the other hand, for the field debugging personnel, the debugging information can be printed on the screen of the electronic equipment by operating on the user interface according to the requirement of clicking combination operation, so that the field debugging can be greatly facilitated.
According to other embodiments of the present disclosure, the debug information presented in the user interface of the application may include a series of custom actions that may trigger some pre-set debug logic, which may facilitate some convenient debug operations by field debuggers (whether technicians or non-technicians).
Drawings
The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments thereof with reference to the accompanying drawings in which:
Fig. 1 schematically illustrates an application scenario of a debugging method, a debugging device and a medium for an application according to an embodiment of the present disclosure;
FIG. 2 schematically illustrates a flow chart of a debugging method for an application in accordance with an embodiment of the present disclosure;
FIG. 3 schematically illustrates a flow diagram of presenting first debug information on a user interface in accordance with an embodiment of the present disclosure;
FIG. 4 schematically illustrates a flowchart showing first debug information on a user interface in accordance with another embodiment of the present disclosure;
FIG. 5A schematically illustrates a flowchart for obtaining per-click attribute information, according to an embodiment of the present disclosure;
FIG. 5B schematically illustrates various regions of a user interface according to an embodiment of the present disclosure;
FIG. 6 schematically illustrates a flow diagram of a receive first click combining operation in accordance with an embodiment of the present disclosure;
FIG. 7 schematically illustrates a block diagram of a debugging apparatus for an application in accordance with an embodiment of the present disclosure;
FIG. 8 schematically illustrates a block diagram of a debugging apparatus for an application in accordance with another embodiment of the present disclosure; and
Fig. 9 schematically illustrates a block diagram of a computer system suitable for implementing a debugging method for an application in accordance with an embodiment of the present disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is only exemplary and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.
Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a convention should be interpreted in accordance with the meaning of one of skill in the art having generally understood the convention (e.g., "a system having at least one of A, B and C" would include, but not be limited to, systems having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a formulation similar to at least one of "A, B or C, etc." is used, in general such a formulation should be interpreted in accordance with the ordinary understanding of one skilled in the art (e.g. "a system with at least one of A, B or C" would include but not be limited to systems with a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
The embodiment of the disclosure provides a debugging method, a debugging device and a medium for an application program. The debugging method comprises the following steps: receiving a first click combination operation of a user on a user interface of an application program, wherein the first click combination operation comprises one click or a plurality of continuous clicks, adjacent time intervals of the plurality of continuous clicks are smaller than a timeout threshold, and the clicking positions and/or clicking modes of each click in the first click combination operation are the same or different; and responding to the first click combination operation, and displaying first debugging information of the application program on a user interface, wherein the first debugging information corresponds to the first click combination operation, and the first debugging information is one of at least one debugging information of the application program.
According to the debugging method, the debugging device and the medium, the first debugging information of the application program is displayed in the user interface of the application program through the triggering of the user operation, so that the first debugging information can be printed in the screen of the electronic equipment running the application program, the running information of the application program can be conveniently checked by a debugger in real time, and the debugging efficiency of the debugger is improved.
Fig. 1 schematically illustrates an application scenario 100 of a debugging method, a debugging device and a medium for an application according to an embodiment of the present disclosure. It should be noted that fig. 1 illustrates only an example of an application scenario in which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments, or scenarios.
As shown in fig. 1, an application scenario 100 according to this embodiment may include an electronic device 1. The electronic device 1 is specifically illustrated in fig. 1 as an electronic billboard 1. It should be understood that the illustration of the electronic device 1 as an electronic billboard 1 in fig. 1 is merely illustrative and not limiting. The embodiment of the present disclosure is not limited in kind and use of the electronic apparatus 1. For convenience of explanation, the embodiment according to the present disclosure will be exemplarily explained below in this specification taking the electronic billboard 1 as an example.
The electronic billboard 1 may be a floor-standing billboard as shown in fig. 1. Of course, the electronic billboard 1 may be a wall-mounted billboard (e.g., mounted on a wall of a building or a wall of a car of an elevator), or the like. The electronic billboard 1 comprises a screen 101. The screen 1 may be of various types, for example, projected, touch-controlled, or operated by a mouse. The screen 101 may be various in size, for example, a small-sized screen formed by a single display screen, or a large-sized screen formed by a plurality of display screens connected to each other. The electronic billboard 1 may be connected to a network or may be disconnected.
The electronic billboard 1 may have an application running therein. The application may be any type of application, such as an image presentation type application, a video playback type application, a shopping type application, or a news information type application.
In the prior art, when an application program in the electronic billboard 1 needs to be debugged, the electronic billboard 1 is usually connected to a computer, and then debug information of the application program is printed out through a computer screen. However, if the electronic billboard 1 does not have an exposed USB debug interface, the shell of the electronic billboard 1 needs to be removed to find the USB debug interface, and even the interior of the electronic billboard 1 may not have a reserved USB debug interface. This can lead to the difficulty of exporting the debug information of the application. Moreover, the electronic billboard 1 is often cumbersome and inconvenient to carry or mail. Thus, when the electronic billboard 1 is experiencing software problems, there is typically no room for other operations than restarting the device or restarting the application if no specialized technician is present.
Embodiments of the present disclosure provide a viable solution to the problem of difficult software debugging in the electronic billboard 1 of the prior art, enabling debug information 10 of an application in the electronic billboard 1 to be printed on the screen 101 of the electronic billboard 1, as shown in fig. 1. Specifically, according to the embodiment of the present disclosure, by receiving a corresponding click-and-combine operation performed by the user 2 on the user interface 11 of the application program in the electronic billboard 1, the debug information 10 of the application program can be presented on the user interface 11, thereby realizing printing of the debug information 10 on the screen 101 of the electronic billboard 1.
According to some embodiments of the present disclosure, debug information 10 may also be a debug log 12, or may also be some pre-set debug logic (e.g. debug controls 13 for one or more parameters, such as seekbar), or may also be a series of custom actions.
Specifically, through the debug log 12, the user 2 finds detailed information for debugging the application program, so that the user 2 can be assisted in locating the problem of the application program more accurately. For example, when the service logic of the application program has a face recognition function, if the face recognition fails, it can be accurately determined according to the debug log 12 whether the face recognition failure is caused by the internal logic of the application program or by the installation of the camera.
Through the debug control 13, the user 2 may perform some convenient debug operations, such as opening some switches of the application, adjusting the camera orientation, triggering the presentation of configuration information of the electronic billboard 1, or triggering the presentation of a debug interface of the application (specifically determined by parameters controlled by the debug control 13). In this way, the user 2 can conveniently perform some convenient debugging operations, and the debugging efficiency of the application program is improved.
It should be noted that the debugging method provided by the embodiments of the present disclosure may be generally performed by the electronic device 1 (e.g., the electronic billboard 1). Accordingly, the debugging device and the medium provided by the embodiments of the present disclosure may be generally disposed in the electronic billboard 1. The debugging method provided by the embodiment of the present disclosure may also be performed by a server or a server cluster that is different from the electronic billboard 1 and is capable of communicating with the electronic billboard 1. Accordingly, the debugging device and the medium provided by the embodiments of the present disclosure may also be disposed in a server or a server cluster different from the electronic billboard 1 and capable of communicating with the electronic billboard 1.
Fig. 2 schematically illustrates a flowchart of a debugging method for an application according to an embodiment of the present disclosure.
As shown in fig. 2, the method includes operation S210 and operation S220.
In operation S210, a first click combination operation of the user 2 on the user interface 11 of the application program is received, wherein the first click combination operation includes one click or a plurality of continuous clicks, adjacent time intervals of the plurality of continuous clicks are smaller than a timeout threshold, and a click position and/or a click manner of each click in the first click combination operation are the same or different. In some embodiments, each click may be, for example, a single click operation by a mouse, such as when the application is operated by the mouse. In other embodiments, when the screen 101 is a touch screen, each click may be determined by a single click event resulting from a combination of one ACTION DOWN press event and a corresponding ACTION UP event when the user 2 touches the screen 101 with a finger or an operator. The click position of each click may for example depend on the place where the click event occurred in the user interface 11 of the application. In some embodiments, a click event may have only one click location. In other embodiments, a single click event may have multiple click locations simultaneously, e.g., user 2 clicks with multiple fingers simultaneously. According to embodiments of the present disclosure, the manner of clicking per click may depend, for example, on the duration of one click event, or may depend, for example, on the simultaneous presence of several click positions in one click event.
In operation S220, first debug information of the application program is presented on the user interface 11 in response to the first click combination operation, wherein the first debug information corresponds to the first click combination operation, and the first debug information is one of at least one debug information 10 of the application program.
According to embodiments not disclosed herein, the at least one debug information 10 may be a debug log 12 of an application, one or more parametric debug controls 13, and/or user-defined debug information.
Fig. 3 schematically illustrates a flowchart showing first debug information on user interface 11 in operation S220 according to an embodiment of the present disclosure.
As shown in fig. 3, operation S220 may include operations S301 to S305.
In operation S301, attribute information of each click in the first click combination operation is acquired, the attribute information including information characterizing a click position and/or a click manner. In some embodiments, the information characterizing the click location may be, for example, coordinate information of the location where each click operates in the user interface 11. In other embodiments, the user interface 11 may be divided into a plurality of regions, and the information characterizing the click position may be, for example, information of a region to which a position operated in the user interface 11 per click belongs. This information characterizing the manner of clicking may be, for example, information determined based on how long each click is (e.g., information that may be categorized as long press, short press, or medium-long press, etc.), in some embodiments, or may be information such as the number of click positions present in each click, etc.
In operation S302, a code having a mapping relationship with the attribute information of each click is determined based on a preset code mapping relationship to obtain a code corresponding to each click. According to an embodiment of the disclosure, the preset code mapping relationship may be preconfigured in the application program, or may be obtained from a cloud or other servers through a network.
In operation S303, codes corresponding to each click in the first click combining operation are combined, and a first code combination corresponding to the first click combining operation is obtained.
In operation S304, first debug information corresponding to the first code combination is determined based on a mapping relationship between the preset code combination and the debug information. According to an embodiment of the disclosure, the mapping relationship between the preset code combination and the debug information may be preconfigured in the application program, or may be obtained from a cloud or other servers through a network.
Then in operation S305, first debug information, such as debug log 12, or debug control 13, etc., is presented in user interface 11.
FIG. 4 schematically illustrates a flowchart of operation S220 of presenting first debug information on user interface 11 in accordance with another embodiment of the present disclosure;
As shown in fig. 4, according to another embodiment of the present disclosure, operation S220 may include operation S401 and operation S402 in addition to operation S301 to operation S305. Wherein, in operation S401, the code mapping relationship is configured. In operation S402, a mapping relationship between the code combination and the debug information is configured.
According to an embodiment of the present disclosure, when the user interface 11 is divided into one or more areas, the information characterizing the click position of each click in the first click combination operation is acquired in operation S301, and specifically, the information characterizing the click position may be determined according to the area to which the click position of each click belongs in the user interface 11. Reference may be made specifically to the description of fig. 5A and 5B.
Fig. 5A schematically illustrates a flowchart of acquiring attribute information per click in operation S301 according to an embodiment of the present disclosure. Fig. 5B schematically illustrates various regions of the user interface 11 according to an embodiment of the present disclosure.
As shown in fig. 5A, operation S301 may include, in particular, operation S501 and operation S502 according to an embodiment of the present disclosure.
In operation S501, the user interface 11 is divided into four quadrants according to a cartesian coordinate system with the center of the user interface 11 as an origin. Specifically, as shown in fig. 5B, the user interface 11 is divided into four quadrants according to a cartesian coordinate system, wherein the upper right is a first quadrant 111, the upper left is a second quadrant 112, the lower left is a third quadrant 113, and the lower right is a fourth quadrant 114.
Then, in operation S502, information of a quadrant in which the click position of each click is located is used as information representing the click position of each click.
According to an embodiment of the present disclosure, the obtaining of the information characterizing the clicking manner of each click in the first click combination operation in operation S301 determines the information characterizing the clicking manner based on the preset condition satisfied by the duration of each click. For example, when the duration of each click is greater than or equal to a preset duration, the information characterizing the click mode is determined to be a long press, or when the duration of each click is less than the preset duration, the information characterizing the click mode is determined to be a short press. For example, the preset duration may be set to 200ms (for example only), where each click is determined to be a long press when the duration of the click exceeds 200ms, and a short press otherwise.
In conjunction with fig. 1 and 5B, it is assumed that the user 2 touches the screen 101 with a single finger, and the clicking manner of each click is divided into two types of long presses or short presses, in this scenario, there may be 8 kinds of optional attribute information per click, that is: 1. short pressing the first quadrant 111; 2. short pressing the second quadrant 112; 3. short pressing the third quadrant 113; 4. short pressing the fourth quadrant 114; 5. long press first quadrant 111; 6. long press second quadrant 112; 7. the long press third quadrant 113; 8. long presses the fourth quadrant 114. The above 8 cases may correspond to 8 different attribute information, respectively, and each attribute information may correspond to one code according to a preset code map. Therefore, by executing the click operation combination on the screen 101 by the user 2, a corresponding code combination can be obtained, and further, corresponding debug information can be obtained according to the mapping relation between the preset code combination and the debug information. In addition, when the number of codes included in each code combination is 1, 8 code combinations can be obtained. When the number of codes included in each code combination is 2, 8×8=64 code combinations can be obtained. Similarly, when the number of codes included in each code combination is 6 bits, 8 ∈6=16, 777,216 code combinations can be obtained. It follows that, according to embodiments of the present disclosure, the complexity of the code may ensure that malicious vandals, who are unaware of the code, are almost impossible to trigger the presentation of valid debug information 10 in a brute force exhaustive manner.
Fig. 6 schematically illustrates a flowchart of a receive first click combining operation in operation S210 according to an embodiment of the present disclosure.
As shown in fig. 6, operation S210 may include operation S601 and operation S602.
In operation S601, a click operation of the user 2 on the user interface 11 is detected. Then, in operation S602, when a click operation is detected, two clicks before and after an adjacent time interval is less than a timeout threshold are divided into one click combination operation. For example, a timeout mechanism may be set for multiple successive click operations to ensure that two click operations spaced beyond the timeout threshold are not accidentally divided into a click combination operation.
Fig. 7 schematically illustrates a block diagram of a debugging device 700 for an application according to an embodiment of the present disclosure.
As shown in fig. 7, according to an embodiment of the present disclosure, the application is an application of an android system, and the debugging device 700 includes a screen debugging component 710. The screen debug component 710 is a subclass of android View. The screen debugging component 710 has integrated therein an interface 711 for printing at least one debugging information 10. Wherein the screen debugging component 710 is configured to perform the debugging method with reference to fig. 2-6, wherein the first debugging information is printed on the user interface 11 via the interface 711 to enable presentation of the first debugging information in the user interface 11.
The screen debugging component 710 can inherit from the ViewGroup base class. Wherein the user interface 11 may be part of the screen debugging component 710. When no debug information 10 is presented, the user interface 11 may be presented in a fully transparent form in the screen 101, while when any one or more of the debug information 10 is to be presented, the user interface 11 may be presented in a semi transparent form in the screen 101, wherein the user interface 11 is presented with the debug information 10 (e.g. debug log 12 and debug control 13). Coding combinations for reading various debug information 10 may be defined in screen debug component 710.
An interface 711 (e.g., API: void postMessage (FINAL STRING MSG)) may be integrated in the screen debug component 710. When the screen debugging component 710 runs, the debugging log 12 of the application program can be fetched through the interface 711, the screen debugging component 710 is printed, and when corresponding clicking combination operation input by the user 2 is received, code combination displaying the debugging log 12 is triggered to be generated, and then the debugging log 12 is displayed on the user interface 11, so that the effect that the debugging log 12 of the application program can be printed on the screen 101 of the electronic device 1 under the condition that a USB debugging interface is not provided is achieved.
The screen debugging component 710 may be specifically implemented, for example, by a developer writing the following in an Android layout file, where DbgMsgView is the screen debugging component 710:
For example:
<com.dbgmsgview.DbgMsgView
android：layout_width＝″match_parent″
android：layout_height＝″match_parent″
dbgMsgView：hide_code＝″1212″
dbgMsgView：max_line＝″15″
dbgMsgView：show_code＝″1212-″
dbgMsgView：text_size＝″@dimen/dbg_text_size″>
</com.dbgmsgview.DbgMsgView>
wherein, the explanation of each line in the above code is as follows:
android: layout_width= "match_parent" -the width of screen debug component 710 is the width of screen 101;
android: layout_height= "match_parent" -the height of screen debug component 710 is the height of screen 101;
dbgMsgView: hide_code= "1212" -hide code combination of debug log 12 to "1212", the corresponding click combination operation may be, for example: short press first quadrant 111- > short press second quadrant 112- > short press first quadrant 111- > short press second quadrant 112;
dbgMsgView: max_line= "15" -the maximum line number of display debug information on screen debug component 710 is 15;
dbgMsgView: show_code= "1212-" -screen debug component 710 displays the code combination of debug log 12 as "1212-", the corresponding click combination operation may be, for example: short press first quadrant 111- > short press second quadrant 112- > short press first quadrant 111- > long press second quadrant 112;
dbgMsgView: text_size= "@ dimen/dbg_text_size" — set fonts in screen debug component 710.
In addition, a developer may also define various parameter settings in the screen debugging component 710 as needed to meet different needs, such as:
dbgMsgView: max_line-maximum number of support lines
DbgMsgView: show_code-code combination showing debug log 12
DbgMsgView: code_code-code combination of hidden debug log 12
DbgMsgView: show_ seekbar _code-show/hide Screen debug control 13
Code combination of (c)
DbgMsgView: long_click_threshold-set the click mode to long press
Long threshold value
DbgMsgView: text_size-set font size
DbgMsgView: custom_code-code to set custom action coding
When the screen debugging component 710 is initialized by the Android system, all the code combinations defined in the screen debugging component can be read, and then the parameter () method is called to analyze all the code combinations and then store the code combinations into the data structure in the memory. When a click operation of the user 2 on the user interface 11 is detected, the screen debugging component 710 may determine whether to perform a combination of adjacent click operations in the manner shown in fig. 6. And matches the code combination defined in the screen debugging component 710 according to the click combination operation after determining that a one-click combination operation is obtained. When any code combination matches the click combination operation of user 2, the operation defined by that code combination will be triggered. In addition, the storage of debug information 10 may be defined in screen debug component 710, such as defining List < String > to store debug information 10.
Fig. 8 schematically illustrates a block diagram of a debugging device 800 for an application according to another embodiment of the present disclosure.
As shown in fig. 8, the debugging device 800 includes a receiving module 810 and a presentation module 820.
The receiving module 810 may, for example, perform operation S210, configured to receive a first click combination operation of the user 2 on the user interface 11 of the application program, where the first click combination operation includes one click or multiple continuous clicks, and adjacent time intervals of the multiple continuous clicks are less than a timeout threshold, and a click position and/or a click manner of each click in the first click combination operation are the same or different. According to an embodiment of the present disclosure, the receiving module 810 may specifically perform operations S601 and S602 as described above, for detecting a click operation of the user 2 on the user interface 11, and dividing two clicks before and after an adjacent time interval less than a timeout threshold into one click combination operation when the click operation is detected.
The presentation module 820 may, for example, perform operation S220 for presenting first debug information of the application on the user interface 11 in response to the first click combination operation, wherein the first debug information corresponds to the first click combination operation, and the first debug information is one of at least one debug information 10 of the application. According to an embodiment of the present disclosure, at least one debug information 10 includes a debug log 12 of an application, one or more parametric debug controls 13, and/or user-defined debug information.
According to an embodiment of the disclosure, the presentation module 820 may specifically perform operations S301 to S305 as described above, and is configured to obtain attribute information of each click in the first click combination operation, where the attribute information includes information characterizing a click position and/or a click manner (operation S301), determine, based on a preset code mapping relationship, a code having a mapping relationship with the attribute information to obtain a code corresponding to each click (operation S302), combine the codes corresponding to each click in the first click combination operation to obtain a first code combination corresponding to the first click combination operation (operation S303), determine, based on a mapping relationship between the preset code combination and the debug information, first debug information corresponding to the first code combination (operation S304), and present the first debug information on the user interface 11 (operation S305).
According to an embodiment of the present disclosure, the debugging device 800 further comprises a mapping relation configuration module 830. The mapping relation configuration module 830 may perform, for example, operations S401 and S402 as previously described, for configuring a coding mapping relation, and configuring a mapping relation of a coding combination and debug information.
According to an embodiment of the present disclosure, obtaining attribute information of each click in a first click combination operation includes determining, for each click, information characterizing a click location according to an area to which the click location of each click belongs in the user interface 11, wherein the user interface 11 is divided into one or more areas, and/or determining information characterizing a click manner based on preset conditions satisfied by a duration of each click.
According to an embodiment of the present disclosure, information characterizing a click position is determined according to an area to which the click position of each click belongs in the user interface 11, including dividing the user interface 11 into four quadrants according to a Cartesian coordinate system with a center of the user interface 11 as an origin (operation S501), and information of a quadrant in which the click position of each click is located is used as information characterizing the click position (operation S502). And determining information representing the clicking mode based on preset conditions met by the duration time of each click, wherein the information representing the clicking mode is determined to be a long press when the duration time of each click is greater than or equal to the preset duration time, or is determined to be a short press when the duration time of each click is less than the preset duration time.
Any number of modules, sub-modules, units, sub-units, or at least some of the functionality of any number of the sub-units according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented as split into multiple modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system-on-chip, a system-on-substrate, a system-on-package, an Application Specific Integrated Circuit (ASIC), or in any other reasonable manner of hardware or firmware that integrates or encapsulates the circuit, or in any one of or a suitable combination of three of software, hardware, and firmware. Or one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be at least partially implemented as computer program modules, which, when executed, may perform the corresponding functions.
For example, any of the receiving module 810, the presentation module 820, and the mapping relationship configuration module 830 may be combined in one module to be implemented, or any of the modules may be split into a plurality of modules. Or at least some of the functionality of one or more of the modules may be combined with, and implemented in, at least some of the functionality of other modules. At least one of the receiving module 810, the presentation module 820, and the mapping relationship configuration module 830 may be implemented at least in part as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or in hardware or firmware in any other reasonable manner of integrating or packaging circuitry, or in any one of or a suitable combination of three of software, hardware, and firmware, according to embodiments of the present disclosure. Or at least one of the receiving module 810, the presentation module 820, and the mapping relation configuration module 830 may be at least partially implemented as a computer program module, which when executed, may perform the corresponding functions.
Fig. 9 schematically illustrates a block diagram of a computer system 900 adapted to implement a debugging method for an application in accordance with an embodiment of the present disclosure. The computer system 900 illustrated in fig. 9 is merely an example, and should not be construed as limiting the functionality and scope of use of embodiments of the present disclosure.
As shown in fig. 9, a computer system 900 according to an embodiment of the present disclosure includes a processor 901, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 902 or a program loaded from a storage portion 908 into a Random Access Memory (RAM) 903. The processor 901 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. Processor 901 may also include on-board memory for caching purposes. Processor 901 may include a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the present disclosure.
In the RAM 903, various programs and data necessary for the operation of the computer system 900 are stored. The processor 901, the ROM 902, and the RAM 903 are connected to each other by a bus 904. The processor 901 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 902 and/or the RAM 903. Note that the program may be stored in one or more memories other than the ROM 902 and the RAM 903. The processor 901 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in the one or more memories.
According to an embodiment of the disclosure, computer system 900 may also include an input/output (I/O) interface 905, with input/output (I/O) interface 905 also being connected to bus 904. The system 900 may also include one or more of the following components connected to the I/O interface 905: an input section 906 including a keyboard, a mouse, and the like; an output portion 907 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage portion 908 including a hard disk or the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as needed. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on the drive 910 so that a computer program read out therefrom is installed into the storage section 908 as needed.
According to embodiments of the present disclosure, the method flow according to embodiments of the present disclosure may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from the network via the communication portion 909 and/or installed from the removable medium 911. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 901. According to embodiments of the present disclosure, the above-described computer systems, devices, apparatuses, modules, units, etc. may be implemented by computer program modules.
The present disclosure also provides a computer-readable storage medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present disclosure.
According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example, but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, the computer-readable storage medium may include ROM 902 and/or RAM 903 and/or one or more memories other than ROM 902 and RAM 903 described above.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be combined in various combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.
The embodiments of the present disclosure are described above. These examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the embodiments cannot be used advantageously in combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the disclosure, and such alternatives and modifications are intended to fall within the scope of the disclosure.
Claims (17)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910241915.4A CN111752818B (en) | 2019-03-27 | 2019-03-27 | Debugging method, debugging device and medium for application program |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910241915.4A CN111752818B (en) | 2019-03-27 | 2019-03-27 | Debugging method, debugging device and medium for application program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111752818A CN111752818A (en) | 2020-10-09 |
| CN111752818B true CN111752818B (en) | 2024-08-16 |
Family
ID=72672084
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910241915.4A Active CN111752818B (en) | 2019-03-27 | 2019-03-27 | Debugging method, debugging device and medium for application program |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111752818B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115599249A (en) * | 2021-07-08 | 2023-01-13 | 北京字跳网络技术有限公司（Cn） | A component debugging method, device, equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104346100A (en) * | 2014-10-17 | 2015-02-11 | 广东欧珀移动通信有限公司 | A shortcut operation method and device for an intelligent mobile terminal in a black screen state |
| CN106547682A (en) * | 2015-09-21 | 2017-03-29 | 腾讯科技（深圳）有限公司 | The method and device of commissioning Mobile solution |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH10333935A (en) * | 1997-05-30 | 1998-12-18 | Mitsubishi Electric Corp | Debugging method and recording medium |
| US7814463B2 (en) * | 2003-05-16 | 2010-10-12 | Oracle International Corporation | User interface debugger for software applications |
| CN102866853A (en) * | 2012-08-23 | 2013-01-09 | 广东欧珀移动通信有限公司 | Method and device for controlling an application program of a touch screen terminal |
| CN102968301A (en) * | 2012-11-12 | 2013-03-13 | 福建天晴数码有限公司 | Method for real-time control on running window of game |
| CN104008041B (en) * | 2013-02-21 | 2018-07-06 | 腾讯科技（深圳）有限公司 | Terminal applies test method and device |
| CN106445825B (en) * | 2016-09-30 | 2020-06-12 | 南京秦淮紫云创益企业服务有限公司 | Debugging method and device |
| CN107038112B (en) * | 2016-10-13 | 2020-09-01 | 腾讯科技（北京）有限公司 | Application interface debugging method and device |
| CN107168878B (en) * | 2017-05-22 | 2020-06-09 | 网易有道信息技术（北京）有限公司 | Method, device and medium for testing application program |
| CN109032727B (en) * | 2018-07-03 | 2021-08-03 | Oppo（重庆）智能科技有限公司 | Application startup method, application startup device and terminal device |
-
2019
- 2019-03-27 CN CN201910241915.4A patent/CN111752818B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104346100A (en) * | 2014-10-17 | 2015-02-11 | 广东欧珀移动通信有限公司 | A shortcut operation method and device for an intelligent mobile terminal in a black screen state |
| CN106547682A (en) * | 2015-09-21 | 2017-03-29 | 腾讯科技（深圳）有限公司 | The method and device of commissioning Mobile solution |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111752818A (en) | 2020-10-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112424836B (en) | Technique for displaying shader tables associated with ray-traced images | |
| US11037347B2 (en) | Augmenting a physical device with virtual information | |
| CN109697004B (en) | Method, device, device and storage medium for writing annotations on touch devices | |
| CN109960642A (en) | Automatic test method and device | |
| CN106327546B (en) | Test method and device for face detection algorithm | |
| CN108109580B (en) | Parameter adaptation method, device, equipment and storage medium of LED display screen | |
| US20170242547A1 (en) | Apparatus, method and system for location based touch | |
| CN105630674A (en) | Test method and device capable of aiming at interface | |
| US10255019B2 (en) | Display configurations based on applications | |
| CN106681701A (en) | Task display method and device | |
| CN108845924B (en) | Control response area display control method, electronic device, and storage medium | |
| CN116955181A (en) | Chip testing system, method, computer equipment and storage medium | |
| JP7282133B2 (en) | Browser display verification method, device, computer equipment and storage medium | |
| CN111752818B (en) | Debugging method, debugging device and medium for application program | |
| CN108520063A (en) | Event log processing method, device and terminal equipment | |
| US20090213067A1 (en) | Interacting with a computer via interaction with a projected image | |
| US20170300280A1 (en) | Image processing apparatus and image processing method | |
| CN110175114A (en) | Test terminal, APP and camera compatibility test method and storage medium | |
| WO2019090691A1 (en) | Monkey testing method and terminal | |
| WO2015039585A1 (en) | Method and device for testing software reliability | |
| WO2021139469A1 (en) | Gdb-based opencv program visualization method and apparatus, and device and storage medium | |
| CN111045876A (en) | Splash screen detection method, device, storage medium and electronic device | |
| CN106445430A (en) | Immediate light color rendering system and method for interactive interface, and use thereof | |
| US9753804B1 (en) | Multi-redundant digital signage | |
| WO2012149808A1 (en) | Method and device for checking system state of apparatus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |