Control attribute display method and device, electronic equipment and storage medium

Abstract

The application belongs to the technical field of computers, and particularly relates to a control attribute display method and device, electronic equipment and storage medium. The method comprises the following steps: acquiring attribute information of a target control, and converting the attribute information into corresponding field objects; storing the field objects into an array container to obtain an attribute object list container; in response to an attribute display instruction of the target control, acquiring the field objects from the attribute object list container; and displaying the attribute information by using each sub-template in a preset general template according to a matching result between a data type of the field objects and data types of each sub-template in the general template. The application can improve the efficiency of displaying attribute information of a control.

Description

Technical Field

[0001] This application belongs to the field of computer technology, and specifically relates to a method, apparatus, computer-readable medium, electronic device, and computer program product for displaying control attributes. Background Technology

[0002] In the gaming industry, editors used to edit game scenes typically provide a large number of controls to enrich the game effects, and each control has different attribute types that can be set.

[0003] Each control with different attribute types corresponds to a UI template. A new UI template needs to be designed for each new control type. As the number of controls increases, the expansion of control type attributes leads to bloated code and UI templates, hindering iteration. Summary of the Invention

[0004] The purpose of this application is to provide a method, apparatus, computer-readable medium, and electronic device for displaying control properties, so as to improve the efficiency of displaying control properties.

[0005] According to one aspect of the embodiments of this application, a method for displaying control properties is provided, the method comprising:

[0006] Obtain the attribute information of the target control and convert the attribute information into corresponding field objects;

[0007] Store the field objects into an array container to obtain a list container of attribute objects;

[0008] In response to the property display instruction of the target control, the field object is obtained from the property object list container;

[0009] Based on the matching result between the data type of the field object and the data type of each sub-template in the preset general template, the attribute information is displayed using each sub-template.

[0010] According to one aspect of the embodiments of this application, a control property display device is provided, the device comprising:

[0011] The field conversion module is used to obtain the attribute information of the target control and convert the attribute information into corresponding field objects;

[0012] The storage module is used to store the field objects into an array container to obtain a list container of attribute objects;

[0013] The field object acquisition module is used to retrieve the field object from the attribute object list container in response to the attribute display instruction of the target control;

[0014] The attribute display module is used to display the attribute information using the sub-templates based on the matching results between the data type of the field object and the data type of each sub-template in the preset general template.

[0015] In one exemplary embodiment of this application, the device is configured as follows:

[0016] Obtain the field object name, data type, and attribute value of each attribute information;

[0017] Based on the preset data storage format of the data type, the attribute value is stored in the corresponding field object name to obtain the corresponding field object.

[0018] In one exemplary embodiment of this application, the device is configured as follows:

[0019] Based on the identifier of the target control, the property object list container is traversed and queried to obtain at least one field object of the target control.

[0020] In one exemplary embodiment of this application, the device is configured as follows:

[0021] Retrieve the attribute values ​​stored in each field object;

[0022] Based on the matching result, the attribute value is assigned to the corresponding sub-template, and the attribute bar obtained after assignment is displayed.

[0023] In one exemplary embodiment of this application, the device is configured as follows:

[0024] The attribute bar is obtained by combining and displaying the sub-templates according to their arrangement order in the general template.

[0025] According to one aspect of the embodiments of this application, an electronic device is provided, the electronic device comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the control attribute display method as described above by executing the executable instructions.

[0026] According to one aspect of the embodiments of this application, a computer-readable storage medium is provided, on which computer-readable instructions are stored, which, when executed by a processor, implement the control attribute display method as described in the above technical solutions.

[0027] According to one aspect of the embodiments of this application, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the control attribute display method as described in the above technical solutions.

[0028] In this embodiment, by acquiring the various attribute information of the target control, converting the corresponding attribute information into corresponding field objects, and storing the field objects in an array container to obtain an attribute object list container, upon receiving the attribute display instruction of the target control, the field objects of the target control are retrieved from the attribute object list container. Based on the data type of the field objects, the corresponding sub-template is matched in the general template, and the attribute information of the target control is displayed using the sub-template. By using the attribute list container as an intermediate container to store the field objects of the target control, all attribute information of the target control can be displayed through the general template and the field objects, which is beneficial to improving the display effect of control attributes. Displaying all attribute information through the general template facilitates the management of the target control.

