Data processing method and device for graphical interface debugging

Abstract

The invention provides a data processing method and device for graphical interface debugging, which are applied to a first terminal device in an interface debugging system, and the interface debugging system further comprises a second terminal device. The method comprises the following steps: executing a device state determination operation for a second terminal device to determine a current adaptation state of a software and hardware environment corresponding to the second terminal device; if the current adaptation state is represented as support, interacting with the second terminal device to obtain a target memory position; according to the target memory position, executing a data calling operation for the second terminal device to obtain graphic data; transferring the target graphic data into a graphic interface, and displaying the graphic interface on a preset display screen device; and in response to an interface debugging operation of the user, debugging the graphical interface. Therefore, the first terminal device in the application can enable the second terminal device to break away from dependence on an operating system and a display screen, so that a user can debug the graphical interface, and the flexibility and the stability of system operation are improved.

Description

Technical Field

[0001] The present application belongs to the technical field of embedded devices, and specifically relates to a data processing method and device for graphical interface debugging. Background Art

[0002] At present, as the application scenarios of embedded devices become more and more extensive, the demand for graphical interfaces is also growing. The traditional development model often follows the development ideas of general-purpose computers, that is, equipped with a display screen and building a graphical interface based on a mature operating system.

[0003] However, some embedded devices do not have the conditions to transplant large operating systems and configure related services and tool software during the actual development process, making it difficult for embedded devices to meet actual development needs, which in turn leads to low efficiency and poor flexibility in user debugging of graphical interfaces. Summary of the invention

[0004] An embodiment of the present application provides a data processing method and apparatus for graphical interface debugging, wherein a first terminal device ensures smooth operation of a graphical interface by performing a device status determination operation on a second terminal device, and completes debugging of the graphical interface by obtaining a target memory location instead of interacting with a user on an embedded device, thereby improving the flexibility of the interface debugging system and the stability of system operation.

[0005] In a first aspect, an embodiment of the present application provides a data processing method for graphical interface debugging, which is applied to a first terminal device in an interface debugging system, wherein the interface debugging system further includes a second terminal device, and the second terminal device is an embedded device; the method includes:

[0006] Performing a device status determination operation on the second terminal device to determine a current adaptation status of the software and hardware environment corresponding to the second terminal device, where the current adaptation status is used to indicate whether the second terminal device supports normal operation of the graphical interface;

[0007] If the current adaptation state is characterized as supported, interacting with the second terminal device to obtain a target memory location, where the target memory location is a starting location of a memory used by the second terminal device to store target graphic data;

[0008] According to the target memory location, performing a data retrieval operation on the second terminal device to obtain the graphic data;

[0009] Transferring the target graphic data into a graphic interface and displaying the graphic interface on a preset display device;

[0010] In response to the user's interface debugging operation, the graphical interface is debugged.

[0011] In a second aspect, an embodiment of the present application provides a data processing device for graphical interface debugging, which is applied to a first terminal device in an interface debugging system, wherein the interface debugging system further includes a second terminal device, and the second terminal device is an embedded device; the device includes:

[0012] A state determination unit, configured to perform a device state determination operation on the second terminal device to determine a current adaptation state of a software and hardware environment corresponding to the second terminal device, wherein the current adaptation state is used to indicate whether the second terminal device supports normal operation of a graphical interface;

[0013] a position acquisition unit, configured to interact with the second terminal device to acquire a target memory position if the current adaptation state is characterized as supported, the target memory position being a starting position of a memory used by the second terminal device to store target graphic data;

[0014] A data retrieval unit, configured to perform a data retrieval operation on the second terminal device according to the target memory location to obtain the graphic data;

[0015] An interface display unit, used to transfer the target graphic data into a graphic interface and display the graphic interface on a preset display device;

[0016] The interface debugging unit is used to debug the graphical interface in response to the user's interface debugging operation.

[0017] In a third aspect, an embodiment of the present application provides a terminal device, comprising a processor, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the processor, and the program includes instructions for executing the steps in the first aspect of the embodiment of the present application.

[0018] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program / instruction stored thereon, which implements the steps in the first aspect of the embodiment of the present application when the computer program / instruction is executed by a processor.

[0019] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements some or all of the steps described in the first aspect of the embodiment of the present application.

[0020] It can be seen that in the embodiment of the present application, the first terminal device determines the adaptation status of the current software and hardware environment of the second terminal device and the operation of the graphical interface to ensure that, when the current adaptation status supports it, it displays the graphical interface instead of the second terminal device and interacts with the user to complete the debugging of the graphical interface, thereby avoiding the problem of the second terminal device being unable to execute graphical interface development due to the unconfigured operating system and the unconfigured display screen, thereby improving debugging efficiency and flexibility. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0022] Figure 1 It is a structural block diagram of an interface debugging system provided in an embodiment of the present application;

[0023] Figure 2 It is a flowchart of a data processing method for graphical interface debugging provided by an embodiment of the present application;

[0024] Figure 3 is a schematic diagram of a scenario for determining a current adaptation state provided in an embodiment of the present application;

[0025] Figure 4 It is a schematic diagram of a scenario for obtaining a target memory location provided by an embodiment of the present application;

[0026] Figure 5 It is a scene schematic diagram of a user debugging graphical interface provided by an embodiment of the present application;

[0027] Figure 6 It is a block diagram of the functional units of a data processing device for graphical interface debugging provided by an embodiment of the present application;

[0028] Figure 7 It is a block diagram of the functional units of another data processing device for graphical interface debugging provided by an embodiment of the present application;

[0029] Figure 8 It is a structural block diagram of a terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0030] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0031] The terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.

