07-23-2025 08:22 AM
Hello everyone,
I am still getting used to our company's Win11 upgrade. The development using LV and Teststand has become more tedious with the new taskbar. I currently develop a measurement system using queues and multiple statemachines. To debug I usually jump between the different statemachines and then in the designated VIs. Therefore I have multiple VIs open and quickly loose orientation of all opened files. In the old days (< Win10) I was able to extend the taskbar three rows and at least can see all the opened files. This is no longer possible.
One quick fix for my workflow would be to jump inside a VI without opening it in a separate window. So I can follow a trace without the mess on my taskbar. similar to opening links in a browser.
Is this functionality possible in LV (21)?
07-23-2025 08:28 AM
Hi s.h,
@s.h._tech wrote:
One quick fix for my workflow would be to jump inside a VI without opening it in a separate window.
How do you "open a VI without opening its fp/bd window"?
And why don't you use the project tree to organize your VIs (and open them from there)?
07-23-2025 09:08 AM
Especially while debugging, I need to follow SubVis. Some of our VIs call other VIs and so on. When I arrive at the VI I need, I leave behind a trace of 2-10 unnecessary VIs.
Instead of opening a SubVi in the opened VI, it would be nice to open the SubVI and close the VI that called the SubVi.
An example would be the Windows Explorer. When clicking on a subfolder no new window appears, instead the active window jumps in the subfolder.
07-23-2025 09:12 AM - edited 07-23-2025 09:13 AM
Hi s.h,
@s.h._tech wrote:
An example would be the Windows Explorer. When clicking on a subfolder no new window appears, instead the active window jumps in the subfolder.
LabVIEW IDE is not the same as the Explorer…
@s.h._tech wrote:
Instead of opening a SubVi in the opened VI, it would be nice to open the SubVI and close the VI that called the SubVi.
You need to close the calling VI on your own…
@s.h._tech wrote:
Especially while debugging, I need to follow SubVis. Some of our VIs call other VIs and so on. When I arrive at the VI I need, I leave behind a trace of 2-10 unnecessary VIs.
That's why NI implemented breakpoints in the IDE. No need to follow a stack of 10 subVIs when you know where to debug!
In the end it boils down to a "problem with YOUR workflow"… 😄
07-23-2025 10:40 AM - edited 07-23-2025 10:43 AM
OP- the answer to your question is no. It will always open a new window- there's not a way to auto close the previous one unfortunately.
There is a third party tool called "ExplorerPatcher" that may let you have a multi row taskbar: https://superuser.com/questions/1895674/windows-11-taskbar-multiple-rows
07-23-2025 10:55 AM
You mentioned difficulty due to Windows 11 upgrade, so I'm guessing you don't like something about the taskbar. Check taskbar behaviors to see if there are other options you like better. For example, if you currently get a lot of taskbar buttons for LabVIEW, but you want to limit it to 1, you can "Always" combine taskbar buttons.
07-23-2025 11:08 AM
Combining all windows would make the visibility even worse
07-23-2025 11:14 AM
@GerdW wrote:
Hi s.h,
@s.h._tech wrote:
One quick fix for my workflow would be to jump inside a VI without opening it in a separate window.
How do you "open a VI without opening its fp/bd window"?
That was my initial thought. My guess is that what he wants is that when stepping into a sub VI, the open BD is replaced by the sub VI's BD, then when the sub VI exits, its BD is closed, and the caller's BD is reopened.
07-23-2025 11:42 AM
Thanks for writing it more clearly. Yes
07-23-2025 12:47 PM
Use breakpoints. When you hit the breakpoint it will open the vi with the breakpoint and bring it to the front. It will also make you unpause the code. This will also give you the ability to turn on the light bulb so you can see the execution of the code slowly.