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. pradeeka1 +XWiki.Xiaoling - Content
-
... ... @@ -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** 174 +* Select** File -> Project Settings** 175 175 176 176 [[image:1727229582471-566.png]] 177 177 ... ... @@ -192,8 +192,9 @@ 192 192 Now you can start building the sample UI. Follow the steps below: 193 193 194 194 195 -=== Add widgets === 195 +=== **Add widgets** === 196 196 197 + 197 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 198 199 199 Add a Label, Button, and Image to the screen as shown in **Image 5**. ... ... @@ -202,8 +202,10 @@ 202 202 203 203 Image 5: Add widgets 204 204 205 -=== Modify widget properties === 206 206 207 +=== **Modify widget properties** === 208 + 209 + 207 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. 208 208 209 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. ... ... @@ -213,30 +213,36 @@ 213 213 Image 6: The button widget's "Inspector" tab 214 214 215 215 216 -==== Changing the Button properties ==== 219 +==== **Changing the Button properties** ==== 217 217 218 -Click the Button. Under the **Label** section, type "Click for details..." in the **Text** textbox. 219 219 220 - Underthe"Layout" you can222 +Click the Button. 221 221 224 +Under the "Layout" you can change the button's position and size. 225 + 222 222 [[image:1727485251053-655.png]] 223 223 224 - image 7the button widget's "BUTTON" tab228 +Image 7: The button widget's "BUTTON" tab 225 225 226 226 227 - Thirdpart:It is anareaofstyle setting.231 +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. 228 228 229 -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. 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. 230 230 231 231 [[image:1727485480434-713.png||height="395" width="290"]] 232 232 233 - image 8add event for button242 + Image 8: Add an event for the button 234 234 235 235 236 -==== Changing the label properties ==== 245 +==== **Changing the label properties** ==== 237 237 238 -Click the label. Under the **Label** section, type "Hello World!" in the **Text** textbox. 239 239 248 +Click the label. Under the **Label** section, type "Click For Detail" in the **Text** textbox. 240 240 241 241 [[image:image-20240928090825-1.png||height="327" width="391"]] 242 242 ... ... @@ -243,8 +243,9 @@ 243 243 Image 9: Modify text of label widget 244 244 245 245 246 -==== 4.Changing image properties ====255 +==== **Changing image properties** ==== 247 247 257 + 248 248 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. 249 249 250 250 [[image:image-20240928113424-9.png||height="355" width="505"]] ... ... @@ -255,30 +255,38 @@ 255 255 256 256 image 11 use image widget in SquareLine Studio 257 257 258 -**5. The relationship between widgets** 259 259 260 -The rearetwo common relationshipsbetween 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.269 +==== **The relationship between widgets** ==== 261 261 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 + 262 262 [[image:1727486567182-334.png||height="318" width="278"]] 263 263 264 -image 12 move label1 to make label1 widget be a child of button1 widget(1) 265 265 280 +Move **Label1** to make it a child of **Button1**. See Image 13. 281 + 266 266 [[image:image-20240928112001-8.png||height="431" width="796"]] 267 267 268 - image 13movelabel1 to makelabel1 widgetbea child ofbutton1widget(2)284 + Image 13: Move Label1 to make it a child of Button1. 269 269 270 270 271 -** 6.Preview the screen**287 +==== **Preview the screen** ==== 272 272 273 -You can test the result by clicking on the **PLAY** button. The screen will change into play mode. 274 274 290 +You can test the result by clicking on the **PLAY** button. The screen will change into play mode. See Image 14. 291 + 275 275 [[image:1727487368023-281.png]] 276 276 277 - image 14click on thetriangleiconto start or end the simulation294 + Image 14: Simulating the project 278 278 279 -For more detailed usage, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]]. 280 280 297 +For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]]. 281 281 299 + 282 282 == 2.4 Integrate UI Code to ESP-IDF Project == 283 283 284 284 ... ... @@ -340,8 +340,9 @@ 340 340 341 341 = 4. Example Project 2: LoRaWAN RS485 Alarm = 342 342 343 -= 5. 361 += 5. The way to add a new panel to project = 344 344 363 + 345 345 **~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.** 346 346 347 347 [[image:image-20241121113445-1.png||height="584" width="934"]] ... ... @@ -348,6 +348,7 @@ 348 348 349 349 image 5.1 a panel about water_leak 350 350 370 + 351 351 **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. 352 352 353 353 [[image:image-20241121141120-4.png||height="383" width="795"]] ... ... @@ -354,6 +354,7 @@ 354 354 355 355 image 5.2 ui files exported 356 356 377 + 357 357 **3. Delete or rename some file.** Here are the steps: 358 358 359 359 Step1 Delete the 'components' directory. ... ... @@ -488,6 +488,7 @@ 488 488 489 489 image 5.26 ui_water_leak_events_.c after modification 490 490 512 + 491 491 **12. Modify ui_water_leak_style.c file.** 492 492 493 493 Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"' ... ... @@ -504,6 +504,7 @@ 504 504 505 505 image 5.28 ui_water_leak_style.c (1) after modification 506 506 529 + 507 507 Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)' 508 508 509 509 delete code as shown in image 5.29 ... ... @@ -512,6 +512,7 @@ 512 512 513 513 image 5.29 ui_water_leak_style.c (2) 514 514 538 + 515 515 Step3. The image 5.30, 5.31 show the change. 516 516 517 517 [[image:image-20241122152026-45.png||height="277" width="828"]] ... ... @@ -522,6 +522,7 @@ 522 522 523 523 image 5.31 ui_water_leak_style.c (3) after modification 524 524 549 + 525 525 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). 526 526 527 527 [[image:image-20241122153958-47.png]] ... ... @@ -532,6 +532,7 @@ 532 532 533 533 image 5.33 ui_water_leak_style.c (4) 534 534 560 + 535 535 Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34). 536 536 537 537 [[image:image-20241122155650-50.png||height="922" width="513"]] ... ... @@ -538,6 +538,7 @@ 538 538 539 539 image 5.34 ui_water_leak_style.c (5) 540 540 567 + 541 541 Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35. 542 542 543 543 [[image:image-20241122161934-51.png]] ... ... @@ -544,6 +544,7 @@ 544 544 545 545 image 5.35 546 546 574 + 547 547 Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36. 548 548 549 549 [[image:image-20241122162852-53.png||height="330" width="529"]] ... ... @@ -550,6 +550,7 @@ 550 550 551 551 image 5.37 552 552 581 + 553 553 Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail. 554 554 555 555 panel_with_type union_sensor; ... ... @@ -568,6 +568,7 @@ 568 568 569 569 image 5.38 570 570 600 + 571 571 **13. Modify sort.c file.** 572 572 573 573 Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.