Controls – Pages vs. Global Library (Burger Menu)
Overview
PLCVisu offers two different ways to access and use Controls (UI elements like buttons, sliders, and indicators):
1. Controls in Pages
When you add a Control directly in a Page:
- You can bind it to a variable using the
Connection String - You can edit the label, configure settings, and connect logic
- Ideal for immediate use in a specific visualization or HMI screen
- Each control instance is independent and specific to that Page
2. Controls via Burger Menu → Controls
This is the global Control Library and serves as a central management panel.
- You see an overview of all available Controls, including standard ones and your custom SVGs
- You can add new custom graphics or modify existing ones (e.g. update icons)
- Useful for managing corporate design, ensuring consistency across all projects
- These are templates – not yet active in a Page until explicitly inserted
Key Difference
| Feature | Controls in Pages | Controls via Burger Menu |
|---|---|---|
| Can be used directly | ✅ Yes | ❌ No – only templates |
| Logic binding (Connection String) | ✅ Yes | ❌ No |
| Edit visual template | ❌ Not here | ✅ Yes |
| Library management | ❌ | ✅ Centralized overview |
| Use case | Live visualization | Icon/Control management |
Typical Workflow
- Use Burger Menu → Controls to design or import new SVG-based controls
- Insert those controls in Pages to connect them to logic and display real-time values
Tip: Always manage your icon library and visual templates globally via the Controls menu – then bring them into Pages for logic integration.
Connection String
# Controls – Pages vs. Global Library (Burger Menu)
## Overview
PLCVisu offers two different ways to access and use Controls (UI elements like buttons, sliders, and indicators):
---
## 1. Controls in **Pages**
When you add a Control directly in a Page:
- You can **bind it to a variable** using the `Connection String`
- You can **edit the label**, configure settings, and connect logic
- Ideal for **immediate use** in a specific visualization or HMI screen
- Each control instance is **independent** and specific to that Page
---
## 2. Controls via **Burger Menu → Controls**
This is the **global Control Library** and serves as a central management panel.
- You see an **overview of all available Controls**, including standard ones and your custom SVGs
- You can **add new custom graphics** or modify existing ones (e.g. update icons)
- Useful for managing **corporate design**, ensuring consistency across all projects
- These are **templates** – not yet active in a Page until explicitly inserted
---
## Key Difference
| Feature | Controls in Pages | Controls via Burger Menu |
|----------------------------------|----------------------------|-------------------------------|
| Can be used directly | ✅ Yes | ❌ No – only templates |
| Logic binding (Connection String)| ✅ Yes | ❌ No |
| Edit visual template | ❌ Not here | ✅ Yes |
| Library management | ❌ | ✅ Centralized overview |
| Use case | Live visualization | Icon/Control management |
---
## Typical Workflow
1. Use **Burger Menu → Controls** to design or import new SVG-based controls
2. Insert those controls in **Pages** to connect them to logic and display real-time values
---
> **Tip:** Always manage your **icon library and visual templates** globally via the Controls menu – then bring them into Pages for logic integration.