[0032] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0033] See also Figure 1 , Figure 1 : is a structural block diagram of an interface debugging system provided by an embodiment of the present application. Figure 1 As shown, the interface debugging system 100 includes a first terminal device 110 and a second terminal device 120, wherein the second terminal device 120 is an embedded device. Before obtaining the relevant data of the graphical interface stored in the second terminal device 120, the first terminal device 110 will perform a device status determination operation on the second terminal device 120 to ensure that the current software and hardware environment of the second terminal device 120 can support the normal operation of the graphical interface. When it is determined that the current adaptation state of the second terminal device 120 is characterized as support, the first terminal device 110 will interact with the second terminal device 120 to obtain the target memory location, and then obtain the graphic data associated with the graphical interface. The first terminal device 110 will subsequently display the graphical interface instead of the second terminal device 120 according to the graphic data, and interact with the user 130 to debug the graphical interface. Among them, one first terminal device 110 is only connected to one second terminal device 120 at the same time, and each first terminal device 110 can support interaction with different models of second terminal devices 120, and the second terminal device 120 can be any embedded device on the market.

[0034] Based on this, an embodiment of the present application provides a data processing method for graphical interface debugging, and the embodiment of the present application is described in detail below in conjunction with the accompanying drawings.

[0035] See also Figure 2 , Figure 2This is a flow chart of a data processing method for graphical interface debugging provided by an embodiment of the present application. The method is applied to a first terminal device in an interface debugging system, the interface debugging system also includes a second terminal device, and the second terminal device is an embedded device; the method includes:

[0036] Step S201: performing a device status determination operation on a second terminal device to determine a current adaptation status of a software and hardware environment corresponding to the second terminal device.

[0037] The current adaptation status is used to indicate whether the second terminal device supports the normal operation of the graphical interface.

[0038] In one possible embodiment, a device status determination operation is performed on the second terminal device to determine the current adaptation status of the software and hardware environment corresponding to the second terminal device, including: obtaining device parameters of the second terminal device; determining a data collection table based on the device parameters; obtaining benchmark data corresponding to the first data item and the second data item; monitoring the operation process of the second terminal device to perform data collection based on the data collection table, and determining the collected data corresponding to the first data item and the second data item; and comparing the collected data and the benchmark data in turn based on the first data item and the second data item to determine the current adaptation status.

[0039] The data collection table includes a first data item corresponding to the hardware environment required for the second terminal device to run the graphical interface, and a second data item corresponding to the software environment required for the second terminal device to run the graphical interface.

[0040] Among them, this step is a specific implementation method for the first terminal device to determine the current adaptation state of the second terminal device in the current software and hardware environment, that is, the current software and hardware environment can support the normal operation of the graphical interface. The purpose of determining the current adaptation state is to ensure the stable operation of the system. By determining the current adaptation state, the compatibility issues between the second terminal device and the software and hardware environment can be discovered and handled in a timely manner to prevent system crashes or abnormal operations caused by compatibility issues. By determining the adaptation state, it can be ensured that the terminal device can achieve the expected fluency when running the graphical interface, thereby improving user satisfaction. In addition, only when the current adaptation state of the second terminal device is characterized as support can the subsequent acquisition of graphic data and the stable operation of the display and debugging of the graphical interface be guaranteed to avoid the service terminal caused by the device problem of the second terminal device. The specific implementation method for the first terminal device to obtain the benchmark data can be to determine the reference data with the highest frequency as the benchmark data based on the historical data fed back by the normal operation graphical interface of the third terminal device with the device parameters.

[0041] For example, see Figure 3 , Figure 3is a schematic diagram of a scenario for determining the current adaptation state provided by an embodiment of the present application. Figure 3 As shown, before the debugging of the graphical interface is officially started, a communication connection will be established between the first terminal device and the second terminal device. After the communication connection is established, the second terminal device will first send its own device parameters to the first terminal device so that the second terminal device can generate a corresponding data collection table. The content in the data collection table is the first data item corresponding to the hardware environment mentioned above and its corresponding benchmark data, as well as the second data item corresponding to the software environment and its corresponding benchmark data. After the data collection table is generated, the first terminal device will collect data from the second terminal device according to the table, thereby performing data comparison through the data collection table, and then determining the final current adaptation state to characterize whether the current internal hardware and software environment of the second terminal device supports the normal operation of the graphical interface.

[0042] Among them, in this step, the device status determination operation is performed on the second terminal device by first obtaining its device parameters, and then formulating a data collection table, which covers the hardware and software environment data items required to run the graphical interface; then, the benchmark data is obtained from the historical data of the third terminal device with similar device parameters and normal operation of the graphical interface; then, the operation of the second terminal device is monitored in real time and relevant data is collected; finally, the collected data is compared with the benchmark data to determine the adaptation status of the second terminal device under the current software and hardware environment. If the current adaptation status determined is characterized as support, it means that the hardware and software environment have been adjusted to a state that can support the normal startup and operation of the graphical interface, which provides a basis for subsequent debugging by obtaining memory addresses to transfer pictures. For the first terminal device, only when the graphical interface system of the embedded device itself can work normally, the terminal device has the opportunity to obtain and display the graphical interface of the embedded device through the network or other connection methods.

[0043] It can be seen that in this example, the first terminal device obtains the device parameters of the second terminal device to customize the corresponding data collection table for the second terminal device, and then determines the current adaptation status of the software and hardware environment of the second terminal device through data collection and data comparison. The purpose is to improve the success rate of subsequent calls to the target graphical interface and improve the stability of the interface debugging system operation.

[0044] In a possible embodiment, the collected data and the benchmark data are compared in sequence according to the first data item and the second data item to determine the current adaptation state, including: obtaining the reference deviation ranges corresponding to each first data item and each second data item respectively; determining the first adaptation state of each first data item in sequence for the reference deviation range and the benchmark data corresponding to each first data item; if each first adaptation state is characterized as supported, determining the second adaptation state of each second data item in sequence for the reference deviation range and the benchmark data corresponding to each second data item; if each second adaptation state is characterized as supported, determining that the current adaptation state is characterized as supported; if any second adaptation state is characterized as unsupported, determining that the current adaptation state is characterized as unsupported.

