LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Top Kudoed Authors
cancel
Showing results for 
Search instead for 
Did you mean: 

Show hidden controls as "ghosts" in edit mode

I occasionally hide controls on my FP and control their visibility programmatically during the execution of my program. The problem is that if I edit my UI and the control is hidden, it's very easy not to be aware that it's there and to accidentally overlap it, hide it or even move it off the screen.

 

To solve this, I usually try to save the VIs with all the controls visible, but that's not always feasible.


A better solution - LabVIEW should always show hidden controls in edit mode. It should just have some way of differentiating them from visible controls. This mockup shows them as ghosts, but it can also be any other solution:

 

20779iD19E3A04FFDC0A31

 

In run mode, of course, the control would not be shown. This is similar to the black border you get when objects overlap a tab control.


___________________
Try to take over the world!
40 Comments
Knight of NI Knight of NI
Knight of NI

> What if the effect, grayed out or otherwise only appeared with the move tool selected.

 

I don't think I would like stuff appearing and disappearing all the time (which is what would happen with the auto-tool). It's simpler to have a toggle.

 

Ideally, I would say that this should be a global system toggle, so that each developer can have their preference, but I'm assuming some people would want something easily accessible in the toolbar, so here's one suggestion which should cover this:

 

This would be a global setting, but there would also be a toggle on the toolbar. Whenever you open a VI's FP for the first time, the local toggle would initialize itself from the global setting. From that point on (until you unload the VI), the local toggle will control the behavior of that VI. The value of the toggle will NOT be saved with the VI, so that next time you open the VI, it will again read the global setting.


___________________
Try to take over the world!
Knight of NI Knight of NI
Knight of NI

Also, this should probably apply to hidden tab pages.


___________________
Try to take over the world!
Member

Good & Useful Idea.

 

But you shout can switch this view on and off

Member

have you every hidden a control within a cluster and try to get it back.  This feature would be great to show these.  If you have a hidden control you can at least find the terminal and click Show Indicator.  You can't do this with clusters.  I have to get a reference to all the controls within a cluster and use a property node to show indicator

Trusted Enthusiast

> have you every hidden a control within a cluster and try to get it back.  This feature would be great to show these.  If you have a hidden control you can at least find the terminal and click Show Indicator.  You can't do this with clusters.  I have to get a reference to all the controls within a cluster and use a property node to show indicator

Can't say that I have ever done that, but if I were to I would probably edit the cluster control (Advanced->Customize).  In the Edit menu of the Control Editor is the option to show all hidden controls.

Knight of NI Knight of NI
Knight of NI

For clusters, you should already be able to do this today even without customizing. The advanced sub-menu should have another sub-menu for un-hiding any of the elements in the cluster.

 

More specifically, one of the problems with cluster is that if the cluster is set to auto-grow, showing the elements would presumably make the cluster temporarily larger, which can hide other controls or expand the container which holds the cluster (another cluster or a tab control). For clusters, perhaps this can simply be accomplished by marking the cluster somehow (e.g. with a glyph or a halo).


___________________
Try to take over the world!
Active Participant

This idea is great, but it should be implemented with not exclusively acting on the Visible property = False, but also on a couple of special cases where controls are invisible due to other causes - for instance a SubPanel with hidden Frame and no content loaded.

 

/Steen

CLA, CTA, CLED & LabVIEW Champion
Member

Yes PLEASE! At the moment I have to implement "cleanup" code to restore the visibility of the controls I've been hiding.

Member

Pictures tell more than thousand words...

 

What would You think about this solution?

hidden_controls.png

No resizing, no confusion about inactive elements and universally applicable to all hidden elements.

 

Kudos for this idea!

Example Gatekeeper
Status changed to: In Development
 
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman