LabVIEW Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

Array To Cluster Function, add Type to Convert Cluster

 

I rarely use this function, but when I do I always end up using Variant to Data function for my Cluster Type.

So I would like to add a Type terminal to convert cluster type.

 

111.png


If Type terminal is unwired, this function work as it in current version.

 

If it is wired then it will convert to cluster type, and further it can also be used to define cluster size. So this way we can adjust cluster size dynamically if cluster definition changed.

 

Thanks,

 

222.png

If I'm the first to post this Idea then I'll be shocked.

The Idea is simple. We all love programming in LabVIEW, and I'm sure that we've all at one time or another had a colleague, friend or family member ask if we know how to do something on the PC. The immediate thought is I don't know where to get the software to do that, but I could write a simple LabVIEW app  in a few hours that does the job.

E.G hunt through someone's PC and move all of the jpg files over a certain size to a specific location so they can easily find their holiday snaps.

 

You can't create this simple function for them, because if you do, and build an exe, they still need the Runtime engine.

 

Surely for REALLY simple stuff (File IO, basic comms stuff in the Base LabVIEW edition ...) - not DAQ or anything like that it is possible to create an EXE that INCLUDES the runtime components that it needs and is stand alone.

 

This would open up LabVIEW for the use of making quick gadget like apps for the office as well as test and measurement.

 

I can't se how this could be a bad thing.

If you wanted to use a lot of functions from the same palette, you have to either keep going back through the context sensitive Replace/Create menu or manually search back over to the palette through the Functions palette to get to the functions you need.

 

Wouldn't it be nicer if we could pin that palette down directly from the context menu?

 

Ed.png

 

 

If this has already been implemented in LabVIEW 2012, give this idea a miss!

I inherited lots of VIs with complicated terminal connectors. It is a challenge to determine which terminal is associated with a given control. 

 

Why not highlight the associated terminal when a front panel control has been selected?

 

In other words, currently when I select a terminal, the corresponding control is highlighted. I'm proposing that it should also work the other way -- when I select a control, the corresponding terminal gets highlighted. 

 

I have just figured out a workaround, but it's clumsy. I can temporarily delete the control, observe which terminal goes white, and then immediately restore it with Control Z. But my proposed solution would be cleaner. 

 

Thanks

 

Well as the title says...

 

In the string constant you are able to make a scrollbar visible but this is still inconvenient when only see 2 lines of your whole string when you have a string constant of 50 lines or so... and you 9 out 10 times you don't want to create a bigger field because it messes with your diagram.

 

Therefore a small popup with a only a large textfield would grately simplify things.

 

I came up with this idea when I was writing a error message and there wasn't much space to type the string in, I also had this, http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Need-Edit-Window-for-New-Cluster-Constants/idi-p/1208295, idea in my backhead.

 

What do you guys think?

I feel I am the only one who thinks the Front Panel is archaic.  I would like NI to develop new controls. e.g. left/right/up/down arrows to name 1.  I would also like NI to provide a minimum of 5 different styles of controls, or allow us more flexibility to design our own.  I'm so tired of the button and control selection looking so "yesterday".   NI has done such a great job at updating the diagrams, but I feel the FP needs Much Attention!  Please post your thoughts on this (agree or disagree).

I want to have the possibility to use a probe directly on an iteration terminal.

When using a loop (for- and while-) I sometimes would like to see how many iterations that have past since I started. This is easily obtained by using an indicator connected to the iteration terminal or using a probe on a wire from it, but if I forget to create an indicator and I don't use a wire from the terminal I think it would be great to just right-click on the iteration terminal and create a probe.  

Sometimes, the case selector label gets in the way of wires.  It would be nice to be able to drag the label left or right.

 

annoying.PNG

 

 

better.PNG

When  we are resizing the window if it shows the size means it will easy to make User interface as shown

Resize window shows.png

Currently, digital displays are free floating and are not the same height as their corresponding plot in the legend.

 

before.PNG

 

Also, when an additional plot is added the displays no longer line up.

 

added.PNG

 

I would suggest including the digital displays inside the Plot Legend.

 

