Open Subvi NOT in a new window

[Gregory]

---

@s.h._tech wrote:

Combining all windows would make the visibility even worse

---

I see, can you explain how it was better in Windows 10 then?

[BertMcMahan]

---

@Gregory wrote:

---

@s.h._tech wrote:

Combining all windows would make the visibility even worse

---

I see, can you explain how it was better in Windows 10 then?

---

The OP wants his taskbar to have lots of buttons for windows so he can have lots of stuff open. The default behavior in Windows 10 was to combine all windows into a single icon on your taskbar, but you could set it so that all windows have their own box in the taskbar, the way it was "back in the day". Windows 10 also allowed you to stretch the taskbar vertically so you could have 2 or 3 rows of entries in the taskbar.

Windows 11 still lets you give an entry to all items in the taskbar (rather than collapsing them all under a single "LabVIEW" button) but now you can't stretch the taskbar anymore, so he has a whole bunch of windows crowded in the taskbar.

I'm of the same mind as OP, personally- I hate the "collapse all windows into a single thing to click" just as much as I hate the "remove text and only leave an icon" so I have my taskbar set to show the names of the window in the taskbar and never combine them. I also tend to have a whole bunch of windows open when designing/debugging complicated programs where it's useful to see 5 or 6 different VI's or windows open at once.

My solution is to use two 1440p monitors, which gives me a LOT more pixels to work with, and to use ExplorerPatcher to de-Windows 11 the taskbar.

Basically the OP wants his taskbar to look like this:

[s.h._tech]

---

 and to use ExplorerPatcher 

---

Not allowed in my organization. All the software needs to be validated before it is available in our download center.

[cordm]

That seems like a useful feature, you should make it an idea on the idea exchange

Maybe something like shift-double clicking a sub VI opens the sub VI FP and closes the calling VIs FP/BD (if unmodified).

[Jacobson]

Q and I worked on something that tried to address this. It's available on VIPM and overwrites the navigation window (Ctrl+Shift+N) and when you click on a subVI it will open the BD in a new window which lets you continue to click into different subVIs while keeping track of the trace.

I'm not sure it still works on newer releases so I would backup resource/dialog/zoom_out.llb. I think they changed it from an actual llb to a folder with .llb in the name which messed something up.

https://www.vipm.io/package/vi_peek/

[s.h._tech]

I Installed VIPM and the "VI_Peek" package. A lot of dependencies were also installed (DQMH for example)

I am unable to verify if "VI Peel" is running or correctly configured. Since LV behaves normally, I imagine it is not as easy as just installing. There are some example projects using DQMH streams, but I am unsure how to proceed. When I have time, I will take a closer look at what VIPM has to offer and if it does influence my current setup. Since the whole NI ecosystem is very fragile, I do not want to upgrade specific drivers or runtimes. 

ExplorerPatcher keeps getting deleted by my organization. It showed the LV symbols in the stacked taskbar, but all windows did not have names in it.

For now I try to open only necessary VIs in the project window. When debugging I have to live with the NI window in the taskbar, which displays all opened VIs. The slowdown in development is noticeable and we are working on alternative solutions (back to Linux or Win7 since all our PXIs are still Win7).

[VinnyAstro]

I like the idea of opening VI in a ephemeral way (is that the right english word?), sometimes I'm just unsure where to look and I have to go down the rabbit whole, is it because I'm bad at it? Maybe.

But I do like the idea of maybe revisiting the Navigator Pane (ctrl+shift+N) that could be more useful as an actual Opened-VI manager if that doesn't exist, I don't think it would be too difficult to program. A simple VI can list all VIs in memory that are opened (with the property FP.State), just a few more steps and you could easily close them.

Put each in a cluster with a "Close" button, back in an array, and you can easily choose the size and orientation of it, adapt your UI window how you want (set it to Floating for instance) add a bit of logic to navigate quickly between the opened VI (Click on a name puts it to front) and you got a nice and quick "Opened VI Navigator Pane" !

Is it necessary or the workflow should be revisited? That I don't know tbh.

[BertMcMahan]

---

@VinnyAstro wrote:

But I do like the idea of maybe revisiting the Navigator Pane (ctrl+shift+N) that could be more useful as an actual Opened-VI manager if that doesn't exist, I don't think it would be too difficult to program.

---

Try clicking "Window" -> "All Windows...".

[VinnyAstro]

---

@BertMcMahan  a écrit :

---

@VinnyAstro wrote:

But I do like the idea of maybe revisiting the Navigator Pane (ctrl+shift+N) that could be more useful as an actual Opened-VI manager if that doesn't exist, I don't think it would be too difficult to program.

---

Try clicking "Window" -> "All Windows...".

---

That's a good point, I didn't even know about that one haha But I also meant as something that stays on, like the navigation pane. Yet again, is it necessary, I'm not sure, I just liked the idea 🙂