[0045] Among them, the reference deviation range is used to indicate the remaining data of the configuration deviation allowed by the software environment or hardware environment required for the second terminal device to run the graphical interface, the first adaptation state is used to indicate whether the hardware environment mapped by the corresponding first data item of the second terminal device supports the normal operation of the graphical interface, and the second adaptation state is used to indicate whether the software environment mapped by the corresponding second data item of the second terminal device supports the normal operation of the graphical interface.

[0046] Among them, in this step, the first terminal device first sets a reference deviation range for each first data item (hardware environment related data) and the second data item (software environment related data), and these ranges reflect the acceptable variation range of the hardware and software configuration required to run the graphical interface. Then, for each first data item, the collected data is compared with the benchmark data and the corresponding reference deviation range to determine whether the hardware environment supports the normal operation of the graphical interface (i.e., the first adaptation state). If the first adaptation state of all first data items indicates support, the process continues to perform the same comparison on the second data item to determine whether the software environment also supports the normal operation of the graphical interface (i.e., the second adaptation state). Finally, only when all first adaptation states and second adaptation states indicate support, the current adaptation state is determined to be supported; otherwise, as long as one second adaptation state indicates unsupported, the current adaptation state is determined to be unsupported. The principle of this step is based on data comparison and configuration tolerance analysis. By setting the reference deviation range, the process can take into account the reasonable changes in the hardware and software configuration, thereby more accurately evaluating the adaptability of the second terminal device in the current environment. The comparison process ensures that each data item is evaluated individually, allowing the precise identification of specific causes that may have caused adaptation issues.

[0047] Exemplarily, the types of the first data item may include memory occupancy (system memory usage percentage), storage read / write speed (the amount of data transferred per second in read / write operations (MB / s)), and graphics processing capability (the number of frames rendered per second (FPS)). Further, the benchmark data corresponding to the memory occupancy is 20%, and the reference deviation range (i.e., the allowable fluctuation range) is ±10%, the benchmark data corresponding to the storage read / write speed is 40%, and the reference deviation range is ±15%, the benchmark data corresponding to the storage read / write speed is read speed: 150MB / s; write speed: 100MB / s, and the reference deviation range is ±20%, and the benchmark data corresponding to the graphics processing capability is 60FPS, and the reference deviation range is ±15%.

[0048] Exemplarily, the types of the second data item may include operating system version (system version number and update patch), application compatibility (how the application runs on the device) and graphics driver version (driver version of the graphics processing unit). The benchmark data corresponding to the operating system version is the block number XXX; the reference deviation range: that is, the version difference is allowed to be ±1 minor version, and the patch update is not more than 3 months; the benchmark data corresponding to the application compatibility is the number of compatible applications: 95% of mainstream applications, no serious compatibility issues; the reference deviation range: the proportion of incompatible applications allowed: ≤5%, minor compatibility issues are acceptable; the corresponding benchmark data of the graphics driver version is xxx.xx.xx, and the reference deviation range: the version difference is allowed to be: ±1 minor version number.

[0049] It can be seen that in this example, the first terminal device improves system operating efficiency, ensures stability, and comprehensively optimizes the user experience by accurately determining the device adaptation status, that is, collecting hardware and software data and comparing them with benchmarks.

[0050] In one possible embodiment, the first data item includes at least one of the following types of reference data items: processor operating frequency, memory read and write speed, memory capacity and bandwidth, graphics processor model, and interface type of input device; and the second data item includes at least one of the following types of reference data items: operating system version number, driver version number, graphics library or graphics framework version number, and configuration file parameters of the application corresponding to the graphical interface.

[0051] Among them, the types of each reference data item in the first data item (i.e., the reference data item corresponding to the hardware environment) are introduced in turn. Among them, the processor operating frequency refers to the processor's base frequency, maximum turbo frequency, and current operating frequency. The processor operating frequency directly affects the device's processing power and response speed; the memory read and write speed refers to the memory read and write rate (MB / s). The memory read and write speed determines the efficiency of the device in processing data and running applications; the memory capacity and bandwidth refer to the total memory capacity (GB) and memory bandwidth (GB / s). The memory capacity and bandwidth determine the number and speed of tasks that the device can process simultaneously; the graphics processor model refers to the GPU model and its core number. The graphics processor model and core number affect the device's graphics processing capabilities and game performance; the input device interface type refers to the interface type of input devices such as keyboards and mice (such as USB, Bluetooth, etc.). The input device interface type determines the data transmission speed and compatibility between the device and the host.

[0052] Further, the types of each reference data item in the second data item (i.e., the reference data item corresponding to the software environment) are introduced in turn. Among them, the operating system version number refers to the major version number and minor version number of the operating system, and the operating system version number determines the software compatibility and security of the device; the driver version number refers to the version number of the device driver (such as the graphics card driver, the sound card driver, etc.), and the driver version number determines the performance and stability of the device in the operating system; the graphics library or graphics framework version number refers to the version number of each graphics library, and the graphics library or graphics framework version number determines the device's ability and compatibility in graphics processing; the configuration file parameters of the application corresponding to the graphical interface refer to the key parameters in the configuration file of the application, and the configuration file parameters of the application determine the performance and compatibility of the device when running a specific application. By presetting the benchmark data and the reference deviation range for the above first data item and the second data item, and then collecting and comparing data for the second terminal device based on them, the first terminal device can fully understand the software and hardware environment of the second terminal device for running the graphical interface, and determine its adaptation status in the current environment, thereby helping to improve the operating efficiency of subsequent devices, ensure system stability, and provide users with a smooth and efficient experience.

