Is there an easy way to edit things under an invisible control

[InfiniteNothing]

For clarity, I should mention that I'm trying to do these actions during edit time and not programmatically.

I have an invisible button floating over some other controls and a decoration. What's the easiest way to interact with the things under the invisible boolean. For example how would I delete or move the decoration or maybe toggle a boolean under the invisible button.  Of course I could click on the invisible button and move it out of the way and then move it back but I'm hoping there's an easier way so I don't have to worry about repositioning the invisible button or messing around with reordering controls.

Message Edited by InfiniteNothing on 09-29-2009 02:00 PM

[Spectre_Dave]

Try selecting the "invisible" button then using the reorder menu send the "invisible" control to the back.

[billko]

Why would you even have the invisible control overlaying the visible ones?  Why not park it outside the visible area of your VI?  Then you don't even have to make it invisible.  Or does this control become visible at some point when running the VI?

Bill

[InfiniteNothing]

---

VADave wrote:
Try selecting the "invisible" button then using the reorder menu send the "invisible" control to the back.

---

My biggest problem with that method is that I might have to send it back many steps. If I move it all the way back, I might not be able to get it back to where it was originally.

Message Edited by InfiniteNothing on 09-29-2009 02:11 PM

[InfiniteNothing]

---

billko wrote:

Why would you even have the invisible control overlaying the visible ones?  Why not park it outside the visible area of your VI?  Then you don't even have to make it invisible.  Or does this control become visible at some point when running the VI?

Bill

---

Basically, there's a fairly large area where a user can click to trigger an event. This was the easiest way I could think to implement that

Message Edited by InfiniteNothing on 09-29-2009 02:13 PM

[billko]

I see what you are getting at.  Perhaps the only way to do it is how it was suggested to send it to the back.  At least until you are going to actually run the code.

Bill

[Mark_Yedinak]

---

billko wrote:

Why would you even have the invisible control overlaying the visible ones?  Why not park it outside the visible area of your VI?  Then you don't even have to make it invisible.  Or does this control become visible at some point when running the VI?

Bill

---

I have used large invisible controls to quickly disable large selections of the front panel. It is a quick way to disable lots of controls at one time. Yes, you can disable them individually but it can be easier to disable them using a single control. If the invisible control sits over the area you want to prevent the user from interacting with you simply enable the control access to the items underneath is blocked. Disable the invisible control and everything underneath becomes usable again. I don't use this technique often but it is handy at times.

When I have used this technique a good way for interacting with the controls underneath are to drop a property node for the control in the VI and hide it. When it is hidden you can get at the items underneath it. When you are done editing unhide the control.

Message Edited by Mark Yedinak on 09-29-2009 04:16 PM

[InfiniteNothing]

---

Mark Yedinak wrote:

---

billko wrote:

Why would you even have the invisible control overlaying the visible ones?  Why not park it outside the visible area of your VI?  Then you don't even have to make it invisible.  Or does this control become visible at some point when running the VI?

Bill

---

I have used large invisible controls to quickly disable large selections of the front panel. It is a quick way to disable lots of controls at one time. Yes, you can disable them individually but it can be easier to disable them using a single control. If the invisible control sits over the area you want to prevent the user from interacting with you simply enable the control access to the items underneath is blocked. Disable the invisible control and everything underneath becomes usable again. I don't use this technique often but it is handy at times.

When I have used this technique a good way for interacting with the controls underneath are to drop a property node for the control in the VI and hide it. When it is hidden you can get at the items underneath it. When you are done editing unhide the control.

---

 Nice! I'll just make it invisible from the block diagram (right click the terminal>"hide control"). Hopefully I can remember to make my transparent control visible again. 😉 If anyone else has any other cool suggestions I'm always open for ideas.

Message Edited by InfiniteNothing on 09-29-2009 02:28 PM

[billko]

---

Mark Yedinak wrote:

---

billko wrote:

Why would you even have the invisible control overlaying the visible ones?  Why not park it outside the visible area of your VI?  Then you don't even have to make it invisible.  Or does this control become visible at some point when running the VI?

Bill

---

I have used large invisible controls to quickly disable large selections of the front panel. It is a quick way to disable lots of controls at one time. Yes, you can disable them individually but it can be easier to disable them using a single control. If the invisible control sits over the area you want to prevent the user from interacting with you simply enable the control access to the items underneath is blocked. Disable the invisible control and everything underneath becomes usable again. I don't use this technique often but it is handy at times.

When I have used this technique a good way for interacting with the controls underneath are to drop a property node for the control in the VI and hide it. When it is hidden you can get at the items underneath it. When you are done editing unhide the control.

Message Edited by Mark Yedinak on 09-29-2009 04:16 PM

---

Awesome.  I never thought of doing it that way.  Kudos, of course!

[RavensFan]

How about programmatically moving the control to a different position.  When you are ready, programmatically bring it back to its original coordinates.