Changes for page LTS5 LoRa HMI Touch Screen
Last modified by Dilisi S on 2025/02/26 19:24
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.pradeeka - Content
-
... ... @@ -102,7 +102,7 @@ 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 ... ... @@ -153,6 +153,7 @@ 153 153 * Max. 2 themes 154 154 * Max. 1 component 155 155 156 + 156 156 == 2.3 Simple usage of SquareLine Studio and exporting UI code == 157 157 158 158 ... ... @@ -164,6 +164,7 @@ 164 164 * In the **PROJECT SETTINGS**, select **LVGL version** **8.3.11** 165 165 * Select the **CREATE **button. 166 166 168 + 167 167 [[image:image-20240928103357-2.png||height="680" width="708"]] 168 168 169 169 Image 2: Creating a new SquareLine project ... ... @@ -171,7 +171,7 @@ 171 171 172 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 173 174 -* Select **File -> Project Settings**176 +* Select File -> Project Settings 175 175 176 176 [[image:1727229582471-566.png]] 177 177 ... ... @@ -189,72 +189,49 @@ 189 189 Image 4 Configure/modify project settings 190 190 191 191 192 -Now you can start building the sampleUI. Follow the steps below:194 +Now you can start building the UI. Follow the steps below: 193 193 194 194 195 - ===**Add widgets**===197 +**~1. add widget** 196 196 199 +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. 197 197 198 -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. 199 - 200 -Add a Label, Button, and Image to the screen as shown in **Image 5**. 201 - 202 202 [[image:image-20240928111412-6.png||height="526" width="864"]] 203 203 204 - Image 5:Add widgets203 + image 5 add widgets 205 205 205 +**2. modify widget** 206 206 207 - ===**Modify widget properties**===207 +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 - 210 -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. 211 - 212 -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. 213 - 214 214 [[image:1727485118799-984.png]] 215 215 216 - Image 6:The button widget's "Inspector" tab211 + image 6 the button widget's "Inspector" tab 217 217 213 +Second part: "Layout" means a auto position-management for widgets contained in the parent widget. "Transform" includes size, position and align modification. 218 218 219 -==== **Changing the Button properties** ==== 220 - 221 - 222 -Click the Button. 223 - 224 -Under the "Layout" you can change the button's position and size. 225 - 226 226 [[image:1727485251053-655.png]] 227 227 228 - Image 7:The button widget's "BUTTON" tab217 +image 7 the button widget's "BUTTON" tab 229 229 219 +Third part: It is an area of style setting. 230 230 231 - Next, add a click event tothebutton.Whenthe button is clicked,anevent shouldtriggertochange the current screen(Screen1)to awscreen(Screen2)withafade effect and thetransitionfrom Screen1 to Screen2shouldtake500ms.221 +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. 232 232 233 -* Click **ADD EVENT** button. 234 -* Select **CLICKED** under the Trigger. 235 -* Select **Screen2** from **Screen to**. 236 -* Select **FADE ON** from **Fade mode**. 237 -* Enter **500** in the **Speed** text box. 238 -* Finally, click **ADD** button. 239 - 240 240 [[image:1727485480434-713.png||height="395" width="290"]] 241 241 242 - Image 8:Addanevent forthebutton225 + image 8 add event for button 243 243 227 +**3. change label widget content** 244 244 245 - ====**Changing the labelproperties**====229 +Modify the content in text as shown in image 9, the text content of label widget will be changed accordingly. 246 246 247 - 248 -Click the label. Under the **Label** section, type "Click For Detail" in the **Text** textbox. 249 - 250 250 [[image:image-20240928090825-1.png||height="327" width="391"]] 251 251 252 - Image 9:Modify text of label widget233 + image 9 modify text content of label widget 253 253 235 +**4. Add image into project** 254 254 255 -==== **Changing image properties** ==== 256 - 257 - 258 258 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. 259 259 260 260 [[image:image-20240928113424-9.png||height="355" width="505"]] ... ... @@ -265,38 +265,29 @@ 265 265 266 266 image 11 use image widget in SquareLine Studio 267 267 247 +**5. The relationship between widgets** 268 268 269 - ==== **The relationship between widgets**====249 +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. 270 270 271 - 272 -Widgets commonly have two types of relationships: **parallel** and **parent-child**. 273 - 274 -* In a **parallel relationship**, widgets' positions are determined relative to a shared reference object. 275 -* 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. 276 - 277 277 [[image:1727486567182-334.png||height="318" width="278"]] 278 278 253 +image 12 move label1 to make label1 widget be a child of button1 widget(1) 279 279 280 -Move **Label1** to make it a child of **Button1**. See Image 13. 281 - 282 282 [[image:image-20240928112001-8.png||height="431" width="796"]] 283 283 284 - Image 13: MoveLabel1 to make it a child ofButton1.257 + image 13 move label1 to make label1 widget be a child of button1 widget(2) 285 285 259 +**6. Preview the final effect** 286 286 287 - ====**Preview the screen**====261 +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. 288 288 289 - 290 -You can test the result by clicking on the **PLAY** button. The screen will change into play mode. See Image 14. 291 - 292 292 [[image:1727487368023-281.png]] 293 293 294 - Image 14:Simulatingtheproject265 + image 14 click on the triangle icon to start or end the simulation 295 295 267 +For more detailed usage, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]]. 296 296 297 -For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]]. 298 298 299 - 300 300 == 2.4 Integrate UI Code to ESP-IDF Project == 301 301 302 302 ... ... @@ -358,9 +358,8 @@ 358 358 359 359 = 4. Example Project 2: LoRaWAN RS485 Alarm = 360 360 361 -= 5. The way to add a new panel to project = 331 += 5. The way to add a new panel to project = 362 362 363 - 364 364 **~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.** 365 365 366 366 [[image:image-20241121113445-1.png||height="584" width="934"]] ... ... @@ -367,7 +367,6 @@ 367 367 368 368 image 5.1 a panel about water_leak 369 369 370 - 371 371 **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. 372 372 373 373 [[image:image-20241121141120-4.png||height="383" width="795"]] ... ... @@ -374,7 +374,6 @@ 374 374 375 375 image 5.2 ui files exported 376 376 377 - 378 378 **3. Delete or rename some file.** Here are the steps: 379 379 380 380 Step1 Delete the 'components' directory. ... ... @@ -509,7 +509,6 @@ 509 509 510 510 image 5.26 ui_water_leak_events_.c after modification 511 511 512 - 513 513 **12. Modify ui_water_leak_style.c file.** 514 514 515 515 Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"' ... ... @@ -526,7 +526,6 @@ 526 526 527 527 image 5.28 ui_water_leak_style.c (1) after modification 528 528 529 - 530 530 Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)' 531 531 532 532 delete code as shown in image 5.29 ... ... @@ -535,7 +535,6 @@ 535 535 536 536 image 5.29 ui_water_leak_style.c (2) 537 537 538 - 539 539 Step3. The image 5.30, 5.31 show the change. 540 540 541 541 [[image:image-20241122152026-45.png||height="277" width="828"]] ... ... @@ -546,7 +546,6 @@ 546 546 547 547 image 5.31 ui_water_leak_style.c (3) after modification 548 548 549 - 550 550 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). 551 551 552 552 [[image:image-20241122153958-47.png]] ... ... @@ -557,7 +557,6 @@ 557 557 558 558 image 5.33 ui_water_leak_style.c (4) 559 559 560 - 561 561 Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34). 562 562 563 563 [[image:image-20241122155650-50.png||height="922" width="513"]] ... ... @@ -564,7 +564,6 @@ 564 564 565 565 image 5.34 ui_water_leak_style.c (5) 566 566 567 - 568 568 Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35. 569 569 570 570 [[image:image-20241122161934-51.png]] ... ... @@ -571,7 +571,6 @@ 571 571 572 572 image 5.35 573 573 574 - 575 575 Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36. 576 576 577 577 [[image:image-20241122162852-53.png||height="330" width="529"]] ... ... @@ -578,7 +578,6 @@ 578 578 579 579 image 5.37 580 580 581 - 582 582 Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail. 583 583 584 584 panel_with_type union_sensor; ... ... @@ -597,7 +597,6 @@ 597 597 598 598 image 5.38 599 599 600 - 601 601 **13. Modify sort.c file.** 602 602 603 603 Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.