Changes for page 09 Lua Editor

Last modified by Nhu Nguyen on 2025/03/09 17:22

From 4.10 to 4.9 From 6.1 to 5.1

From version 5.1

edited by Stone Wu
on 2022/08/08 10:34

Change comment: There is no comment for this version

To version 4.10

edited by Hunter
on 2022/07/29 15:01

Change comment: Update document after refactoring.

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.Stone
++XWiki.Hunter

Content

@@ -14,22 +14,24 @@
  (% style="text-align:center" %)
  [[image:HMI Lua Editor user manual_html_34da990820a7a4e5.png||height="208" width="400" class="img-thumbnail"]]
--== Script file area ==
++== **Script File Area** ==
  The script file area is located on the left side, named after the Lua, It will be referred to as the Lua node hereinafter.
  **Lua Node**
--* 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);
--* 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;
++~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);
--**✎Note: **
++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;
--* There is no script file for the newly created project. Following two new files will automatically generate.
--* Script_BG.lua: is the global background script file, which includes initialization and timing functions
--* Script_Screen.lua: is a screen script file, and each screen can have initialization, timing, and close functions
--* 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.
++**✎Note: **There is no script file for the newly created project. Following two new files will automatically generate.
++Script_BG.lua: is the global background script file, which includes initialization and timing functions
++
++Script_Screen.lua: is a screen script file, and each screen can have initialization, timing, and close functions
++
++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.
++
  **Lua Child Node**
  After creating a new file, expand the Lua node to display several script files. The following is referred to as child nodes.
@@ -37,26 +37,31 @@
  (% style="text-align:center" %)
  [[image:HMI Lua Editor user manual_html_fc10128583a230da.png||height="143" width="200" class="img-thumbnail"]]
--* Child node color description:
--* Red: encrypted file
--* Yellow: read-only file
--* Green: existed file or refresh the list to turn white to green
--* White: The newly created file, and the project will turn green after refreshing, protecting or reopening the project
++Child node color description:
--**Delete:** right-click the child node to delete. The deleted node will be placed in the recycle bin.
++Red: encrypted file
--**Rename: **right-click child node to rename.
++Yellow: read-only file
--**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).
++Green: existed file or refresh the list to turn white to green
--* Encryption mode: When this mode is turned on, you need to verify the password to view and edit.
--* Read-only mode: This mode is opened without verifying the password, if you want to edit, you must first release the protection
++White: The newly created file, and the project will turn green after refreshing, protecting or reopening the project
--**Unprotect:** Right-click on the child node, select Unprotect, enter the password to release.
++**(1) Delete:** right-click the child node to delete. The deleted node will be placed in the recycle bin.
++**(2)** **Rename: **right-click child node to rename.
++
++**(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).
++
++Encryption mode: When this mode is turned on, you need to verify the password to view and edit.
++
++Read-only mode: This mode is opened without verifying the password, if you want to edit, you must first release the protection
++
++**(4) Unprotect:** Right-click on the child node, select Unprotect, enter the password to release.
++
  **✎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.
--== Script editor ==
++== **Script Editor** ==
  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.
@@ -73,14 +73,20 @@
  **Editor Area**
