LabVIEW Idea Exchange

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

I saw this idea which I really liked and I realised that this would also be nice.....I do this type of 'insert subVI, delete broken wires' action all day.

 

error_wires.png

 

I searched I think what I am proposing is a little similar to this idea but I think in the difference with the idea I'm putting forward is that labview will only automatically delete a section of the broken wire when the 'short circuit' is sending data around a VI as well as through it!

 

The second part of the idea - where the 'merge errors' vi can be configured to appear automatically when two 'sources' are wired to one sink would be useful when you are parallelising subVIs on the block diagram. I'd also suggest that if this option is configured and the source wires are deleted (so that only one source is linked to one sink) have the merge error vi disappear!!!

 

I'll be gutted if I've wasted my time on another duplicate.....I keep not finding other peoples great ideasSmiley Happy

 

 

The LabVIEW forum has shown the constant need of a colorbox indicator that looks like an LED (round or square). Of course we can make our own, but maybe it would be easier if these would ship with LabVIEW.

 

 

Here are some example links. It comes up all the time! 😄

4 Color LED

Dimmer

labtris

I think this is about time that we can have more than 256 colors in our VI icons.

 

I would really like to have support for 24 bit images so this nice icon 24 bit icon example.png does no longer become this:

 256 color icon limitation.png

 

PJM

I normally have 32x32 png images on disk and have to copy and paste them in (and that doesn't always work well and has been reported).

I think it would be cool and fast if I could just drag and drop an image into the Icon Editor from disk.

 

I would like this image to appear as the top-most User Layer or replace the currently selected image (as per mockup below).

 

 

DD in IE.png

Currently on waveform graph, once a plot is named it cannot be deleted (it can be made blank, but it still shows in all pull downs).  For instance I plot 3 graphs, each having 16 plots.  I then refresh data and plot only on graph of 11 plots.  My new plot names show in the top of the pull downs, but all the previous plot names still show up as well (see attached screen shots).

Please expose a method to remove plot names (property to give array of existing names and property to remove name or all names).

 

The title say it all.

 

The Build and Strip Path primitive should be able to operate on array of path and array of string.

 

Polymorphic Strip and Build Path.png

 

PJM

I remember when I first discovered the "Show Item Paths" option in the "Project" menu. This is such a useful view, but for some reason we are only seeing the tip of the iceberg!

 

I propose that the project window be enhanced to support other useful VI properties too:


properties2.png

 

Among other things, this would allow us to very easily identify VIs (or controls, or libraries, ... ) with non-standard properties. (Have you ever revisited an old project and tried to figure out which VIs are reentrant, or inlined?)

 

What properties should be available?

  • Ideally, this view would support ALL properties for ALL project items ( - at least those that have a compact text representation).
  • If that proves impractical for some good technical reason then I'd suggest we at least get access to the Execution properties.
  • It would be great if we could choose which columns to display from available item properties. These columns could then be toggled on/off (just like the existing "Paths" column):

 

menus2.png

An added bonus would be the ability to sort by any column:

 

  • My preferred implementation would be to allow the user to click on any column name to toggle between ascending and descending view. (This type of thing has been suggested a few times for multicolumn listboxes...)
  • On the other hand, I'd be happy enough if this worked the same as it currently does with "Paths", i.e. using the "Arrange By" option (>> Right-click on a parent item in the project and arrange the child items by Name, Type, Path, etc)

 

I think this would be a BIG step in the right direction towards leveraging the existing project interface to provide some REALLY useful information.

 

Spoiler
If anyone is wondering about the "Runs On Error" property then you should visit this idea.

 

Add field witch shows the size of the array.

 

new probe watch window

 

So simple but so helpful Smiley Happy

In LV 2011, an asynchronous Call By Reference feature was added to LV. This feature added two new nodes:

 

    • Start Asynchronous Call
    • Wait On Asynchronous Call

It would be nice if there was a way to use the LV event structure to wait for the results of an async call. For example:

EventStructureIntegration.png

 

I am not necessarily  proposing this is the way to integrate the ACBR with the event structure, it is just one suggestion. Instead, I hope this idea can gage the amount of interest in some sort of event structure integration. If anyone has any better ideas or suggestions, please say so in the comment.

The LabVIEW Viewer would be a stand-alone application that allows for the viewing on VIs for someone who doesn't have a full-blown LabVIEW installation.  It would function similar to how the development environment functions on a 'locked' VI.

 

I've used 'VI Documentation' in the past, but this viewer would allow for live navigation, context help, drilling-down into SubVIs, scrolling through case structures, etc.

 

  

 

 

 

1) Add icon selection for Three Button Dialog.vi
  None,

  Hand/ Stop/ Error,

  Question,

  Exclamation/ Warning,

  Information, ect…
2) The current version of vi, Centers to Workspace (desktop). Make it center to caller.

 

no icon.png

 

info.png

 

exclamation.png

 

critical.pngquestion.png

 

abort.png

One of my pet peeves when using the Unbundle or Bundle by Name occurs when I remove or add an item from a cluster and LabVIEW attempts to find the item with a similiar name.  The behavior should always break when the specific item in the Unbundle/Bundle by name is removed.

 

More often than not LabVIEW picks the wrong thing and introduces programming bugs. 

How about this for a possible improvement.

 

It would be neat if there was a format painter button somewhere on the toolbar that acts like the format painter in a word processor, this format painter would copy all formatting information from one object (probably a FP control/indicator) to another.

 

Click on the first object, click on format painter and then click on the second item and viola! the formatting is copied over.

 