[0029] Other features and advantages of this application will become apparent from the following detailed description, or may be learned in part from practice of this application.

[0030] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0031] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0032] Figure 1 A flowchart illustrating the control property display method according to an embodiment of this application is shown.

[0033] Figure 2 This illustration shows a flowchart of the steps for converting attribute information into field information according to an embodiment of this application.

[0034] Figure 3 A flowchart illustrating the steps for displaying attribute information using a sub-template according to an embodiment of this application is shown.

[0035] Figure 4A schematic diagram of a sub-template for displaying attribute information provided in an embodiment of this application is shown.

[0036] Figure 5 A schematic diagram of the attribute bar provided in one embodiment of this application is shown.

[0037] Figure 6 This illustration shows a schematic diagram of the relationship between the various components in a control property display method provided in an embodiment of this application.

[0038] Figure 7 A schematic diagram of the structure of a control attribute display device provided in an embodiment of this application is shown.

[0039] Figure 8 A schematic diagram of a computer system architecture suitable for implementing the embodiments of this application is shown. Detailed Implementation

[0040] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this application more comprehensive and complete, and to fully convey the concept of the exemplary embodiments to those skilled in the art.

[0041] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this application. However, those skilled in the art will recognize that the technical solutions of this application can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this application.

[0042] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0043] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0044] It should be noted that the control property display method provided in this application embodiment can be executed by the server, and correspondingly, the control property display device is set in the server.

[0045] In this embodiment, a control refers to an encapsulation of data and methods. A control may have its own properties and methods. Properties are the accessors of the control's data. Methods refer to the functionality represented by the control itself.

[0046] For example, editors used to edit game scenes provide a large number of controls to enrich game effects. This results in each control having many different types of attribute information that can be set, such as character, numeric, boolean, array, or a combination of these. Controls are categorized based on their attribute information, and each category corresponds to a display style. As the number of control types increases, the number of corresponding display styles also increases, making the control style code difficult to maintain and hindering iteration. Therefore, the control attribute display method proposed in this application aims to improve the display effect of control attribute information and, to some extent, facilitates the management of multiple controls.

[0047] Figure 1 The flowchart illustrates a method for displaying control properties according to an embodiment of this application. This method can be executed by a terminal device and includes steps S110 to S140.

[0048] S110: Obtain the attribute information of the target control and convert the attribute information into the corresponding field object.

[0049] The target control refers to the control used to display attribute information in the embodiments of this application. The target control includes at least one type of attribute information, and each type of attribute information is converted into a corresponding field object.

[0050] Attribute information is used to represent attribute information. The data type and attribute value of attribute information are stored through field objects. Optionally, the field object also includes a field object name, which is used to distinguish different attribute information.

[0051] The data types of attribute information include character, numeric, boolean, vector, array, etc.

[0052] S120: Store the field objects into an array container to obtain a list container of attribute objects.

[0053] After converting all the attribute information of the target control into corresponding field objects, all field objects are stored in an array container to obtain a list container of attribute objects.

[0054] A property object list container is a type of array container where the property information of the target control is stored in the data container in the format of field objects, resulting in a property object list container.

[0055] The property object list container stores all field objects for each target control, on a per-target-control basis.

[0056] S130, in response to the property display instruction of the target control, retrieves the field object from the property object list container.

[0057] When it is necessary to display the property information of the target control, the response is made by retrieving the field object of the target control from the property object list container.

[0058] Optionally, based on the identifier of the target control, the property object list container is traversed and queried until the corresponding object field of the target control is found.

[0059] S140, based on the matching result between the data type of the field object and the data type of each sub-template in the preset general template, use each sub-template to display each attribute information.

[0060] Specifically, the field object stores the data type of attribute information. The general template is a pre-designed shared template based on the display style of various types of attribute information. The general template includes sub-templates for different types of field objects.

[0061] Based on the matching result between the data type of the field object and the data type of the sub-template, the matching sub-template is used to display the field object of the corresponding type.