[0053] It can be seen that in this example, the first terminal device sets the types of data items corresponding to the hardware environment and software environment of the device by setting the types corresponding to the various first data items and the types corresponding to the various second data items, thereby improving the accuracy and comprehensiveness of determining the current adaptation status of the hardware and software environment of the second terminal device, and then improving the stability of the subsequent operation of the interface debugging system for the graphical interface.

[0054] Step S202: If the current adaptation status is characterized as supported, interact with the second terminal device to obtain the target memory location.

[0055] The target memory location is a starting memory location of the second terminal device for storing target graphic data.

[0056] In one possible embodiment, interacting with a second terminal device to obtain a target memory location includes: monitoring the memory usage rate and the amount of memory data occupied by the graphics process in real time; if the memory usage rate is less than or equal to a preset usage rate, and the amount of memory data is less than or equal to a preset memory threshold, obtaining a memory area range used by the graphics process, the memory area range being used to store associated data of the graphical interface; determining a sampling frequency based on an average frequency of change of the memory usage rate within a preset time period; generating a sampling instruction based on the sampling frequency and the memory area range; sending a sampling instruction to the second terminal device to obtain sample data from the second terminal device; and performing an analysis operation on a preset number of sample data to determine a target memory location of the graphical interface.

[0057] The graphic process is a related process opened by the second terminal device running the graphic interface, and the sampling instruction is used to instruct the second terminal device to perform a sampling operation of the sampling frequency within the memory area.

[0058] Among them, this step is a branch in which the memory usage rate occupied by the graphic process is less than or equal to the preset usage rate, and the amount of memory data is less than or equal to the preset memory threshold. Under this branch, the system of the first terminal device will obtain the memory area range used by the graphic process, and this range stores the associated data of the graphical interface. Then, the sampling frequency is determined according to the average change frequency of the memory usage rate within the preset time period, and a sampling instruction is generated based on this, and sent to the second terminal device. According to the sampling instruction, the second terminal device performs a sampling operation according to the sampling frequency within the specified memory area range, and sends the sample data back to the system. The system will eventually conduct an in-depth analysis of these sample data to determine the target memory location of the graphical interface. The principle of this process is based on memory monitoring, sampling analysis and data processing technology. By monitoring the memory usage of the graphic process in real time, it can be ensured that sampling is performed when the memory resources are sufficient and stable, thereby improving the accuracy and reliability of the data. The determination of the sampling frequency takes into account the dynamic changes in the memory usage rate to ensure that as much useful data as possible is obtained without affecting the system performance. Finally, through in-depth analysis of the sample data, the distribution of the graphical interface in the memory can be revealed, thereby locating the target memory location.

[0059] Furthermore, since the memory usage and memory data volume corresponding to the graphics process are relatively small, in order to increase the speed of obtaining the target memory location, a sampling method is adopted for data acquisition and data analysis, which effectively improves the efficiency of obtaining the target memory location and provides data support for subsequent graphics interface optimization and debugging.

[0060] It can be seen that in this example, by using intelligent sampling strategies and dynamically adjusting the sampling frequency, unnecessary resource consumption can be avoided while ensuring monitoring accuracy. And by conducting in-depth analysis of the preset number of sample data, the system can accurately determine the target memory location of the graphical interface, ensuring the normal display of the subsequent graphical interface while saving time and computing resources.

[0061] In a possible embodiment, after real-time monitoring of the memory usage rate and memory data volume occupied by the graphics process, the method further includes: if the memory usage rate is greater than a preset usage rate, or the memory data volume is greater than a preset memory threshold, obtaining the memory area range and the data storage format corresponding to the memory structure and the graphical interface of the second terminal device; determining the scan page size according to the memory structure and the data storage format; dividing the memory area range into multiple pages to be scanned according to the scan page size, and determining the page order; performing scanning operations on the multiple pages to be scanned in sequence according to the page order to read the target memory data; performing data parsing operations on the target memory data to determine the target memory location.

[0062] Among them, this step is a complementary branch to the solution of the previous step. This step is aimed at the situation where the memory usage corresponding to the graphics process is greater than the preset usage, or the amount of memory data is greater than the preset memory advance. The solutions involved in the two steps monitor the memory usage of the graphics process in real time and flexibly respond to different memory states (whether low load or high load). Both solutions can ensure that memory data is effectively acquired and analyzed at the right time and conditions, thereby accurately locating the target memory location of the graphical interface. This not only helps to improve the stability and performance of the system, but also provides valuable data support for subsequent graphics interface optimization, debugging and troubleshooting.

[0063] Among them, the principle of the scheme involved in this step lies in the in-depth understanding and flexible response to the memory structure. When the memory usage rate or the amount of memory data is monitored to exceed the preset threshold, the system will not immediately perform sampling, but first obtain the memory area range and the memory structure of the second terminal device and the data storage format corresponding to the graphical interface. This information is crucial for subsequent memory scanning and data parsing. According to the memory structure and data storage format, the system can determine the most suitable scanning page size, and then divide the memory area range into multiple pages to be scanned, and determine the order of page scanning. This step ensures the efficiency and accuracy of the scanning operation. Subsequently, the system performs the scanning operation in sequence according to the page order to read the target memory data. Finally, through the data parsing operation, the system can identify and determine the target memory location. In terms of memory, the scheme fully considers the dynamics and complexity of memory usage. Whether it is sampling analysis when the memory usage rate is low or scanning parsing when the memory usage rate is high, the first terminal device can flexibly adjust the strategy according to the current memory status to ensure that the target memory location is efficiently obtained without affecting the normal operation of the system. This not only helps to optimize memory usage, but also improves the overall performance and stability of the system.