embedded.png

 

It could be a property of the graph so the user could choose to turn the option on or off

 

properties.PNG

 

Note: The current method to have a similar effect is to lock the entire chart so that it cannot be edited (KB 4VQDROPI)

Hi,

 

I suggest that radix is always visible when the numeric display format is other than decimal. Is this number decimal for instance?:

 

Number_188.png

 

Well, it was hex:

 

Number_x188.png  ... -> ...  Number_392.png

 

Basically you'd know that if there isn't a radix visible, then the number is decimal. It should still be possible to show radix for decimal numbers as well. This should be the case for both constants and controls/indicators.

 

Just one of those little things that would enforce a minimum of documentation.

 

Cheers,

Steen

It would be nice if the conditional tunnel would be polymorphic.  They only accept Boolean as condition.  Please add the error cluster, like it is available on Case Structure.

PolymorphConditionalTunnel.png

Hi.

 

I'd really like to be able to select the entire top-level cluster in an event structure, if event data is a cluster:

 

Top-level cluster.png

 

I know this have been brought up in numerous forums over the years, but I feel it's being ignored somewhat by NI? It usually gathers quite a few positive acknowledgements from other users, but I think it's about three years since it's been brought up in the idea exchange. It seems so easy to implement and would greatly simplify many event structures. So forgive me for duplicating something from countless other places, but I think it deserves a second (or ninth or whatever) glance Smiley Happy

 

Cheers,

Steen

More Lable.PNG

 

It seams like I usually right justify my control lables, left justify my indicators and center justify lables for constants on my block diagram.  Why only one option?

CaseError.PNG

Would be nice to have an element selector with error case. No need to wire an unbundle element to connect the error code, then the Case structure becomes like a numerical values case selector.

I am a habitual right-clicker, it is an ergonomical method to perform many tasks , so long as the right-click menu isn't too long and is configured well.  When I select multiple BD objects I would like to have more options than 'Properties' from the right-click menu.  In particular I would like to be able to Clean Up Selection and  Remove Broken Wires from Selection.  Other possibilities include Align, Arrange, Group and Create SubVI from selection.

 

Disclaimer:  One ulterior motive is to provide an alternative implementation for Remove Broken Wires (Ctrl+B) so that the keyboard shortcut can be freed for its much more natural use as Bold.   Of course I am advocating a selective approach where it is limited to a selection.  IMO the VI wide implementation is more trouble than it is worth, and certainly is not so useful that it should occupy prime keyboard shortcut real estate.  

Message Edited by Darin.K on 05-07-2010 09:53 AM

When selecting properties from the Y Scale, I would expect to get the properties window opened for that axis.  But no, you get the properties for the x-axis.  But I distinctly selected the properties from within the Y Scale.  See image below.

 

My suggestion is to open the properties window to the axis where the selection was made from.

 

 

Sometimes I want to insert a unconnected Sub VI on my panel into a some wire. I always end up deleting and reconnecting the wires to insert my Sub VI.

 

I miss a solution to quick insert a VI into a wire without deleting and reconnecting the wires.

example.jpg

I know we already have the option to use the QuickDrop with ctrl+I, but I miss a solution to insert a VI (that already exists on my panel) into a existing wire.

What about clicking on the wire and draging the Sub VI while pressing crtl+i?

When doing UI work, it can be quite frustrating rewiring hidden controls to the connector pane. You have to go to the block diagram -> Show Control -> go to front panel and wire it up then hide your control again.

 

I have seen a number of ideas proposing ideas such as hidden controls always being visible in edit mode or being able to link block diagram controls to the connector pane which I agree with and would also solve this.

 

My suggestion is that when you select the Wiring Tool on the front panel or click on the connector pane (to wire up a terminal) all the hidden controls would become partially visible and become connectable to the connector pane.

1.png

At present case structures have options (right click) to create multiple cases if enums are attached to the case selector. If someone want's to reuse the same case structure with less number of items in a new enum, one has to manually delete one case at a time. Having an option to select multiple cases to delete, or automatically delete broken cases would be desirable to speed up things.