[0062] For example, a field object stores three types of attribute information: attribute A, attribute B, and attribute C. The data types of attribute information A, attribute B, and attribute C are all different. A general template includes sub-templates A, B, and C. Attribute information A matches the data type of sub-template A, attribute information B matches the data type of sub-template B, and attribute information C matches the data type of sub-template C; therefore, attribute information A is displayed through sub-template A, attribute information B is displayed through sub-template B, and attribute information C is displayed through sub-template C.

[0063] In this embodiment, by acquiring the various attribute information of the target control, converting each attribute information into a corresponding field object, and storing the field objects in an array container, an attribute object list container is obtained. When it is necessary to display the attribute information of the target control, the field object of the target control is retrieved from the attribute object list container. The corresponding sub-template is matched in the general template according to the data type of the field object. The attribute information of the target control is displayed through the sub-template. By designing the attribute object list container as a transfer object to connect the attribute information of the target control and the general template, the attribute information of the target control is converted into field objects and stored in the attribute object list container. Thus, the attribute information of the target control can be displayed through the general template, which is beneficial to improving the display effect of the control attributes. Displaying all attributes through the general template facilitates the management of the target control and is conducive to iterating the display style of the attribute information of the target control.

[0064] In this embodiment, as an optional implementation method, such as Figure 2 As shown, in step S110, the attribute information of the target control is obtained and the attribute information is converted into the corresponding field object, including the following steps S210 to S220.

[0065] S210, obtain the field object name, data type, and attribute value of each attribute information.

[0066] Field object names are used to distinguish between different attribute information. The data type of each attribute refers to its type, such as character or array. The attribute value refers to the corresponding numerical value; for example, if the data type is character, the attribute value will be a string.

[0067] S220: Based on the preset data storage format for the data type, the attribute value is stored in the corresponding field object name to obtain the corresponding field object.

[0068] For each data type, a corresponding data storage format is preset, and the attribute values ​​are stored according to the preset data storage format to obtain the corresponding field object.

[0069] It should be noted that the number of field objects is the same as the number of attribute information.

[0070] For example, target control 1 has three attribute information: attribute information A, attribute information B, and attribute information C. After converting each attribute information into a field object, we get three field objects: field object A, field object B, and field object C.

[0071] Field object A can be represented as FieldObjectA = {name, type, value}. Name represents the attribute name. If attribute object A is a color attribute, then the attribute name is color. Type represents the data type. If attribute object A is a color attribute, then it belongs to the three-dimensional array type, so type = threeArray. Value represents the attribute value. If attribute object A is a color attribute, then value is the corresponding RGB value, for example, [135, 266, 250].

[0072] In this embodiment, by designing field objects, the attribute information of the target control is converted into field objects. The field objects store the data type and attribute value of the attribute information. When displaying the attribute information of the target control, the sub-templates in the general template can be quickly matched by reading the data type in the field objects.

[0073] As an optional implementation, VALUEMAP is designed as the default data storage format for attribute information with array data type, and is used to store attribute values.

[0074] For attribute information of data type, VALUEMAP is designed as the storage format, and the attribute values ​​of array-type attribute information are stored through VALUEMAP.

[0075] For example, if attribute information B is an array type attribute information, the corresponding field object B is represented as FieldObjectB = {name, type, valuemap}. If attribute information B is a color attribute, and the corresponding RGB value is [135, 206, 250], then valuemap = [[0, 135, 255], [0, 206, 250], [0, 250, 255]].

[0076] It should be noted that if the attribute information is not an array type, the valuemap is empty, and the attribute value of the attribute information is stored in the value field.

[0077] In this embodiment, as an optional implementation, in step S130, in response to the attribute display instruction of the target control, a field object is obtained from the attribute object list container, including:

[0078] Based on the identifier of the target control, the property object list container is traversed and queried to obtain at least one field object of the target control.

[0079] Specifically, after converting the target control's attribute information into field objects, the target control's field objects are stored in the attribute object list container based on the target control's identifier.

[0080] Upon receiving a property display instruction from the target control, the system iterates through the property object list container based on the target control's identifier to obtain the target control's field object.

