Locked VI shouldn't prohibit viewing Window Appearance options

[dadreamer]

This is not a real issue, but more of a wish, tiny though for submitting to the Idea Exchange section. When a VI is in locked state (using the option on VI Properties -> Protection tab or it doesn't have a block diagram), it's impossible to display its Window Appearance options, because the "Customize..." button becomes disabled.

But it would be more logical instead to allow the user to open the Window Appearance window with all these options disabled.

In cases when a VI doesn't have a diagram, it's impossible to set the VI into the Unlocked state (e.g., it's contained inside an exe or lvlibp). There's a way to open it with the Open VI Reference node and retrieve the settings with the VI Server counterparts (if implemented), but it's not as easy as pressing a single button.

[santo_13]

The goal of locking the VI is to restrict any means of editing to the VI whether FP or BD.

[Kyle97330]

---

@santo_13 wrote:

The goal of locking the VI is to restrict any means of editing to the VI whether FP or BD.

---

It certainly is, but you're missing the point of the complaint being that you can't even SEE what the current settings are on a locked VI, which is a perfectly valid complaint.

You can currently see things like whether it's re-entrant or not, but not edit them, the difference is that the panel showing the options isn't even available to view.

[JÞB]

---

@Kyle97330 wrote:

---

@santo_13 wrote:

The goal of locking the VI is to restrict any means of editing to the VI whether FP or BD.

---

It certainly is, but you're missing the point of the complaint being that you can't even SEE what the current settings are on a locked VI, which is a perfectly valid complaint.

You can currently see things like whether it's re-entrant or not, but not edit them, the difference is that the panel showing the options isn't even available to view.

---

All those properties are runtime readable.  Most are even runtime Writable! Although, you will get a password prompt to unlock any locked vis if you attempt a write.

Simple enough to build your own property display vi since you only need 1 pnode and a VI ref in.

You could easily leverage the existing property display viewer from the vi settings dialog in the app build spec.