Last modified by Dilisi S on 2025/02/26 19:24
<
From version < 123.1 >
edited by Dilisi S
on 2024/12/24 04:36
To version < 105.1 >
edited by BoYang Xie
on 2024/11/22 15:47
>
Change comment: Uploaded new attachment "image-20241122154745-48.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.pradeeka
1 +XWiki.xieby
Content
... ... @@ -21,20 +21,20 @@
21 21  
22 22  = 1.  Introduction =
23 23  
24 -== 1.1  What is the LTS5 LoRa HMI Touch Screen? ==
24 +== 1.1  What is LTS5 LoRa HMI touch screen ==
25 25  
26 26  
27 -The LTS5 is a (% style="color:blue" %)**LoRa / LoRaWAN HMI Touch Screen**(%%) designed for displaying information in IoT projects. It features a **5.0-inch HMI touch screen** and supports **Wi-Fi**, **Bluetooth**, and **LoRa** wireless protocols.
27 +LTS5 is a (% style="color:blue" %)LoRa / LoRaWAN HMI Touch Screen(%%) designed for display purpose of IoT project. It have a 5.0" HMI touch screen, and support WiFi, Bluetooch, LoRa wireless protocol.
28 28  
29 -The LTS5 is an open-source software project powered by an **ESP32 MCU** and a **Dragino LA66 LoRa** module. The extensive development resources available for ESP32 can significantly reduce development time.
29 +LTS5 is an Open Source software project. The MCU is ESP32 and Dragino LA66 LoRa module. There are lots of development source for ESP32 which can greatly reduce the development time.
30 30  
31 -The LTS5's HMI touch screen supports **drag-and-drop** design, allowing developers to use SquareLine to easily customize the display UI for various applications.
31 +The HMI touch screen of LTS5 supports drap & drop design. Developer can use SquareLine to easily customize the display UI for different application.
32 32  
33 -The LA66 LoRa module can be programmed to support either private LoRa protocols or the LoRaWAN protocol.
33 +LTS5 use LA66 LoRa module, this module can be program to support private LoRa protocol or LoRaWAN protocol.
34 34  
35 +
35 35  == 1.2  Features ==
36 36  
37 -
38 38  * ESP32-WROOM MCU: 8MB RAM & 16MB ROM
39 39  * Dragino LA66 LoRa Module
40 40  * Support Private LoRa protocol or LoRaWAN protocol
... ... @@ -47,7 +47,7 @@
47 47  * 5V DC power
48 48  * IP Rating: IP52
49 49  
50 -== 1.3  Specifications ==
50 +== 1.3  Specification ==
51 51  
52 52  
53 53  **LoRa**:
... ... @@ -102,37 +102,28 @@
102 102  * Smart Cities
103 103  * Smart Factory
104 104  
105 -= 2.  Getting Started with 'Hello World' =
105 += 2.  Getting Started with Hello World =
106 106  
107 107  == 2.1  About this demo ==
108 108  
109 109  
110 -This getting started example demonstrates how to design and deploy a simple display UI for the LTS5 device. The example includes:
110 +In this Getting Started Example, we will show how to design a simple Display UI and upload it to LTS5. This UI has  a button , when user click the button. The Web UI will jump to a new page.
111 111  
112 -* Creating a basic UI with a single button.
113 -* Implementing functionality to navigate the Web UI to a new page when the button is clicked.
114 -* Uploading the UI to the LTS5 device.
115 115  
116 -By completing this demo, you will gain foundational knowledge for customizing the LTS5 interface and building more advanced IoT applications.
117 -
118 -
119 119  == 2.2  Install Software Running Environment ==
120 120  
115 +The ESP MCU can be developed using ESP-IDF, Arduino, or MicroPython. For this project, we utilize ESP-IDF for compilation and Visual Studio Code (VSCode) for editing.
121 121  
122 -The **ESP MCU** supports development with **ESP-IDF**, **Arduino**, or **MicroPython**. We use **ESP-IDF** for compilation and **Visual Studio Code (VS Code)** as the development environment for this project.
117 +=== 2.2.1 Install VSCode and ESP-IDF extension ===
123 123  
124 124  
125 -=== 2.2.1 Install VS Code and ESP-IDF extension ===
120 +Firstly, download and install VSCode for your computer's operating system from the official website: [[Download Visual Studio Code - Mac, Linux, Windows>>url:https://code.visualstudio.com/download]].
126 126  
122 +Next, you need to install the ESP-IDF extension within VSCode. The detailed operation steps are illustrated in image 1.
127 127  
128 -First, download and install **VS Code** for your operating system from the Visual Studio Code website: [[Visual Studio Code - Mac, Linux, Windows>>https://code.visualstudio.com/download]].
129 -
130 -Next, install the **ESP-IDF** extension within **VS Code**. Detailed steps for this process are shown in Image 1.
131 -
132 -
133 133  [[image:image-20240928110211-5.png||height="508" width="866"]]
134 134  
135 - Image 1: ESP-IDF extension install
126 + image 1 ESP-IDF extension install
136 136  
137 137  Links for reference: [[Install ESP32 ESP-IDF on Windows and Integrate with VS code (esp32tutorials.com)>>url:https://esp32tutorials.com/install-esp32-esp-idf-windows-integrate-vs-code/#:~~:text=In%20this%20tutorial,%20we%20will%20show%20you%20how%20to%20install]]
138 138  
... ... @@ -140,116 +140,72 @@
140 140  === 2.2.2 Install SquareLine Studio ===
141 141  
142 142  
143 -Download and install the latest version of [[SquareLine Studio>>https://squareline.io/downloads#lastRelease]] on your computer. It supports Windows, Linux, and Mac OS. The software version we are using here is 1.4.2.
134 +The version we are utilizing for this software is 1.4.2. You can download it from the official link: [[SquareLine Studio - Download the current version of SquareLine Studio>>url:https://squareline.io/downloads#lastRelease]].
144 144  
145 -[[image:squareline.io_downloads.png]]
136 +Please note that this software necessitates the registration of a license prior to usage, and various licenses come with distinct limitations. For instance, the free version imposes restrictions such as a limit of 1 component, 150 widgets, and 10 screens. However, for first-time downloads, you are granted unrestricted access for a period of 30 days without the need for immediate registration.
146 146  
147 147  
148 -After installation, you can use SquareLine Studio with a **PERSONAL license plan**. Click **LOG IN** and create a free account using your email address. Then activate your PERSONAL license plan for free. You don’t need to provide any credit card information. However, the PERSONAL license plan has the following limitations:
139 +== 2.3 Simple usage of SquareLine Studio and export UI code ==
149 149  
150 -* Max. 10 screens
151 -* Max. 150 widgets
152 -* Max. 5 global colors
153 -* Max. 2 themes
154 -* Max. 1 component
155 155  
156 -== 2.3 Simple usage of SquareLine Studio and exporting UI code ==
142 +After launching and logging in to this software, create a project as shown in the following image 2. The version of LVGL is 8.3.11.
157 157  
158 -
159 -After launching and logging into the software, create a new project as shown in Image 2.
160 -
161 -* Select the major **LVGL** version as **8.3**.
162 -* Select the **Desktop** tab.
163 -* Select  **Eclipse with  SDL for  development on PC**:
164 -* In the **PROJECT SETTINGS**, select **LVGL version** **8.3.11**
165 -* Select the **CREATE **button.
166 -
167 167  [[image:image-20240928103357-2.png||height="680" width="708"]]
168 168  
169 - Image 2: Creating a new SquareLine project
146 + image 2 create a SquareLine project
170 170  
148 +Next, we need to make some settings for this project. By clicking in the specified order on image 3, we can see the page as shown in image 4.
171 171  
172 -Next, you need to configure some settings for this project. By clicking in the specified order shown in Image 3, you will be directed to the page displayed in Image 4.
173 -
174 -* Select** File  -> Project Settings**
175 -
176 176  [[image:1727229582471-566.png]]
177 177  
178 - Image 3 accessing project settings
152 + image 3 project settings
179 179  
180 -
181 -In the PROJECT SETTINGS dialog box, configure/modify the project settings:
182 -
183 -* **UI Files Export Root**: Select a folder on your computer to store the UI files.
184 -* **LVGL Include Path**: Set this to **lvgl.h**
185 -* **Click on the APPLY CHANGES button.**
186 -
187 187  [[image:image-20240928105309-4.png||height="526" width="556"]]
188 188  
189 - Image 4 Configure/modify project settings
156 + image 4 modify project settings
190 190  
158 +Now we can start to use this software. Here are some usage information for this software.
191 191  
192 -Now you can start building the sample UI. Follow the steps below:
160 +**~1. add widget**
193 193  
162 +To add a widget, you should click a widget you want to add at the area entitled “Widgets”. In image , demonstrate a add process of label, button, and image 5.
194 194  
195 -=== Add widgets ===
196 -
197 -To add widgets navigate to the **Widgets** area, then click on the widgets you want to add. The selected widgets will be added to the screen. You can reposition the widgets in the screen area by clicking and dragging them.
198 -
199 -Add a Label, Button, and Image to the screen as shown in **Image 5**.
200 -
201 201  [[image:image-20240928111412-6.png||height="526" width="864"]]
202 202  
203 - Image 5: Add widgets
166 + image 5 add widgets
204 204  
205 -=== Modify widget properties ===
168 +**2. modify widget**
206 206  
207 -The area for modifying widgets is called the **Inspector** tab. The Inspector tab consists of four sections: **COMPONENT**, **<WIDGET>**, **STYLE SETTINGS**, and **EVENTS**, as shown in Image 6.
170 +The area for modifying widgets is called "Inspector". There are four parts in the "Inspector" tab. We use three of them more frequently, excluding "COMPONENT". The second part is aimed at adjusting the layout, size, position, alignment, flags, and states, etc. of widgets. The name of the second part indicates the type of widget it is representing, and in image 6, it is "BUTTON".
208 208  
209 -The second section allows you to adjust a widget's layout, size, position, alignment, flags, states, and more. When you select a widget on the screen, the name of this section changes to match the name of the selected widget.
210 -
211 211  [[image:1727485118799-984.png]]
212 212  
213 - Image 6: The button widget's "Inspector" tab
174 + image 6 the button widget's "Inspector" tab
214 214  
176 +Second part: "Layout" means a auto position-management for widgets contained in the parent widget. "Transform" includes size, position and align modification.
215 215  
216 -==== Changing the Button properties ====
217 -
218 -Click the Button.
219 -
220 -Under the "Layout" you can change the button's position and size.
221 -
222 222  [[image:1727485251053-655.png]]
223 223  
224 -Image 7: The button widget's "BUTTON" tab
180 +image 7 the button widget's "BUTTON" tab
225 225  
182 +Third part: It is an area of style setting.
226 226  
227 -Next, add a click event to the button. When the button is clicked, an event should trigger to change the current screen (Screen1) to a new screen (Screen2) with a fade effect and the transition from Screen1 to Screen2 should take 500ms.
184 +Fourth part: It is an area for adding events. In image 8, it is adding a click event to a button. If the button is clicked after the click event is added as shown in image 8, the current screen will fade into another specified screen, and the switching process will last 500ms.
228 228  
229 -* Click **ADD EVENT** button.
230 -* Select **CLICKED** under the Trigger.
231 -* Select **Screen2** from **Screen to**.
232 -* Select **FADE ON** from **Fade mode**.
233 -* Enter **500** in the **Speed** text box.
234 -* Finally, click **ADD** button.
235 -
236 236  [[image:1727485480434-713.png||height="395" width="290"]]
237 237  
238 - Image 8: Add an event for the button
188 + image 8 add event for button
239 239  
190 +**3. change label widget content**
240 240  
241 -==== Changing the label properties ====
192 +Modify the content in text as shown in image 9, the text content of label widget will be changed accordingly.
242 242  
243 -Click the label. Under the **Label** section, type "Click For Detail" in the **Text** textbox.
244 -
245 -
246 246  [[image:image-20240928090825-1.png||height="327" width="391"]]
247 247  
248 - Image 9:  Modify text of label widget
196 + image 9 modify text content of label widget
249 249  
198 +**4. Add image into project**
250 250  
251 -==== 4. Changing image properties ====
252 -
253 253  To use the image widget, you should first add an image to your project. The image format must be PNG, and its resolution should not exceed 800x480 pixels. There are two ways to add an image file. One way is to move your image into the folder "…/squareline project/assets/", as shown in image 10. The other way is to click the "ADD FILE INTO ASSETS" button, then select an image from your computer to import. After adding, you can see the image in the "assets" area in SquareLine Studio, as demonstrated in image 11.
254 254  
255 255  [[image:image-20240928113424-9.png||height="355" width="505"]]
... ... @@ -260,36 +260,29 @@
260 260  
261 261   image 11 use image widget in SquareLine Studio
262 262  
210 +**5. The relationship between widgets**
263 263  
264 -==== 5. The relationship between widgets ====
212 +There are two common relationships between widgets: one is parallel, the other is parent-child. The parallel relationship means that widgets' relative position is based on a collective object of reference. In parent-child relationship, the parts of the child object that are outside the boundaries of the parent object are not visible by default. Therefore, we need to adjust the position of the child object so that it falls within the range of the parent object, allowing it to be seen as illustrated in image 13.
265 265  
266 -Widgets commonly have two types of relationships: **parallel** and **parent-child**.
267 -
268 -* In a **parallel relationship**, widgets' positions are determined relative to a shared reference object.
269 -* In a **parent-child relationship**, any part of the child object outside the parent's boundaries is hidden by default. To make the child object fully visible, you must adjust its position to fit within the parent's range, as shown in Image 13.
270 -
271 271  [[image:1727486567182-334.png||height="318" width="278"]]
272 272  
216 +image 12 move label1 to make label1 widget be a child of button1 widget(1)
273 273  
274 -Move **Label1** to make it a child of **Button1**. See Image 13.
275 -
276 276  [[image:image-20240928112001-8.png||height="431" width="796"]]
277 277  
278 - Image 13: Move Label1 to make it a child of Button1.
220 + image 13 move label1 to make label1 widget be a child of button1 widget(2)
279 279  
222 +**6. Preview the final effect**
280 280  
281 -**6. Preview the screen**
224 +An advantage of this kind of software is that you can edit the UI with quick previews. In other words, it provides a way of combining graphical programming with simulation immediately.
282 282  
283 -You can test the result by clicking on the **PLAY** button. The screen will change into play mode. See Image 14.
284 -
285 285  [[image:1727487368023-281.png]]
286 286  
287 - Image 14: Simulating the project
228 + image 14 click on the triangle icon to start or end the simulation
288 288  
230 +For more detailed usage, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
289 289  
290 -For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
291 291  
292 -
293 293  == 2.4 Integrate UI Code to ESP-IDF Project ==
294 294  
295 295  
... ... @@ -351,53 +351,54 @@
351 351  
352 352  = 4. Example Project 2: LoRaWAN RS485 Alarm =
353 353  
294 +(% class="wikigeneratedid" %)
354 354  = 5.  The way to add a new panel to project =
355 355  
356 -**~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.**
297 +~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.
357 357  
358 358  [[image:image-20241121113445-1.png||height="584" width="934"]]
359 359  
360 360   image 5.1 a panel about water_leak
361 361  
362 -**2. Export the ui file.** You need  to adjust the export path first, then click "Export->Export UI Files". This step had been introduced before. Then you can get the ui files as shown in image 5.2.
303 +2. Export the ui file. You need  to adjust the export path first, then click "Export->Export UI Files". This step had been introduced before. Then you can get the ui files as shown in image 5.2.
363 363  
364 364  [[image:image-20241121141120-4.png||height="383" width="795"]]
365 365  
366 366   image 5.2 ui files exported
367 367  
368 -**3. Delete or rename some file.** Here are the steps:
309 +3. Delete or rename some file. Here are the steps:
369 369  
370 - Step1 Delete the 'components' directory.
371 - Step2 Delete 'filelist.txt'.
372 - Step3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
373 - Step4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
374 - Step5 Rename the 'screens' directory to 'styles'.
311 + 3.1 Delete the 'components' directory.
312 + 3.2 Delete 'filelist.txt'.
313 + 3.3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
314 + 3.4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
315 + 3.5 Rename the 'screens' directory to 'styles'.
375 375  
376 376  [[image:image-20241121151934-10.png||height="303" width="792"]]
377 377  
378 - image 5.3 rest file (1)
319 + image 5.3 rest file 1
379 379  
380 380  [[image:image-20241121142925-7.png||height="141" width="793"]]
381 381  
382 - image 5.4 rest file (2)
323 + image 5.4 rest file 2
383 383  
384 -**4. Open this project in vscode.**
325 +4. Open this project in vscode.
385 385  
386 386  5. Add file include path about water_leak in extra_lib/CMakeLists.txt as shown in image 5.5, 5.6, and its format is similar to the tem_hum or door.
387 387  
388 388  [[image:image-20241121181957-17.png||height="438" width="516"]]
389 389  
390 - image 5.5 extra_lib/CMakeLists.txt before add
331 + image 5.5 before add
391 391  
392 392  [[image:image-20241121182239-18.png||height="520" width="518"]]
393 393  
394 - image 5.6 extra_lib/CMakeLists.txt after add
335 + image 5.6 after add
395 395  
396 -**6. Modify header file include in fonts and images directory.** Open the fonts/ui_font_Font12.c file, as shown in image 5.7, then modify the '#include "../ui.h"' to '#include "../ui_water_leak.h"', the image 5.8 is the modified image. Other font file need to be modified in same way.
337 +6. Modify header file include in fonts and images directory. Open the fonts/ui_font_Font12.c file, as shown in image 5.7, then modify the '#include "../ui.h"' to '#include "../ui_water_leak.h"', the image 5.8 is the modified image. Other font file need to be modified in same way.
397 397  
398 398  [[image:image-20241121171629-11.png]]
399 399  
400 - image 5.7 before-modified font file
341 + image 5.7 before-modified font file
401 401  
402 402  [[image:image-20241121171901-12.png]]
403 403  
... ... @@ -413,183 +413,28 @@
413 413  
414 414   image 5.10 modified image file
415 415  
416 -**7. Modify the ui_water_leak/CMakeLists.txt.** Open this file, and modify it from image 5.11 to image 5.12.
357 +7. Modify the ui_water_leak/CMakeLists.txt. Open this file, and modify it from image 5.11 to image 5.12.
417 417  
418 418  [[image:image-20241121180030-15.png]]
419 419  
420 - image 5.11 ui_water_leak/CMakeLists.txt before modification
361 + image 5.11 before modification
421 421  
422 422  [[image:image-20241121180517-16.png]]
423 423  
424 - image 5.12 ui_water_leak/CMakeLists.txt after modification
365 + image 5.12 after modification
425 425  
426 -**8. Modify ui_water_leak.h file.** The image 5.13, 5.14 show the code before modification, and the image 5.15, 5.16 show the code after modification.
367 +8.
427 427  
428 -[[image:image-20241122094200-23.png]]
429 429  
430 - image 5.13 ui_water_leak.h (1) before modification
431 431  
432 -[[image:image-20241122094320-24.png||height="852" width="554"]]
433 433  
434 - image 5.14 ui_water_leak.h (2) before modification
435 435  
436 -[[image:image-20241122094600-25.png||height="1078" width="554"]]
437 437  
438 - image 5.15 ui_water_leak.h (1) after modification
439 439  
440 -[[image:image-20241122094719-26.png||height="941" width="583"]]
441 441  
442 - image 5.16 ui_water_leak.h (2) before modification
443 443  
444 -**9. Modify ui_water_leak.c file.** The image 5.17, 5.18, 5.19 show the code before modification, and the image 5.20, 5.21, 5.22 show the code after modification.
445 445  
446 -_ui_flag_modify( ((lv_obj_t *)(e->user_data)), LV_OBJ_FLAG_HIDDEN, _UI_MODIFY_FLAG_TOGGLE);  This code replaces 4 lines of code in ui_water_leak.c, so it is pasted here for convenience.
447 447  
448 -[[image:image-20241122102929-27.png||height="619" width="426"]]
449 -
450 - image 5.17 ui_water_leak.c (1) before modification
451 -
452 -[[image:image-20241122112838-30.png||height="551" width="628"]]
453 -
454 - image 5.18 ui_water_leak.c (2) before modification
455 -
456 -[[image:image-20241122110815-29.png||height="725" width="712"]]
457 -
458 - image 5.19 ui_water_leak.c (3) before modification
459 -
460 -[[image:image-20241122113158-31.png||height="872" width="677"]]
461 -
462 - image 5.20 ui_water_leak.c (1) after modification
463 -
464 -[[image:image-20241122113259-33.png||height="874" width="724"]]
465 -
466 - image 5.21 ui_water_leak.c (2) after modification
467 -
468 -[[image:image-20241122113359-34.png||height="804" width="746"]]
469 -
470 - image 5.22 ui_water_leak.c (3) after modification
471 -
472 -**10. Modify ui_water_leak_events.h file.** The image 5.23 show the code before modification, and the image 5.24 show the code after modification.
473 -
474 -[[image:image-20241122134113-35.png||height="380" width="421"]]
475 -
476 - image 5.23 ui_water_leak_events_.h before modification
477 -
478 -[[image:image-20241122134420-37.png||height="201" width="283"]]
479 -
480 -image 5.24 ui_water_leak_events_.h after modification
481 -
482 -**11. Modify ui_water_leak_events.c file.** The image 5.25 show the code before modification, and the image 5.26 show the code after modification.
483 -
484 -Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
485 -
486 -Step2. add code  below in delete_object() function definition.
487 -
488 - panel_all * panel = find_upper_by_SensorPanel(&arr,((lv_obj_t *)(e->user_data~)~)~);
489 -
490 - size_t index = panel->panel_obj_index;
491 -
492 - deleteElement(&arr, index);
493 -
494 -[[image:image-20241122135023-38.png||height="358" width="372"]]
495 -
496 - image 5.25 ui_water_leak_events_.c before modification
497 -
498 -[[image:image-20241122135258-39.png||height="403" width="559"]]
499 -
500 - image 5.26 ui_water_leak_events_.c after modification
501 -
502 -**12. Modify ui_water_leak_style.c file.**
503 -
504 -Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
505 -
506 - add '#include "../../sort.h"'
507 -
508 - add '#include "ui.h"'
509 -
510 -[[image:image-20241122141536-41.png||height="361" width="612"]]
511 -
512 - image 5.27 ui_water_leak_style.c (1) before modification
513 -
514 -[[image:image-20241122142129-42.png||height="386" width="613"]]
515 -
516 - image 5.28 ui_water_leak_style.c (1) after modification
517 -
518 -Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
519 -
520 - delete code as shown in image 5.29
521 -
522 -[[image:image-20241122145620-44.png||height="757" width="671"]]
523 -
524 - image 5.29 ui_water_leak_style.c (2)
525 -
526 -Step3. The image 5.30, 5.31 show the change.
527 -
528 -[[image:image-20241122152026-45.png||height="277" width="828"]]
529 -
530 - image 5.30 ui_water_leak_style.c (3) before modification
531 -
532 -[[image:image-20241122152542-46.png||height="293" width="830"]]
533 -
534 - image 5.31 ui_water_leak_style.c (3) after modification
535 -
536 -Step4. Copy partly the code in ui_water_leak.c, paste at extra_lib/sort.h(The process is shown in image 5.32, 5.33).
537 -
538 -[[image:image-20241122153958-47.png]]
539 -
540 - image 5.32 ui_water_leak_style.c (4)
541 -
542 -[[image:image-20241122154755-49.png||height="864" width="513"]]
543 -
544 - image 5.33 ui_water_leak_style.c (4)
545 -
546 -Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
547 -
548 -[[image:image-20241122155650-50.png||height="922" width="513"]]
549 -
550 - image 5.34 ui_water_leak_style.c (5)
551 -
552 -Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
553 -
554 -[[image:image-20241122161934-51.png]]
555 -
556 - image 5.35
557 -
558 -Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
559 -
560 -[[image:image-20241122162852-53.png||height="330" width="529"]]
561 -
562 - image 5.37
563 -
564 -Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
565 -
566 -panel_with_type union_sensor;
567 -
568 -union_sensor.panel_type = WATER_LEAK_TYPE;
569 -
570 -......
571 -
572 -lv_obj_set_x(union_sensor.panel_union.door.ui_PanelSensorDoor, x_by_index(index));
573 -
574 -lv_obj_set_y(union_sensor.panel_union.door.ui_PanelSensorDoor, y_by_index(index));
575 -
576 -return union_sensor;
577 -
578 -[[image:image-20241122171211-54.png||height="635" width="792"]]
579 -
580 - image 5.38
581 -
582 -**13. Modify sort.c file.**
583 -
584 -Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
585 -
586 -[[image:image-20241122173718-56.png||height="378" width="579"]]
587 -
588 - image 5.39 sort.c (1)
589 -
590 -There are still some changes need to be done in sort.c, and omit here for the moment.
591 -
592 -
593 593  = 6. FAQ =
594 594  
595 595  == 6.1 ==
image-20241122154755-49.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -135.7 KB
Content
image-20241122155650-50.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -104.4 KB
Content
image-20241122161934-51.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -230.3 KB
Content
image-20241122162612-52.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -58.7 KB
Content
image-20241122162852-53.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -125.5 KB
Content
image-20241122171211-54.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -173.3 KB
Content
image-20241122173706-55.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -37.6 KB
Content
image-20241122173718-56.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -37.6 KB
Content
squalreline-trial.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -60.4 KB
Content
squareline.io_downloads.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -1.5 MB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0