[0081] In this embodiment, the target control is connected to the field objects in the property object list container by the identifier of the target control. When it is necessary to respond to the property display command of the target control, the field object of the target control can be quickly queried, which improves the response speed of the property display command to a certain extent.

[0082] As an optional implementation, the identifier of the target control is the control name of the target control.

[0083] Specifically, the identifier of a target control is its control name. For example, the control name of target control 1 is target control 1. Searching for [target control 1] in the property object list container yields the field objects of target control 1, which can be represented as target control 1 = [FieldObjectA, FieldObjectB, FieldObjectC]. Target control 1 includes property information A, property information B, and property information C. FieldObjectA represents the field object of property information A, FieldObjectB represents the field object of property information B, and FieldObjectC represents the field object of property information C.

[0084] In this embodiment, as an optional implementation method, such as Figure 3 As shown, in step S140, based on the matching result between the data type of the field object and the data type of each sub-template in the preset general template, each sub-template is used to display each attribute information, including the following steps S310 to S320.

[0085] S310, retrieve the attribute values ​​stored in each field object.

[0086] S320: Based on the matching results, assign the attribute values ​​to the corresponding sub-templates and display the attribute bar obtained after the assignment.

[0087] After matching the corresponding sub-template based on the data type of the field object, the attribute values ​​stored in each field object are obtained, and the corresponding attribute values ​​are assigned and displayed in the corresponding positions of the sub-template, thus obtaining a sub-template that displays the attribute information.

[0088] The corresponding sub-template can be matched based on the data type of the field object.

[0089] In this embodiment, by obtaining the attribute values ​​stored in each field object and assigning the attribute values ​​to the corresponding positions in the sub-template, the attribute bar can clearly and intuitively display all the attribute information of the target control, which improves the display effect of the attribute information to a certain extent.

[0090] Figure 4 The diagram illustrates the attribute information displayed in the sub-templates for various data types.

[0091] like Figure 4 As shown, sub-template 41 represents the display style of attribute information with numeric data type. The left column of sub-template 41 displays the attribute name, and the right column of sub-template 42 displays the attribute value. The attribute name of this attribute information is [serial number], and the corresponding attribute value is 35397.

[0092] Sub-template 42 represents the display style for attribute information with a character data type. The left column of sub-template 42 displays the attribute name, and the right column displays the attribute value. The attribute name for this attribute information is [Name], and the corresponding attribute value is SceneModelObject.

[0093] Sub-template 43 represents the display style of Boolean attribute information. The left column of sub-template 43 displays the attribute name, and the right column of sub-template 43 displays the attribute value. The attribute name of this attribute information is [Enabled], and the corresponding attribute value is represented as "Yes", with a binary value of 1.

[0094] Sub-template 44 represents the display style of array-type attribute information. The left column of the first row of sub-template 44 displays the attribute name, and the right column of the first row displays the result. The left column of the second to fourth rows of sub-template 44 displays the name of each array element, and the right column of the second to fourth rows displays the value of each array element. The attribute name of this attribute information is position, and the corresponding attribute value is (9500, 6420, 13300). The data type of this attribute information is array type, and the attribute value of each array element is displayed below, for example, the X coordinate is 9500.00.

[0095] As an optional implementation, in step S320, the attribute bar obtained after the assignment is displayed, including:

[0096] The attribute bar is displayed by combining the sub-templates according to their order of arrangement in the general template.

[0097] Specifically, the order in which the sub-templates are arranged in the general template is determined, and the sub-templates are combined and displayed to obtain the attribute bar.

[0098] The properties bar contains all the property information of the target control. The property information of each data type is displayed in the corresponding sub-template, and the sub-templates are arranged in order.

[0099] In this embodiment, the attribute information of the corresponding data type is displayed through sub-templates. The attribute bar is obtained by arranging the sub-templates in order. The attribute bar can intuitively display all the attribute information of the target control. Each sub-template is based on a general template, which simplifies the display style of attribute information to a certain extent and optimizes the efficiency of the attribute display process of the target control.

[0100] Figure 5 A schematic diagram of the property bar of target control 1 is shown.

[0101] The target control 1 includes attribute information BASE, attribute information POS, and attribute information CubeBorder.