An example of this is setting the numeric format (which takes quite a few clicks to set the significant digits etc). I know its possible to edit properties of multiple similar objects, but this is a bit different.

 

Maybe this would work on the BD as well?

 

I think it would probably be possible to do this with JKI's Right Click Framework, looping over all the properties of and setting the destination the same as the target.

Hi,

 

when I have to rework a vi, i usually start by putting the existing code in a disable structure

and then start working in the disabled 'case'.

 

Quite often I end up trying to replace the disable structure with a case structure to test the new or reworked vi.

 

Now I have to copy everyting into a temporary vi, remove the disable structure, put a case structure in place, paste again and rewire iputs and outputs.

 

Please add the ability to replace the disable structure with a case structure.

With the three nodes aligned to Top, we get that annoying bend in the error wires. The spacing between Refnum and Error wires is one pixel greater on the Property Node than on To More Specific Class.

 

Align TMSC Terminals.png

 

Thoughts?

I frequently see people posting messages about issues they have using the application builder.  They report an error number and the text of the error description.

 

Here are some recent examples:

 

Error 1 while building in 8.2

Build Error, Error 6 occurred at AB_Source_VI.lvclass:

Get Error 6 about 50% of time when building Application

Build installer error code -12 while copying distribution

 

The error description always has a long path through numerous VI's that make up the application builder package pointing to where the error occurred.  But the description never seems to give any detail about what actually caused the error.  It is often too long of a file name, or too deep of a path that gave too long of a path/filename which the app. builder VI's could not handle.

 

It would be helpful to both the people who are having the issue, and to the people trying to help on the forums when they post their message asking for help, to have some information as to where to look.

 

Maybe that information is already available and I just don't know where to find it.  Fortunately for me, I don't think I've come across this problem.  One, I haven't need to build a whole lot of executables.  Two, I keep my project folders at the root level of my hard drive, so the initial part of the path is always short.  (e.g.  c:\ProjectFolder\......)  I know if you stored projects in a My Documents directory, the initial path is ridiculously long because of the way Windows locates My Documents on your hard drive  (e.g. C:\Documents and Settings\My UserName\My Documents\ProjectFolder in XP) so you've already wasted 40-50 characters even before you give the directory name for you project folder.

 

My request:  Let's show some meaningful information in the error dialog box for Applicaiton Builder errors that can help people figure out how to fix it.

In the current implementation, charts increment along the x-axis and waveform graphs have the array index linked to the x-axis. The y axis is graphing the values.

 

There are many scenarios where this axis association should be swapped. However, we cannot do it without resorting to xy-graphs and jumping through flaming hoops, significantly complicating the data structures.

 

I propose a right-click option "swap axes" which would have the following effect, depending on the object:

 

Charts (waveform, intensity) would have the y-axis labeled "time" (by default), there would be an optional vertical scroll bar, and the data would run up (or down) with time (instead of left or right). Everything else would stay the same, same datatypes, data structures, same definition of chart history, etc.

 

Waveform graphs would have the y-axis tied to the array index of the data, while the value is tied to the x-axis.

 

Often, we want the data simplicity of a waveform graph, but swapped axes. One (of many) example application would be an intensity graph with a cursor flanked by a narrow vertical graph on the right and a narrow horizontal graph below (See image). These two additional graphs are used here to interactively show the intensity profile along the cursor lines.

 

 

Currently, it is not possible to use a waveform graph for the graph on the right. We need to use an xy-graph and do some data gymnastics. With this idea implemented, we could use a plain waveform graph with swapped axes and simply graph a plain 1D array sliced out with "index array". Wouldn't that be great?! 😄

 

Similarly, we could also allow this for xy graphs where it is not as important, but would simply swap the way the data is displayed (e.g. the imaginary part along X for complex data). This could be useful too.

 

The ability to swap axes should probably only be available at edit time...

 

 

 

 

 

 

Message Edited by altenbach on 06-24-2009 04:49 PM

The current behavior of LabVIEW is as such:

 

UserEventsWithClusters.png

 

The pick list of event data strips the cluster, only allowing access to the elements inside the cluster. In order to manipulate the native datatype, you must reconstitute the cluster inside the event structure, a performance hit on large data structures firing at quick event rates. This is not to mention a messy FP.

 

I suggest that User Events preserve the clustered event datatype, allowing the programmer to access to the native datatype on the consumer end. The option to select only the element "Clustered Typedef.Array of I32s" of course still remains, but is not forced upon you. (Note that the below block diagram is NOT a direct LabVIEW screenshot... brought to you by trickery and a paint program. I clustered the cluster on event datatype [not shown] so that the event structure could eat the outer layer)

 

NewUserEventsWithClusters.png

 

My motivation with this suggestion is directly linked with my other post on the Big Typedef Issue.

Currently, it's not possible to build a 32-bit application using the 64-bit IDE. The work around is to write your code in the 64-bit version, and then open it in the 32-bit version to build the executable.

 

This idea is: Make it possible to build a 32-bit application in the 64-bit IDE.

 

An extension to this idea is: be able to build a OSX / Linux executable using the Windows IDE, and all various permutations of that (build Win exe on Linux, etc.). I would be OK with having to download and install some OSX/Linux libraries that would allow this.

Any time I create another Y axis for my plots, I always have to manually adjust the range of each axis to get the grids on both axis to line up in a pleasant way.  For example:

autoscale.jpg

 

It would be nice if I could make Autoscale take into consideration all the axis present on the graph in determining numeric spacing to give the best looking plot.