You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: link existing screens as state variants via drag connection (#16)
When dragging a connection from one screen to another, a popup now asks
the user to choose between "Navigate" (creates a navigation connection)
and "State Variant" (links the target screen into the source's state
group). This enables users to assign existing screens as state variants
without having to create new blank screens.
Co-authored-by: Quang Tran <16215255+trmquang93@users.noreply.github.com>
Copy file name to clipboardExpand all lines: src/pages/docs/userGuide.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -184,10 +184,14 @@ After creating a conditional group, inline label inputs appear along each connec
184
184
185
185
Screen states let you model different visual variants of the same logical screen — for example, a loading state, an error state, or a logged-in vs. logged-out view.
186
186
187
-
### Adding a state
187
+
### Adding a new state screen
188
188
189
189
Select a screen, then click "Add State" in the right sidebar. A new variant screen is created 250px to the right of the original, sharing a state group with it. The original screen is automatically labeled "Default".
190
190
191
+
### Linking an existing screen as a state variant
192
+
193
+
Drag a connection from one screen to another. A popup appears asking you to choose between **Navigate** (creates a normal navigation link) and **State Variant** (links the target screen into the source screen's state group). Choosing "State Variant" groups both screens together — a dashed connector line appears between them, and they are treated as a single logical screen in the generated instructions.
194
+
191
195
### Naming states
192
196
193
197
Each state has a name field visible in the sidebar (e.g., "Loading", "Error", "Empty"). State names appear in the screen header on the canvas and in the generated instructions.
0 commit comments