LabVIEW Public Beta Program in 2025
[New Feature] Debug Window
LabVIEW 2025 Q3 combines probe and breakpoint management in a new Debug Window, which replaces the Probe Watch Window.
The Debug Window lists breakpoints and probes for all VIs in memory. The Value column formatting is configurable with an INI token that assigns a format string (e.g., DebugNumericFormat="%#_4g"). The Last Update column shows time to millisecond resolution and does not include date.
The right-click menu in the Debug Window tree allows you to add, remove, rename, highlight, and export data for probes and breakpoints. You can also enable and disable breakpoints.
You can also add and remove probes and breakpoints from the right-click menu on wires on VI block diagrams. The Breakpoint Manager is no longer in the right-click menu.
Ctrl+D opens the Debug Window. The keyboard shortcut for Arrange>>Distribute changed to Ctrl+Shift+D.
The Debug Options button on the Debug Window has the following commands:
- Show/Hide Probe Display – show or hide the probe display pane on the right side of the Debug Window.
- Keep Window on Top – toggle whether the Debug window is a floating window.
- Show Values on Wires – when enabled, temporary labels will show probe values directly on the VI block diagram during VI execution.
-
In the probe display pane, the Probe Options button enables you to switch quickly between different probe styles or create a new custom probe.
The Debug Window after opening a LabVIEW Project briefly appears and goes away the first time. I've attached a video of this happening, where you can see it briefy appear the first time.
I'm using the TestStand Operator Interface from the 2025 Q2 install as the project to open. But I've repeated this with just a project made with New -> Empty Project and it does the same.
The Debug Window is a nice feature, thank you!
If Probes are active and the code is running: As soon as "show Values on wire" is activated, the blue Values appear with correct, always updated values.
But if "show Values on wire" is deactivated, the blue Values are still there, but no longer updated.
The Value on the blue Field shows 12 but the correct value at this time is 468. I would expect that the blue fields are no longer visible after deactivating "show Values on wire".
Maybe someone with access to beta could test if this is the same behavior with Q3.
A breakpoint cleared during a break condition->save all is not cleared anymore after reload of project. Seeing this in a dynamic dispatch vi.
2025 Q3 Beta behaves the same way as your video. If I clear it, while its running, it doesn't stay cleared next time the project is open.
If instead I open the VI not in the run state and clear the breakpoint, it correctly shows the dirty dot and saving it removes the breakpoint permanently. Likewise, using the new Debug Window while the vi is not in run state, and clearing the breakpoint from there, removes it permanently.
But if I use the debug window, and clear it while the VI is in run state, it doesn't do the dirty dot and doesn't persist.So it seems like this issue is related to the breakpoint being cleared while the VI is in a run state. Like that doesn't flag the VI as changed, so it never gets saved.