[0102] The attribute information bar 51 shows the position of the attribute information BASE in the attribute bar. The attribute information BASE includes the serial number attribute, the name attribute, and the Enabled attribute. The data type of the serial number attribute is numeric, and the attribute value of the serial number attribute is 35397. The data type of the name attribute is character, and the attribute value of the name attribute is SceneModelObject. The Enabled attribute is boolean, and the attribute value is represented as 1 in binary, which is shown as [Yes] in the figure.

[0103] The attribute information bar 52 shows the position of the attribute information POS in the attribute bar. The attribute information POS includes a position attribute. The data type of the position attribute is data type. The value of the entire position attribute is represented by an array, and the attribute value corresponding to each array element is displayed separately.

[0104] The attribute information bar 53 shows the position of the attribute information CubeBorderColor in the attribute bar. The attribute information CubeBorderColor includes a color attribute. The attribute name of this color attribute is CubeBorderColor, and the corresponding attribute value is [135,206,250].

[0105] It should be noted that, Figure 5 This is merely an illustrative example and should not be construed as limiting the number of attribute information contained in each target control or the number of attributes included in each attribute information in the embodiments of this application.

[0106] Figure 6 A schematic diagram showing the relationship between the various components in the embodiments of this application is provided.

[0107] The target control A61 contains the following properties: property A611, property B613, and property C615. The target control B62 includes property D621. The data types of these properties can be character, boolean, numeric, or array, etc.

[0108] Taking the implementation process of target control A61 as an example, the attribute information of target control A61 is converted into field object A63, and field object A63 is stored in attribute object list container 60. In response to the attribute display instruction of target control A61, the field object A63 of target control A61 is queried in attribute object list container 60, and the corresponding sub-template is matched in general template 65 according to the data type in field object A63.

[0109] For example, if the data type of property A611 in the target control A61 is data type, and the corresponding sub-template is sub-template A651, then the property information of property A611 in the target control A61 will be displayed through sub-template A651.

[0110] It should be noted that the implementation process of target control B62 is the same as that of target control A61, and will not be repeated here.

[0111] Figure 7 A schematic block diagram of the control attribute display device provided in an embodiment of this application is shown. Figure 7 As shown, it includes:

[0112] The field conversion module 71 is used to obtain the attribute information of the target control and convert the attribute information into the corresponding field object.

[0113] Storage module 72 is used to store field objects into an array container to obtain a list container of attribute objects.

[0114] The field object retrieval module 73 is used to retrieve field objects from the property object list container in response to the property display instructions of the target control.

[0115] The attribute display module 74 is used to display attribute information using each sub-template based on the matching result between the data type of the field object and the data type of each sub-template in the preset general template.

[0116] In one embodiment of this application, the field conversion module 71 includes:

[0117] Retrieve the field object name, data type, and attribute value of each attribute.

[0118] Based on the preset data storage format for the data type, the attribute value is stored in the corresponding field object name to obtain the corresponding field object.

[0119] In one embodiment of this application, the field object acquisition module 73 includes:

[0120] Based on the identifier of the target control, the property object list container is traversed and queried to obtain at least one field object of the target control.

[0121] In one embodiment of this application, the attribute display module 74 includes:

[0122] Retrieve the attribute values ​​stored in each field object.

[0123] Based on the matching results, the attribute values ​​are assigned to the corresponding sub-templates, and the attribute bar obtained after the assignment is displayed.

[0124] Figure 8 An electronic device 80 according to an embodiment of this application is shown. Figure 8 The electronic device 80 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0125] like Figure 8 As shown, the electronic device 80 is presented in the form of a general-purpose computing device. The components of the electronic device 80 may include, but are not limited to: at least one processing unit 810, at least one storage unit 820, and a bus 830 connecting different system components (including storage unit 820 and processing unit 810).

[0126] The storage unit stores program code, which can be executed by the processing unit 810 to perform the steps described in the explanatory section of this specification, according to various exemplary embodiments of the present application. For example, the processing unit 810 can perform actions such as... Figure 1 The steps shown are as follows.

[0127] Storage unit 820 may include a readable medium in the form of a volatile storage unit, such as random access memory (RAM) 8201 and / or cache memory 8202, and may further include a read-only memory (ROM) 8203.

