EEZ Studio Project Imports: Preserve Relative Paths and Import Aliases When Moving a Project
Which parts of an imported-project reference must stay valid when moving a main project or reorganizing a shared project library?
Firmware requirements, peripheral integration, task coordination, fault diagnosis and verification for microcontroller products. Start from the actual hardware and acceptance conditions before choosing an implementation.
Which parts of an imported-project reference must stay valid when moving a main project or reorganizing a shared project library?
Why can resetting a Dashboard persistent variable to null leave an older saved value available on the next load?
Why does moving a labeled connection into another user action break a route even when the label text is unchanged?
How can evaluating a live variable after a queued step produce a different value from the one present when the user pressed a button?
Why can a user action deliver a result while its caller still lacks the intended completion sequence?
Why can the displayed ordering change while the original model array remains unchanged?
Why does editing a delay variable while a Flow is already waiting not necessarily change the current wait?
Why does a Counter body run the requested number of times while done remains silent until control returns once more?
How can a loop restart unexpectedly or produce the wrong number of body executions when its return line or step changes?
Why can the sequence output continue even when no case matched, and how should a default branch be represented?