LabVIEW Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea
Builder should automatically attach version of LV to EXE so it can be seen in Windows Explorer. So you can always ask unexperienced end user about version. I drove 1000 km with wrong version of LV on my laptop... Upgrade to new version is not always straitforward... And I always forget to set version information manualy...

While and for loops should have diferent border color or texture whether they arre running or not. In 2009 there is significant improvement in

probe window, but stil it would be nice to know status of a loop without probing.

Whenever I built something (executable, installer) I want to go to the output location to change some filenames for distribution (e.g. I change "volume" folder of the installer to contain the name and version in the program name), zip things up to post on the server, etc.

 

On the final progress screen, where it tells me that the built has finished, I would like an additional button to open the target folder location(s) in explorer (similar to e.g. when downloading a file using IE) while dismissing the dialog.

 

Right now it says:

 

"The build is complete. you can locate the built at <very long and hard to remember path spread over 3-4 lines and that cannot be coped/pasted from this dialog anyway>."

 

Well, if the builder is smart enough to know where things are, why can't it just directly take me there as an option? 😄

Most of applications we write in LV are contained inside of a project. Saving it to disk creates a lot of files (.lvproj, .vi, .ctl, .aliases, etc) and subdirectories. This is convenient when you want to copy one VI or control to another project, but very inconvenient when sending this project to someone. In this case you have to create an archive to put everything together. Make an option to save all items contained in a project in one file.

 

Making a Windows Explorer plugin to automatically open such files as directories would be also a nice addition in this case.

 

Thanks

Labview implements lots of functionality in the right click menu, resulting in large and deep menu hierarchies.  Often I want to select multiple items, but the context menu disappears after a single selection requiring me to go back to the original item and renavigate the menu tree.  That's a lot of repetitive, fairly precise mousing.

 

I'd like to have a hot key that prevents the context menu from disappearing after I select an item.  For example, if I held down the Ctl key while deselecting "Label," I could immediately move down to "Caption" and select it, making the whole process much easier.

Right now, you can only set a single variant attribute at a time.  You can get "all" variant attributes, but it would be nice to be able to get a specific "group" of them.  (the same could be said for delete)

 

From a programmer standpoint, the nice way to accomplish this would be to wire in an array of strings for the variant attributes you are interested in, instead of placing the function in a for loop.  It would also be nice to wire in the data type for all of those attributes, so you don't have to call the variant-to-data.

I like the glyphs in the project explorer window that indicate the scope of each vi.  I would find it extremely helpful if glyphs were added to indicate a VI's override status.  (Must override, overrideable - normal dynamic dispatching, and not overridable - static dispatching)
Add a Master Tab Page for those controls / Indicators that need to be accessible from all Tabs.  We could designate a place - say across the top or along the Right - where all Master controls / Indicators would reside. Also a good place to put Company or project logos.  The master tab should be defaulted to Transparent to inherit the other Tab colors.
In a project a lot of times I want to know all the VIs that are using a particular VI. I may want to open all these Vis up or do a replace all on that VI with a different one. It would be nice if after I right click and choose "find callers" I can do more than just jump to one of the VIs that I double click on.

In the palette you can designate a VI to "Place VI Contents" (used to be "Merge VI" in LV 7.1).

I typically drop most VIs from the Project Explorer now.

It would be handy to designate VIs in the Project in the same fashion, so you could drop the "VI Contents" from a Project selection.

 

I admit I only use "merge VIs" about 0.01% of the time but today was one of those days.

 

A multiple case structure is always difficult to navigate to and understand. A toggle option like the below will add clarity

 

idea.JPG

Please note the Case summary text option suggested in the right of each case in this view. In the present view you have to navigate to each case to get a glimpse of what is done. A simple summary like below will add a lot of clarity and help in understanding what is actually being wired in the subsequent cases (just an example)

 

 

notes.JPG

 

Will be helpful while dealing with multiple case structures isnt it?

case.PNG

 