[0064] For example, see Figure 4 , Figure 4 Schematic diagram of a scenario for obtaining a target memory location provided by an embodiment of the present application. Figure 4 As shown, the memory usage rate and memory data volume corresponding to the graphic process are determined by monitoring the graphic process corresponding to the graphic interface, and then when it is detected that the memory usage rate and the memory data volume are both less than or equal to the preset threshold, the data sampling strategy (the specific implementation method specifically described in the previous example) is executed for the second terminal device; or, when it is detected that any one of the memory usage rate and the memory data volume is greater than the preset threshold, the scanning page tracking strategy (the specific implementation method specifically described in this example) is executed for the second terminal device. Both the data sampling strategy and the scanning page tracking strategy can obtain the corresponding position (target memory position) of the graphic data stored in the memory of the second terminal device.

[0065] It can be seen that in this example, in response to the situation where the amount of data or memory usage corresponding to the graphics process is large, a refined address tracking mode is adopted to improve the data integrity, accuracy and reliability of the target memory location, that is, to fully cover the memory area to obtain complete graphical interface information, thereby improving the flexibility of the first terminal device in data processing.

[0066] Step S203: performing a data retrieval operation on the second terminal device according to the target memory location to obtain graphic data.

[0067] Among them, the specific implementation method of this step can be that after determining the target memory location of the graphical interface, the first terminal device sends a data retrieval instruction to the second terminal device, and the instruction contains detailed information of the target memory location. After the second terminal device receives the instruction, it directly accesses and reads the corresponding graphic data according to the memory location specified in the instruction, and then returns these data to the first terminal device, thereby completing the retrieval of the graphic data.

[0068] Step S204: transferring the target graphic data into a graphic interface, and displaying the graphic interface on a preset display screen device.

[0069] Among them, the specific implementation method of this step can be that the first terminal device first uses graphics processing technology to decode and render the acquired target graphics data to generate a corresponding graphical interface, and then converts the data into a signal that can be recognized by the display through the graphics card, and transmits the signal to a preset display device with the help of a specific interface, and finally the display device presents the graphical interface.

[0070] Step S205 , debugging the graphical interface in response to the user's interface debugging operation.

[0071] In one possible embodiment, in response to a user's interface debugging operation, debugging a graphical interface includes: when detecting a user's interface debugging operation on a displayed graphical interface, determining interaction event information according to the interface debugging operation; determining a data acquisition range in a target memory location according to an element type and a change event; based on the data acquisition range, retrieving element data of an element to be debugged for a second terminal device to modify the element to be debugged; refreshing an interface layout of the graphical interface according to the modified element to be debugged; and rendering and displaying an updated graphical interface on a display device according to the refreshed interface layout and the modified element to be debugged.

[0072] The interactive event information is used to indicate the element type of the element to be debugged and the change event corresponding to the element type, and the data acquisition range is used to indicate the target memory area related to the element to be debugged.

[0073] Among them, element types include but are not limited to buttons, text boxes, images, and new controls, and corresponding change events include but are not limited to window resizing, new control loading, and animation effect triggering.

[0074] Specifically, in this example, when the user performs a debugging operation on the graphical interface displayed on the display device in some way (such as mouse click, keyboard input, etc.), the first terminal device will detect this behavior. At this time, the first terminal device will determine an interactive event information according to the user's operation, which includes the type of element (element to be debugged) that the user wants to debug and the upcoming change event of the element (such as color change, size adjustment, position movement, etc.). The first terminal device will determine a data acquisition range according to the type and change event of the element to be debugged. This range actually indicates the target memory area related to the element to be debugged, and the first terminal device needs to retrieve the current data of the element to be debugged from this area. This step is the key to ensure that the first terminal device can accurately obtain the element data that the user wants to modify. Further, through the data acquisition range, the first terminal device will retrieve the element data corresponding to the element to be debugged to change the attribute or state of the element to be debugged. After the modification is completed, the first terminal device will refresh the interface layout of the graphical interface according to these modified elements to be debugged. This step is the key to ensure that the graphical interface can reflect the user's debugging results in real time, and finally, the updated graphical interface is re-rendered and displayed on the display device. This way, users can see the results of their debugging and make further adjustments as needed.

[0075] Among them, the data acquisition range in the target memory location is determined according to the element type and the change event. The specific implementation method is to parse the element type information to locate its basic structure in the memory, and combine the specific type of the change event (such as attribute change, state transition, etc.) to accurately define the data range that needs to be read or modified from the memory structure to ensure that only the necessary memory data directly related to the element to be debugged is obtained.

[0076] For example, see Figure 5 , Figure 5 Schematic diagram of a user debugging graphical interface provided by an embodiment of the present application. Figure 5As shown, the user interacts with the display screen device to modify the color of a circular element. In this process, when the display screen device of the first terminal device detects that the user decides to modify the color of a circular element, the first terminal device first identifies that the element being operated by the user is a circle. According to the storage structure of the circular element in the memory, the first terminal device knows that it needs to find the attribute data related to the circle, such as color, radius, position, etc. Then it is identified that the operation performed by the user is to change the color of the circular element. According to the type information of the circular element and the color change event, the first terminal device determines that the data acquisition range of the element data to be obtained from the memory of the second terminal device is data related to the color attribute of the circular element. The first terminal device will not obtain data related to other attributes of the circular element (such as radius, position, etc.) or other types of elements (such as rectangles, text, etc.) because these data are irrelevant to the current operation. In the subsequent process, the first terminal device will retrieve data according to the data acquisition range to obtain the color attribute data of the circular element, and modify this data value to change the color of the circle. The first terminal device will store the modified color data back into its own memory, and finally re-render the circular element according to the updated memory data through the graphical interface editor to display the new color.

[0077] It can be seen that in this example, by combining this information with the picture display, developers are provided with more comprehensive and intuitive debugging feedback, which helps them locate and solve problems in the graphical interface more quickly and improve debugging efficiency. In addition, during the debugging process, the acquisition range is shortened according to the specific debugging operation, which can improve the accuracy and efficiency of the first terminal device debugging the target element.