--* **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
--* **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.
--* **Automatic indentation: **The tab key can add 4 spaces
--* **Calling prompt:** only available for Lua interface functions
--* **Hovering hint:** for example the mouse stays near the o letter position of demo() , it will display the prototype of the function
--* **(6)** **Shortcut keys:** In order to facilitate users, various shortcut keys have been added. Detailed description: Configure Lua shortcut keys.doc
--* **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.
++**(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
++**(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.
++
++**(3) Automatic indentation: **The tab key can add 4 spaces
++
++**(4) Calling prompt:** only available for Lua interface functions
++
++**(5) Hovering hint:** for example the mouse stays near the o letter position of demo() , it will display the prototype of the function
++
++**(6)** **Shortcut keys:** In order to facilitate users, various shortcut keys have been added. Detailed description: Configure Lua shortcut keys.doc
++
++**(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.
++
  **Output Area**
  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.
@@ -92,7 +92,7 @@
  (% style="text-align:center" %)
  [[image:HMI Lua Editor user manual_html_a9a41fb25f413fec.png||height="317" width="150" class="img-thumbnail"]]
--== How to use Lua button ==
++== **How to Use Lua Button** ==
  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.
@@ -101,18 +101,19 @@
  Click Lua object will trigger two actions, that is, rising and falling scripts;
--* **Falling script**: after the button is pressed, the code chunk of the area is executed;
--* **Rising script**: after the button is raised, the code chunk in the area is executed;
--* **Timing script**: periodically execute the code.
++**(1)** **Falling script**: after the button is pressed, the code chunk of the area is executed;
--**✎Note: **
++**(2) Rising script**: after the button is raised, the code chunk in the area is executed;
--* 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.
--* 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.
++**(3)** **Timing script**: periodically execute the code.
++**✎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.
++
++**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.
++
  = **Platform** =
--== File header identification ==
++== **File Header Identification** ==
  Any new file will automatically generate a line of code, as shown below:
@@ -126,52 +126,62 @@
  (% style="text-align:center" %)
  [[image:HMI Lua Editor user manual_html_52fb935bcc76d7ad.png||height="113" width="203" class="img-thumbnail"]]
--* **_limits: **Fixed format, cannot be modified
--* **Description**：
--* **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.
--* **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.
++**_limits**：Fixed format, cannot be modified
++**Description**：
++
++**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.
++
++**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.
++
  **✎Note: **If you rename the file manually, you must modify the limits in the file accordingly, otherwise the script file will not take effect.
--== Built-In script file ==
++== **Built-In Script File** ==
  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.
--**Script_BG.lua** is a global background script file, which includes initialization and polling functions
++~1. **Script_BG.lua** is a global background script file, which includes initialization and polling functions
  (% style="text-align:center" %)
  [[image:HMI Lua Editor user manual_html_5eb1ad5776f18955.png||height="148" width="200" class="img-thumbnail"]]
--* we_bg_init(): global initialization, that is, execute once when power on.
--* we_bg_poll(): Global polling, that is, the cycle is repeated after power on.
++we_bg_init(): global initialization, that is, execute once when power on.
++we_bg_poll()：Global polling, that is, the cycle is repeated after power on.
++
  Script_Screen.lua is a screen script file, and each screen has an initialization, polling, and closing functions
  (% style="text-align:center" %)
  [[image:HMI Lua Editor user manual_html_e6807eb0da0eedd4.png||height="231" width="300" class="img-thumbnail"]]
--* we_scr_init_0(): execute this function when screen 0 is initialized
--* we_scr_poll_0(): when in picture 0, the function is executed repeatedly
--* we_scr_close_0(): execute this function when screen 0 is closed
++we_scr_init_0(): execute this function when screen 0 is initialized
++we_scr_poll_0(): when in picture 0, the function is executed repeatedly
++
++we_scr_close_0(): execute this function when screen 0 is closed
++
  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
  **✎Note: **The above function has a fixed name. If it is modified, it will not cause crash, but the function can be found.
--**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.
++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.
--== Script type (operating mechanism) ==
++== **Script Type (Operating Mechanism)** ==
  There are two types of scripts:
--* Active: script automatically executed by HMI
--* Passive: Script executed only after user trigger
++Active: script automatically executed by HMI
++Passive: Script executed only after user trigger
++
  The active types includes:
--* Global _bg_ related functions in Script_BG.lua
--* Screen _scr_ related functions in Script_Screen.lua
++Global _bg_ related functions in Script_BG.lua
++Screen _scr_ related functions in Script_Screen.lua
++
  Polling script in Lua object
--The passive type scripts include: The rising and falling script in Lua object.
++The passive type scripts include:
++
++The rising and falling script in Lua object.

Changes for page 09 Lua Editor

Summary

Details

Navigation

Table of Contents