[0128] The storage unit 820 may also include a program / utility 8204 having a set (at least one) of program modules 8205, including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0129] Bus 830 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0130] Electronic device 80 can also communicate with one or more external devices 900 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with electronic device 80, and / or with any device that enables electronic device 80 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 850. Input / output (I / O) interface 850 is connected to display unit 840. Furthermore, electronic device 80 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 860. As shown, network adapter 860 communicates with other modules of electronic device 80 via bus 830. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 80, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0131] Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, terminal device, etc.) to execute the control attribute display method according to the embodiments of this application.

[0132] In one embodiment of this application, a computer-readable storage medium is provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed by the processor of a computer, the computer executes the above-described control attribute display method.

[0133] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such transmitted data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0134] In one embodiment of this application, a program product for implementing the above-described control property display method is provided. The program product may employ any combination of one or more readable media.

[0135] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0136] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to the embodiments of this application, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0137] Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, touch terminal, or network device, etc.) to execute the method according to the embodiments of this application.

[0138] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein.

[0139] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for displaying control properties, characterized in that, include: The system acquires the attribute information of the target control and converts it into corresponding field objects. The attribute information includes the attribute name, data type, and attribute value. The field objects store the data type and attribute value of the attribute information, and the field object names are used to distinguish different attribute information. The number of field objects is the same as the number of attribute information. VALUEMAP is designed as the default data storage format for attribute information with array data type, and is used to store attribute values. The field objects are stored in an array container to obtain an attribute object list container; wherein, the attribute object list container stores all field objects of each target control on a per-target-control basis; In response to the property display instruction of the target control, the field object is obtained from the property object list container; Based on the matching result between the data type of the field object and the data types of each sub-template in the preset general template, the attribute information is displayed using each sub-template, wherein the general template includes sub-templates for different types of field objects; wherein, Obtain the attribute values ​​stored in each field object; assign the attribute values ​​to the corresponding sub-templates according to the matching results, and display the attribute bar obtained after assignment; combine and display the attribute bar according to the arrangement order of each sub-template in the general template.

2. The control property display method according to claim 1, characterized in that, The step of obtaining the attribute information of the target control and converting the attribute information into corresponding field objects includes: Obtain the field object name, data type, and attribute value of each attribute information; Based on the preset data storage format of the data type, the attribute value is stored in the corresponding field object name to obtain the corresponding field object.

3. The control property display method according to claim 1, characterized in that, The step of retrieving the field object from the attribute object list container in response to the attribute display instruction of the target control includes: Based on the identifier of the target control, the property object list container is traversed and queried to obtain at least one field object of the target control.

4. The control attribute display method according to claim 3, characterized in that, The identifier of the target control is the control name of the target control.

5. A control property display device, characterized in that, include: The field conversion module is used to obtain the attribute information of the target control and convert the attribute information into corresponding field objects. The attribute information includes the attribute name, data type, and attribute value. The field object stores the data type and attribute value of the attribute information, and the field object name is used to distinguish different attribute information. The number of field objects is equal to the number of attribute information. VALUEMAP is designed as the default data storage format for attribute information with array data type, and is used to store attribute values. The storage module is used to store the field objects into an array container to obtain an attribute object list container; wherein, the attribute object list container stores all field objects of each target control on a per-target-control basis; The field object acquisition module is used to retrieve the field object from the attribute object list container in response to the attribute display instruction of the target control; The attribute display module is used to display the attribute information using the sub-templates based on the matching result between the data type of the field object and the data type of each sub-template in the preset general template. The general template includes sub-templates for different types of field objects. Specifically, it obtains the attribute values ​​stored in each field object; assigns the attribute values ​​to the corresponding sub-templates according to the matching result, and displays the attribute bar obtained after assignment; and combines and displays the attribute bar according to the arrangement order of the sub-templates in the general template.

6. An electronic device, characterized in that, include: processor; as well as Memory for storing the executable instructions of the processor; The processor is configured to cause the electronic device to perform the control attribute display method according to any one of claims 1 to 4 by executing the executable instructions.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the control attribute display method according to any one of claims 1 to 4.

Images