[0078] It can be seen that the first terminal device ensures the smooth operation of the graphical interface by performing a device status determination operation on the second terminal device, and completes the debugging of the graphical interface by obtaining the target memory location instead of the embedded device interacting with the user, thereby improving the flexibility of the interface debugging system and the stability of the system operation.

[0079] The following is an embodiment of the device of the present application. The embodiment of the device of the present application and the embodiment of the method of the present application are of the same concept and are used to execute the method described in the embodiment of the present application. For the convenience of explanation, the embodiment of the device of the present application only shows the part related to the embodiment of the device of the present application. For the specific technical details not disclosed, please refer to the description of the embodiment of the method of the present application, which will not be repeated here one by one.

[0080] The embodiment of the present application provides a data processing device for graphical interface debugging, which is applied to Figure 1The first terminal device 110 in the interface debugging system 100 shown, the interface debugging system 100 also includes a second terminal device 120, the second terminal device 120 is an embedded device, and the first terminal device 110 is communicatively connected with the second terminal device 120. Specifically, the data processing device for graphical interface debugging is used to execute the steps executed by the server in the above data processing method for graphical interface debugging. The data processing device for graphical interface debugging provided in the embodiment of the present application may include modules corresponding to the corresponding steps.

[0081] The embodiment of the present application can divide the functional modules of the data processing device for graphical interface debugging according to the above method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. The division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0082] In the case of dividing each functional module into corresponding functional modules, Figure 6 The present invention is a block diagram of the functional units of a data processing device for debugging a graphical interface provided by an embodiment of the present application; a data processing device 60 for debugging a graphical interface is applied to a first terminal device in an interface debugging system, and the interface debugging system also includes a second terminal device; the device includes: a state determination unit 601, which is used to perform a device state determination operation on the second terminal device to determine the current adaptation state of the software and hardware environment corresponding to the second terminal device, and the current adaptation state is used to characterize whether the second terminal device supports the normal operation of the graphical interface; a position acquisition unit 602, which is used to interact with the second terminal device to obtain a target memory location if the current adaptation state is characterized as support, and the target memory location is the memory starting location used by the second terminal device to store target graphic data; a data retrieval unit 603, which is used to perform a data retrieval operation on the second terminal device according to the target memory location to obtain graphic data; an interface display unit 604, which is used to transfer the target graphic data into a graphical interface and display the graphical interface on a preset display device; an interface debugging unit 605, which is used to debug the graphical interface in response to the user's interface debugging operation.

[0083] In a possible embodiment, in performing a device status determination operation on the second terminal device to determine the current adaptation status of the software and hardware environment corresponding to the second terminal device, the status determination unit 601 is specifically used to: obtain device parameters of the second terminal device; determine a data collection table based on the device parameters, the data collection table including a first data item corresponding to the hardware environment required for the second terminal device to run a graphical interface, and a second data item required for the software environment required for the second terminal device to run the graphical interface; obtain benchmark data corresponding to the first data item and the second data item; monitor the operation process of the second terminal device to perform data collection according to the data collection table, and determine the collected data corresponding to the first data item and the second data item; and compare the collected data and the benchmark data in sequence according to the first data item and the second data item to determine the current adaptation status.

[0084] In a possible embodiment, in terms of comparing the collected data and the benchmark data in sequence according to the first data item and the second data item to determine the current adaptation state, the state determination unit 601 is specifically used to: obtain the reference deviation range corresponding to each first data item and each second data item respectively, the reference deviation range is used to indicate the remaining data of the configuration deviation allowed by the software environment or hardware environment required for the second terminal device to run the graphical interface; determine the first adaptation state of each first data item in sequence for the reference deviation range and the benchmark data corresponding to each first data item, the first adaptation state is used to indicate whether the second terminal device supports the normal operation of the graphical interface in the hardware environment mapped by the corresponding first data item; if each first adaptation state is characterized as supported, then determine the second adaptation state of each second data item in sequence for the reference deviation range and the benchmark data corresponding to each second data item, the second adaptation state is used to indicate whether the second terminal device supports the normal operation of the graphical interface in the software environment mapped by the corresponding second data item; if each second adaptation state is characterized as supported, then determine that the current adaptation state is characterized as supported; if any second adaptation state is characterized as unsupported, then determine that the current adaptation state is characterized as unsupported.

[0085] In one possible embodiment, the first data item includes at least one of the following types of reference data items: processor operating frequency, memory read and write speed, memory capacity and bandwidth, graphics processor model, and interface type of input device; and the second data item includes at least one of the following types of reference data items: operating system version number, driver version number, graphics library or graphics framework version number, and configuration file parameters of the application corresponding to the graphical interface.

[0086] In one possible embodiment, in terms of interacting with the second terminal device to obtain the target memory location, the location acquisition unit 602 is specifically used to: monitor the memory usage rate and memory data volume occupied by the graphics process in real time, the graphics process is a related process opened by the second terminal device to run the graphical interface; if the memory usage rate is less than or equal to the preset usage rate, and the memory data volume is less than or equal to the preset memory threshold, then obtain the memory area range used by the graphics process, and the memory area range is used to store associated data of the graphical interface; determine the sampling frequency according to the average change frequency of the memory usage rate within a preset time period; generate a sampling instruction according to the sampling frequency and the memory area range, and the sampling instruction is used to instruct the second terminal device to perform a sampling operation of the sampling frequency in the memory area range; send a sampling instruction to the second terminal device to obtain sample data from the second terminal device; perform an analysis operation on a preset number of sample data to determine the target memory location of the graphical interface.