Can the case selector be centred always irrespecive of the drag.  I feel the justification will give the block diagram uniformity.

It would be nice if it was possible to add another 'Reentrant' setting.

This setting would make sure VI A always uses a specific instance, where VI B uses another instance. Sort of a single parent sub-vi.

This would allow for look-up VIs that have a seperate set of data per VI that is calling them.

 

So you can store some variables that are only valid in a single VI and if another VI is calling the same VI it will be calling a second instance and gets other variables back.

 

Ton

LabVIEW still only gives access to Windows95 color pallette.  With XP, themes came into play and there are numerous other colors used by those themes.  Since NI doesn't provided system-like controls for their non-system standard controls, many of us attempt to make it "feel" like a system control.  Unfortunately, the standard system colors are in the themes (for example, the border color on the system numerics and strings).  I can figure out what the color is for the current theme, but if the user is using a different theme, the color doesn't automatically change.

There needs to be a better way to select nested objects.  Have you ever tried to select a string within a cluster within an array?

 

How about the default selection being the top level object.  Right-click to select the first nested objects.  Then Right-click on down through the hierarchy.

Having now gotten used to the new icon editer, it is a fantastic improvement on the old one: templates and layers are awesome.

I do however miss the line tool + shift key drawing a 45 degree line.

Also, I think that a user-configurable 'development colour' for the transparent colour might be useful. I find the white and grey checkered pattern doesn't stand out much - if I could set it as some garish luminous colour then I could see what is transparent as I draw the icon.

 

This development transparent colour might even be stretched to the front panel colours - if one uses an old style cluster box or similar with a transparent border and fill (for aesthetic reasons) then it can be a little trickey to find the border to drag it around. (This might be better suited to a new idea if anyone agrees)

I'd love to see a handful of built-in false-color colortable choices for the Intensity Plots.

 

I know there's programmatic control over these things - I wrote my own 4-5 years ago. But the black-blue-white should be one of several common selectable colorschemes.

 

I labeled my own as:

 Greyscale B->W

 Greyscale W->B

 X-Ray

 Yellow Hot

 Rainbow

 Rainbow #2

 Fluorescent (green)

 Blue Red Green 

 Planet Earth

 

Perhaps one of the front panel (and Property node please) off of the Z-Axis submenu, listed by title.

 

I also have the ability to invert top/bottom or choose the color-inverse (photographic negative) for even more colors. 

 

Attached is a sample of some common colortables I routinely use.

2nd attachment is a snap of the VI I use to create the colors based on colortable constants.

3rd attachment is my messy but functional code (Block Diag of attachment 2)

 

Suggestion

 

I want to make a suggestion.

 

I often want to use 2 or more controls to trigger the same event, because sometimes the code for one control is only slightly different then for the other control. An example of this is a motor that turns left when a positive speed is entered and right when an negative speed is entered (See Example 1). To make sure my code will stay simple to read, I can easily "group" them in this manner (as in not coding 100 nearly the same events).

 

Please keep in mind that these are simple examples. For my coding I have to do more then just entering a constant. I have to do complex calculations for one control, maybe read a sensor for another and do nothing for a third. So here it is mostly not possible to use sub-VI's.

 

My suggestion is to make it possible to wire the control-reference from the event structure to a case-structure (See Example 2). This is not possible at the time. I managed program a decoder to find out what control was activated. But it feels dirty and takes away a lot of space. Being lazy, it would be great if NI could make it so that the Case-Structure would automaticly list all possible control-references.

 

Hope you guys understand what I mean. Study the 2 examples, I think they will make it clear. 

Thank you!

 

" ... when a TDMS file is open, LabVIEW will create an index structure in memory that is used for random access to the file. The built-in LabVIEW TDM Streaming API will always create this index, even if you're just writing." - Herbert Engels

This feature will cause an apparent memory leak if your program periodically writes to a TDMS file over a long period of time. 

 

Feature Request: 

Disable indexing option for "TDMS Open.vi"