LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

Case Structure accepting Clusters

I noticed that the calendar i.e. "Set Time and Date" or "Time Stamp control" does not work properly if it is accessed from a SubVI window. The calendar is jammed until the user clicks the main VI from the Windows toolbar. This is at least the case with LV2010 sp1, Win7.

My guess is that the calendar opens to the main VI even though the SubVI is active. This is bad if you want to make a SubVI GUI window where the user can set the date. It is possible to avoid the problem by making a SubSubVI for setting the date, but this is a more or less time consuming depending on the programmers skills.

I suggest that the calendar should be made accessiable from a SubVI if the “Show front panel when called” setting is enabled from the “Window appearance”-properties of that SubVI.

VI, SubVI and SubSubVI that demonstrate the problem as attachments

Download All

View All (4)

To compress the BD add a vertical sequence like structure where all frames run independently and in parallel. As soon as inputs being used for a given frame are present, that frame executes. I foresee some input tunnel properties where a tunnel could be assigned to one or multiple frames. Tunnel props could authorize a frame to start execution even though all data hasn't arrived at the structure. This structure is just for visual compression in the BD.

version icon

NI engineer should sort and gather some general instruments driver into a driver VI. It would be a smart Labkey. NI can define a standard command used text script just same as SCPI for general instrments such as DC/AC source, meter, oscilloscope, E-load........ For oscilloscope sum VI, we can just use NI standard functional command, the Labkey can as a interface to find which model or vendor oscilloscope connected and translate the command into the connected instrument command. so NI can reduce drivers quantity and the user can not care for the difference of the command of the different equipment model and vendor. If the developer replace the model or vendor of equipments with others they should not modify their software. The Labkey driver VI should be smart and adapt the change automatically. Just like as .NET frame.

paste format

Change Error Cluster indicator

While I was editing one of the subvi’s in my project I discovered that the wire to the ErrorCluster indicator was gone.

When this is not seen during, editing it will stay unnoticed until there is an error. You never know when this will be.

This will be solved if an ErrorCluster indicator that is not connected will result in a broken arrow.

It can also be solved to set the default value of the ErrorCluster indicators in ‘errclust.llb’ into:

Hi,

1. If I enter an empty path to the next block: (check if file or folder exists.vi from file IO advanced)

I get a true output since it only checks if it is a path but not if it is an empty one.

Since I'm not sure if this is a feature or a bug I sent it here to the idea exchange.

2. If I have more then one version of LabVIEW open and I run a vi/project from the command prompt by writing the correct path to LV exe version that I want and the path to the file I want to run LabVIEW won't open the file in the version I asked it to but rather in the version of LabVIEW which was last opened.

3. The tags for projectItem of builds is different for each build while we all need just some basic access to the name and version tags. Make at least those tags common between all builds.

Dror.

When you need more room on the block diagram or front panel, you can control-drag a rectangle and white space is inserted.

http://zone.ni.com/reference/en-XX/help/371361E-01/lvhowto/adding_working_space/

While that is a really useful feature, it tends to create bent wires and insert unwanted whitespace. More than 90% of the time, what I really want is inserting horizontal space or vertical space.

In the two pictures below, I'm control-click dragging to create more space on the right hand side of my for loop. Before I do this, my 'y' control and '3' constant are nicely aligned, but after control-click-drag, unwanted white space has been inserted. This problem gets really yucky in large, especially ones that are longer than one screen side, but nicely aligned vertically.

I propose that in addition to Control-drag creating rectangular white space in a block diagram, Control-Shift-drag would create only horizontal or vertical white space, essentially locking the rectangle to either zero height or zero width. As it stands, it's a pretty manual and tedious process to move the mouse pixel-by-pixel until I see the dashed lines disappear.

Download All

One of the common uses for the compound arithmetic node occurs when you are refactoring a VI, and realize that you need to, say, add or multiply three numbers instead of just two. So, you replace, say, a multiply node with a compound arithmetic node. The wires all stay corrected which is nice, but the default mode is "add", even though you just replaced a multiply node.

With just a teensy bit of added intelligence in the diagram editor, the mode could be set in the compound arithmetic node, based on what it was you just replaced.

View All (1)

POWER CONTROLS

I´d like to suggest an easy way to create customized controls without inserting VI´s in invisible frame subpanels to do it. It will be like a customized "Power Control" with one VI to handle basic properties and methods. Every time you copy and paste a new customized control LABVIEW INSERTS a reentrant VI to handle this kind of controls (SubVIs) with no need to insert a invisible subpanel and putting a VI to run on it. I believe that the control VI must have one standard event structure to handle it (resize events, mouse in, mouse out, refresh, and other standard events related to basic controls or indicators).

//Commenting areas of code

To be able to select a part of the code in the block diagram and have a tool to make that all a comment (in grey colour and with shadings or something) that is it would be there but completly inactive.

It would work like commenting a piece of code in any other programming language.

It would be useful because sometimes you don't want to actually delete that piece of code. You just want to run the rest of the code as if that part of the code was not there.

Obviously the respective wires would be affected and go into the commenting area.

View All (2)

LabVIEW Idea Exchange

Case Structure accepting Clusters

Straight through error connector for nodes in the timing and some other pallets?

Double Click Call-by-Reference Node

Calendar to work properly from a SubVI GUI window

Create vertical sequence like structure where all frames run independently and in parallel to clean up BD.

version icon

Labkey - smart driver Vi - the interface of the same category instruments

Numerical control accept formular expressions

paste format

Change Error Cluster indicator

Display the connectors of blocks in the function pallet with info without using help

Empty path recognized as a existing file/folder + LabVIEW starting in wrong version + builds

Control-shift-drag to add only horizontal or vertical space to a block diagram or front panel

When replacing an arithmetic node with a compound arithmetic node, select the correct operation mode

Being able to clear the history of Import Shared Library Wizard

POWER CONTROLS

Error connectors at the bottom of a property node?

Shift Register for Stacked Sequence Structure?

Separate options for default position for controls and indicators labels.

//Commenting areas of code