[0087] In a possible embodiment, after real-time monitoring of the memory usage rate and memory data volume occupied by the graphics process, the location acquisition unit 602 is specifically used to: if the memory usage rate is greater than a preset usage rate, or the memory data volume is greater than a preset memory threshold, obtain the memory area range and the data storage format corresponding to the memory structure and the graphical interface of the second terminal device; determine the scan page size according to the memory structure and the data storage format; divide the memory area range into multiple pages to be scanned according to the scan page size, and determine the page order; according to the page order, perform scanning operations on the multiple pages to be scanned in turn to read the target memory data; perform data parsing operations on the target memory data to determine the target memory location.

[0088] In one possible embodiment, in response to the user's interface debugging operation, in debugging the graphical interface, the interface debugging unit 605 is specifically used for: when a user's interface debugging operation on the displayed graphical interface is detected, determining the interactive event information according to the interface debugging operation, the interactive event information is used to indicate the element type of the element to be debugged and the change event corresponding to the element type; determining the data acquisition range in the target memory location according to the element type and the change event, the data acquisition range is used to indicate the target memory area related to the element to be debugged; according to the data acquisition range, retrieving the element data of the element to be debugged for the second terminal device to modify the element to be debugged; refreshing the interface layout of the graphical interface according to the modified element to be debugged; rendering and displaying the updated graphical interface on the display device according to the refreshed interface layout and the modified element to be debugged.

[0089] In the case of integrated units, such as Figure 7 As shown, Figure 7 This is a block diagram of the functional units of another data processing device for graphical interface debugging provided by an embodiment of the present application. Figure 7 In the embodiment, the data processing device 60 for graphical interface debugging includes: a processing module 702 and a communication module 701. The processing module 702 is used to control and manage the actions of the data processing device for graphical interface debugging, for example, the steps of the state determination unit 601, the position acquisition unit 602, the data retrieval unit 603, the interface display unit 604 and the interface debugging unit 605, and / or other processes for executing the technology described herein. The communication module 701 is used to support the interaction between the data processing device for graphical interface debugging and other devices. Figure 7 As shown, the data processing device for graphical interface debugging may include a storage module 703, and the storage module 703 is used to store program codes and data of the data processing device for graphical interface debugging.

[0090] Among them, the processing module 702 can be a processor or a controller, for example, a central processing unit (CPU), a general processor, a digital signal processor (DSP), an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component or any combination thereof. It can implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements a computing function, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like. The communication module 701 can be a transceiver, an RF circuit or a communication interface, and the like. The storage module 703 can be a memory.

[0091] All relevant contents of each scenario involved in the above method embodiment can be referred to the functional description of the corresponding functional module, which will not be repeated here. Figure 2 The data processing method for graphical interface debugging is shown.

[0092] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When a computer instruction or computer program is loaded or executed on a computer, a process or function according to an embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. Computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, computer instructions can be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center containing one or more available media sets. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state hard disk.

[0093] Figure 8 is a structural block diagram of a terminal device provided in an embodiment of the present application. Figure 8 As shown, the terminal device 800 may include one or more of the following components: a processor 810, and a memory 820 coupled to the processor 810, wherein the memory 820 may store one or more programs 821 (i.e., computer programs), and the one or more computer programs may be configured to implement the methods described in the above embodiments when executed by one or more processors 810.

[0094] The processor 810 may include one or more processing cores. The processor 810 uses various interfaces and lines to connect various parts of the entire terminal device 800, and executes various functions and processes data of the terminal device 800 by running or executing instructions, programs, code sets or instruction sets stored in the memory 820, and calling data stored in the memory 820. Optionally, the processor 810 can be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), and programmable logic array (PLA). The processor 810 can integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing display content; and the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 810, but may be implemented separately through a communication chip.

[0095] The memory 820 may include a random access memory (RAM) or a read-only memory (ROM). The memory 820 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 820 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc. The data storage area may also store data created by the terminal device 800 during use, etc.

[0096] It is understandable that the terminal device 800 may include more or fewer structural elements than those in the above structural block diagram, which is not limited here.

[0097] An embodiment of the present application also provides a computer storage medium, on which a computer program / instruction is stored. When the computer program / instruction is executed by a processor, part or all of the steps of any method recorded in the above method embodiments are implemented.

[0098] An embodiment of the present application also provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute part or all of the steps of any method recorded in the above method embodiments.

[0099] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0100] In the several embodiments provided in the present application, it should be understood that the disclosed methods, devices and systems can be implemented in other ways. For example, the device embodiments described above are only schematic; for example, the division of units is only a logical function division, and there may be other division methods in actual implementation; for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0101] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0102] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0103] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform some steps of the methods of various embodiments of the present invention. The aforementioned storage medium includes: a USB flash drive, a mobile hard disk, a magnetic disk, an optical disk, a volatile memory or a non-volatile memory. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM) or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM) and direct RAM bus random access memory (DR RAM), among other media that can store program code.

[0104] Although the present invention is disclosed as above, the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions without departing from the spirit and scope of the present invention, and can make various changes and modifications, including the combination of the above-mentioned different functions and implementation steps, including software and hardware implementation methods, all of which are within the scope of protection of the present invention.

Claims

1. A data processing method for graphical interface debugging, characterized in that: A first terminal device is applied to an interface debugging system, wherein the interface debugging system further comprises a second terminal device, and the second terminal device is an embedded device; the method comprises: Performing a device status determination operation on the second terminal device to determine a current adaptation status of a software and hardware environment corresponding to the second terminal device, wherein the current adaptation status is used to indicate whether the second terminal device supports normal operation of a graphical interface; If the current adaptation state is characterized as support, interacting with the second terminal device to obtain a target memory location, where the target memory location is a memory start location of the second terminal device for storing target graphic data; According to the target memory location, performing a data retrieving operation on the second terminal device to obtain the graphic data; Transferring the target graphic data to the graphic interface, and displaying the graphic interface on a preset display screen device; In response to an interface debugging operation of the user, the graphical interface is debugged.

