Changes for page 09 Lua Editor
Last modified by Nhu Nguyen on 2025/03/09 17:22
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,1 +1,1 @@ 1 -PIStudio.WebHome 1 +PIStudio.1 User Manual.WebHome - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Jim1 +XWiki.Hunter - Content
-
... ... @@ -14,25 +14,24 @@ 14 14 (% style="text-align:center" %) 15 15 [[image:HMI Lua Editor user manual_html_34da990820a7a4e5.png||height="208" width="400" class="img-thumbnail"]] 16 16 17 -== Script filearea ==17 +== **Script File Area** == 18 18 19 19 The script file area is located on the left side, named after the Lua, It will be referred to as the Lua node hereinafter. 20 20 21 21 **Lua Node** 22 22 23 -* Create new file: right-click the Lua node to select new file, and enter a name in pop-up window, (the name starts with an underscore or letter); 24 -* Refresh list: the file edited (new/deleted/renamed) by the user externally, the configuration is not refreshed. In this case this function needs to be used to synchronize changes; 23 +~1. Create new file: right-click the Lua node to select new file, and enter a name in pop-up window, (the name starts with an underscore or letter); 25 25 26 -(% class="box infomessage" %) 27 -((( 28 -**✎Note: ** 25 +2.Refresh list: the file edited (new/deleted/renamed) by the user externally, the configuration is not refreshed. In this case this function needs to be used to synchronize changes; 29 29 30 -* There is no script file for the newly created project. Following two new files will automatically generate. 31 -* Script_BG.lua: is the global background script file, which includes initialization and timing functions 32 -* Script_Screen.lua: is a screen script file, and each screen can have initialization, timing, and close functions 33 -* At any time, as long as there is a new operation, the software will judge whether the above two files exist, and which one is missing will be automatically filled. 34 -))) 27 +**✎Note: **There is no script file for the newly created project. Following two new files will automatically generate. 35 35 29 +Script_BG.lua: is the global background script file, which includes initialization and timing functions 30 + 31 +Script_Screen.lua: is a screen script file, and each screen can have initialization, timing, and close functions 32 + 33 +At any time, as long as there is a new operation, the software will judge whether the above two files exist, and which one is missing will be automatically filled. 34 + 36 36 **Lua Child Node** 37 37 38 38 After creating a new file, expand the Lua node to display several script files. The following is referred to as child nodes. ... ... @@ -40,29 +40,31 @@ 40 40 (% style="text-align:center" %) 41 41 [[image:HMI Lua Editor user manual_html_fc10128583a230da.png||height="143" width="200" class="img-thumbnail"]] 42 42 43 -* Child node color description: 44 -* Red: encrypted file 45 -* Yellow: read-only file 46 -* Green: existed file or refresh the list to turn white to green 47 -* White: The newly created file, and the project will turn green after refreshing, protecting or reopening the project 42 +Child node color description: 48 48 49 - **Delete:**right-click thechildnodeto delete. Thedeletednode will beplaced in the recycle bin.44 +Red: encrypted file 50 50 51 - **Rename:**right-clickchild nodeto rename.46 +Yellow: read-only file 52 52 53 - **Encryption:**right-click thechild node,selectncryption.Eachfilecanbesetwithan independentpassword(length1-6,onlyuppercase/lowercaselettersand numbers areaccepted).48 +Green: existed file or refresh the list to turn white to green 54 54 55 -* Encryption mode: When this mode is turned on, you need to verify the password to view and edit. 56 -* Read-only mode: This mode is opened without verifying the password, if you want to edit, you must first release the protection 50 +White: The newly created file, and the project will turn green after refreshing, protecting or reopening the project 57 57 58 -** Unprotect:**Right-clickonthe child node,selectUnprotect,enterthe password torelease.52 +**(1) Delete:** right-click the child node to delete. The deleted node will be placed in the recycle bin. 59 59 60 -(% class="box infomessage" %) 61 -((( 54 +**(2)** **Rename: **right-click child node to rename. 55 + 56 +**(3) Encryption:** right-click the child node, select encryption. Each file can be set with an independent password(length 1-6, only uppercase/lowercase letters and numbers are accepted). 57 + 58 +Encryption mode: When this mode is turned on, you need to verify the password to view and edit. 59 + 60 +Read-only mode: This mode is opened without verifying the password, if you want to edit, you must first release the protection 61 + 62 +**(4) Unprotect:** Right-click on the child node, select Unprotect, enter the password to release. 63 + 62 62 **✎Note: **If user forgets the password, the script file can never be recovered, the software will not storage any passwords, developers need to keep the password by themselves carefully. 63 -))) 64 64 65 -== Script editor ==66 +== **Script Editor** == 66 66 67 67 The script editor is divided into three blocks: the upper part is the toolbar, the middle part is the editing area, and the lower part is the output area. 68 68 ... ... @@ -79,14 +79,20 @@ 79 79 80 80 **Editor Area** 81 81 82 -* **Highlight color:** Lua's built-in keywords has a different color with the Lua interface functions. The functions written by users will not be highlighted 83 -* **Auto-complete:** Lua function auto-complete prompts, Lua chunk auto-complete (such as if xx then end), also supports the completion of all the words in this script file. Use the Enter key to select candidates words, use the Tab key to turn off automatic completion. 84 -* **Automatic indentation: **The tab key can add 4 spaces 85 -* **Calling prompt:** only available for Lua interface functions 86 -* **Hovering hint:** for example the mouse stays near the o letter position of demo() , it will display the prototype of the function 87 -* **(6)** **Shortcut keys:** In order to facilitate users, various shortcut keys have been added. Detailed description: Configure Lua shortcut keys.doc 88 -* **Interface document: **The scripts listed in the interface document will be distinguished by the highlighted color in the editing area. You can check whether the interface is called incorrectly by judging the color change. Detailed description: Lua interface manual. 83 +**(1) Highlight color:** Lua's built-in keywords has a different color with the Lua interface functions. The functions written by users will not be highlighted 89 89 85 +**(2)** **Auto-complete:** Lua function auto-complete prompts, Lua chunk auto-complete (such as if xx then end), also supports the completion of all the words in this script file. Use the Enter key to select candidates words, use the Tab key to turn off automatic completion. 86 + 87 +**(3) Automatic indentation: **The tab key can add 4 spaces 88 + 89 +**(4) Calling prompt:** only available for Lua interface functions 90 + 91 +**(5) Hovering hint:** for example the mouse stays near the o letter position of demo() , it will display the prototype of the function 92 + 93 +**(6)** **Shortcut keys:** In order to facilitate users, various shortcut keys have been added. Detailed description: Configure Lua shortcut keys.doc 94 + 95 +**(7)** **Interface document: **The scripts listed in the interface document will be distinguished by the highlighted color in the editing area. You can check whether the interface is called incorrectly by judging the color change. Detailed description: Lua interface manual. 96 + 90 90 **Output Area** 91 91 92 92 Click the syntax button in the toolbar to perform a grammar check. If the script is written incorrectly, it will be displayed in the window. Double-click the prompt to locate the "near" line of the error. ... ... @@ -98,7 +98,7 @@ 98 98 (% style="text-align:center" %) 99 99 [[image:HMI Lua Editor user manual_html_a9a41fb25f413fec.png||height="317" width="150" class="img-thumbnail"]] 100 100 101 -== How to use Luabutton ==108 +== **How to Use Lua Button** == 102 102 103 103 Find the custom part->LuaScript on the right side, drag and draw to generate a part. Double-click the part to pop up a dialog box. 104 104 ... ... @@ -107,18 +107,19 @@ 107 107 108 108 Click Lua object will trigger two actions, that is, rising and falling scripts; 109 109 110 -* **Falling script**: after the button is pressed, the code chunk of the area is executed; 111 -* **Rising script**: after the button is raised, the code chunk in the area is executed; 112 -* **Timing script**: periodically execute the code. 117 +**(1)** **Falling script**: after the button is pressed, the code chunk of the area is executed; 113 113 114 -** ✎Note:**119 +**(2) Rising script**: after the button is raised, the code chunk in the area is executed; 115 115 116 -* The timing script is not commonly used because it is similar to the screen background script function. It is not recommended to write and call function here. It should be written in Script_Screen.lua, which is convenient for editing, searching, and replacing operations. 117 -* It is not allowed to write endless loops or call functions that will loop enlessly in the widget. Once used, the entire screen will be stuck, and any buttons will no longer be used. We have to restart the screen to restore. 121 +**(3)** **Timing script**: periodically execute the code. 118 118 123 +**✎Note: **The timing script is not commonly used because it is similar to the screen background script function. It is not recommended to write and call function here. It should be written in Script_Screen.lua, which is convenient for editing, searching, and replacing operations. 124 + 125 +**Warning:** It is not allowed to write endless loops or call functions that will loop enlessly in the widget. Once used, the entire screen will be stuck, and any buttons will no longer be used. We have to restart the screen to restore. 126 + 119 119 = **Platform** = 120 120 121 -== File headeridentification ==129 +== **File Header Identification** == 122 122 123 123 Any new file will automatically generate a line of code, as shown below: 124 124 ... ... @@ -132,52 +132,62 @@ 132 132 (% style="text-align:center" %) 133 133 [[image:HMI Lua Editor user manual_html_52fb935bcc76d7ad.png||height="113" width="203" class="img-thumbnail"]] 134 134 135 -* **_limits: **Fixed format, cannot be modified 136 -* **Description**: 137 -* **Tens digit=1**: indicates that the function or global variable defined in this file can be used in the background code file (Script_BG.lua). If it is 0, it is not available. 138 -* **Ones digit=1**: indicates that the functions or global variables defined in this file can be used in the screen code file (Script_Screen.lua) or LuaScript components. If it is 0, it is not available. 143 +**_limits**:Fixed format, cannot be modified 139 139 145 +**Description**: 146 + 147 +**Tens digit=1**:indicates that the function or global variable defined in this file can be used in the background code file (Script_BG.lua). If it is 0, it is not available. 148 + 149 +**Ones digit=1**:indicates that the functions or global variables defined in this file can be used in the screen code file (Script_Screen.lua) or LuaScript components. If it is 0, it is not available. 150 + 140 140 **✎Note: **If you rename the file manually, you must modify the limits in the file accordingly, otherwise the script file will not take effect. 141 141 142 -== Built-In scriptfile ==153 +== **Built-In Script File** == 143 143 144 144 As mentioned above, the first new build will automatically generate two script files. These two files cannot be deleted and renamed, which will be explained in detail here. 145 145 146 -**Script_BG.lua** is a global background script file, which includes initialization and polling functions 157 +~1. **Script_BG.lua** is a global background script file, which includes initialization and polling functions 147 147 148 148 (% style="text-align:center" %) 149 149 [[image:HMI Lua Editor user manual_html_5eb1ad5776f18955.png||height="148" width="200" class="img-thumbnail"]] 150 150 151 -* we_bg_init(): global initialization, that is, execute once when power on. 152 -* we_bg_poll(): Global polling, that is, the cycle is repeated after power on. 162 +we_bg_init(): global initialization, that is, execute once when power on. 153 153 164 +we_bg_poll():Global polling, that is, the cycle is repeated after power on. 165 + 154 154 Script_Screen.lua is a screen script file, and each screen has an initialization, polling, and closing functions 155 155 156 156 (% style="text-align:center" %) 157 157 [[image:HMI Lua Editor user manual_html_e6807eb0da0eedd4.png||height="231" width="300" class="img-thumbnail"]] 158 158 159 -* we_scr_init_0(): execute this function when screen 0 is initialized 160 -* we_scr_poll_0(): when in picture 0, the function is executed repeatedly 161 -* we_scr_close_0(): execute this function when screen 0 is closed 171 +we_scr_init_0(): execute this function when screen 0 is initialized 162 162 173 +we_scr_poll_0(): when in picture 0, the function is executed repeatedly 174 + 175 +we_scr_close_0(): execute this function when screen 0 is closed 176 + 163 163 The above is the initialization function of screen 0. For screen 100, you can replace 0 with 100. You can add your own function: function we_scr_init_100() end 164 164 165 165 **✎Note: **The above function has a fixed name. If it is modified, it will not cause crash, but the function can be found. 166 166 167 - **Example:**After the screen 0 initialization function is changed to we_scR_init_0(), the script will not be executed when screen 0 is initialized, and then no script will be executed, and nothing will be done because the "we_scr_init_0" function cannot be found.181 +Example: After the screen 0 initialization function is changed to we_scR_init_0(), the script will not be executed when screen 0 is initialized, and then no script will be executed, and nothing will be done because the "we_scr_init_0" function cannot be found. 168 168 169 -== Script type (operatingmechanism) ==183 +== **Script Type (Operating Mechanism)** == 170 170 171 171 There are two types of scripts: 172 172 173 -* Active: script automatically executed by HMI 174 -* Passive: Script executed only after user trigger 187 +Active: script automatically executed by HMI 175 175 189 +Passive: Script executed only after user trigger 190 + 176 176 The active types includes: 177 177 178 -* Global _bg_ related functions in Script_BG.lua 179 -* Screen _scr_ related functions in Script_Screen.lua 193 +Global _bg_ related functions in Script_BG.lua 180 180 195 +Screen _scr_ related functions in Script_Screen.lua 196 + 181 181 Polling script in Lua object 182 182 183 -The passive type scripts include: The rising and falling script in Lua object. 199 +The passive type scripts include: 200 + 201 +The rising and falling script in Lua object.