2. The method according to claim 1, characterized in that The performing a device status determination operation on the second terminal device to determine a current adaptation status of a software and hardware environment corresponding to the second terminal device includes: Acquire device parameters of the second terminal device; Determine a data collection table according to the device parameters, the data collection table including a first data item corresponding to a hardware environment required for the second terminal device to run the graphical interface, and a second data item corresponding to a software environment required for the second terminal device to run the graphical interface; Acquire reference data corresponding to the first data item and the second data item; Monitoring the operation process of the second terminal device to collect data according to the data collection table, and determining the collected data corresponding to the first data item and the second data item; The collected data and the reference data are sequentially compared according to the first data item and the second data item to determine the current adaptation state.

3. The method according to claim 2, characterized in that The step of sequentially comparing the collected data and the reference data according to the first data item and the second data item to determine the current adaptation state includes: Obtaining a reference deviation range corresponding to each of the first data items and each of the second data items, respectively, the reference deviation range being used to indicate the remaining data of the configuration deviation allowed by the software environment or the hardware environment required for the second terminal device to run the graphical interface; determining, in sequence for each reference deviation range and the benchmark data corresponding to each first data item, a first adaptation state of each first data item, the first adaptation state being used to indicate whether the second terminal device supports normal operation of the graphical interface in a hardware environment mapped by the corresponding first data item; If each of the first adaptation states is characterized as supported, determining a second adaptation state of each of the second data items in turn for the reference deviation range and the benchmark data corresponding to each of the second data items, the second adaptation state being used to indicate whether the second terminal device supports normal operation of the graphical interface in the software environment mapped by the corresponding second data item; If each of the second adaptation states is characterized as supported, determining that the current adaptation state is characterized as supported; If any one of the second adaptation states is characterized as not supported, it is determined that the current adaptation state is characterized as not supported.

4. The method according to claim 3, characterized in that The first data item includes at least one of the following types of reference data items: processor operating frequency, memory read and write speed, memory capacity and bandwidth, graphics processor model, and input device interface type; and, The second data item includes at least one of the following types of reference data items: operating system version number, driver version number, graphics library or graphics framework version number, and configuration file parameters of an application corresponding to the graphical interface.

5. The method according to claim 1, characterized in that The interacting with the second terminal device to obtain the target memory location includes: real-time monitoring of the memory usage rate and memory data volume occupied by the graphic process, wherein the graphic process is a related process opened by the second terminal device running the graphic interface; If the memory usage rate is less than or equal to a preset usage rate, and the memory data volume is less than or equal to a preset memory threshold, then obtaining a memory area range used by the graphic process, wherein the memory area range is used to store associated data of the graphic interface; Determine the sampling frequency according to the average change frequency of memory usage within a preset time period; Generate a sampling instruction according to the sampling frequency and the memory area range, wherein the sampling instruction is used to instruct the second terminal device to perform a sampling operation of the sampling frequency in the memory area range; Sending the sampling instruction to the second terminal device to obtain sample data from the second terminal device; An analysis operation is performed on a preset number of the sample data to determine a target memory location of the graphical interface.

6. The method according to claim 5, characterized in that After real-time monitoring of the memory usage rate and the amount of memory data occupied by the graphics process, the method further includes: If the memory usage rate is greater than the preset usage rate, or the memory data volume is greater than the preset memory threshold, then obtaining the memory area range and the memory structure of the second terminal device and the data storage format corresponding to the graphical interface; Determine the scan page size according to the memory structure and the data storage format; According to the scan page size, the memory area range is divided into a plurality of pages to be scanned, and the page order is determined; According to the page sequence, sequentially performing scanning operations on the multiple pages to be scanned to read target memory data; A data parsing operation is performed on the target memory data to determine the target memory location.

7. The method according to any one of claims 1 to 6, characterized in that: The step of debugging the graphical interface in response to an interface debugging operation by a user includes: When an interface debugging operation of the user on the displayed graphical interface is detected, interaction event information is determined according to the interface debugging operation, where the interaction event information is used to indicate an element type of the element to be debugged and a change event corresponding to the element type; Determine a data acquisition range in the target memory location according to the element type and the change event, wherein the data acquisition range is used to indicate a target memory area related to the element to be debugged; Retrieving element data of the element to be debugged for the second terminal device according to the data acquisition range, so as to modify the element to be debugged; Refreshing the interface layout of the graphical interface according to the modified element to be debugged; According to the refreshed interface layout and the modified elements to be debugged, the updated graphical interface is rendered and displayed on the display device.

8. A data processing device for graphical interface debugging, characterized in that: A first terminal device applied to an interface debugging system, wherein the interface debugging system further comprises a second terminal device, and the second terminal device is an embedded device; the device comprises: a state determination unit, configured to perform a device state determination operation on the second terminal device to determine a current adaptation state of a software and hardware environment corresponding to the second terminal device, wherein the current adaptation state is used to indicate whether the second terminal device supports normal operation of a graphical interface; a position acquisition unit, configured to interact with the second terminal device to acquire a target memory position if the current adaptation state is characterized as supported, wherein the target memory position is a starting position of a memory used by the second terminal device to store target graphic data; A data retrieving unit, configured to perform a data retrieving operation on the second terminal device according to the target memory location to obtain the graphic data; An interface display unit, used for transferring the target graphic data into the graphic interface and displaying the graphic interface on a preset display screen device; The interface debugging unit is used to debug the graphical interface in response to the user's interface debugging operation.

9. A terminal device, characterized in that: The method comprises a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the processor, and the programs include instructions for executing the steps in the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: A computer program for electronic data exchange is stored, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 7.

Images