LabVIEW Idea Exchange

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

Sorry if this is a duplicate, I couldn't find any other that fit. So, I am often working with datatypes of various bit depth. I find it very useful to be able to tell if something is a U8 or U16 or I16 etc... at a glance. Presently I am just using labels to do this which is an okay workaround so long as I don't forget to do it. I would love the option to show this information by default much like the radix can be shown.

 

Current:

Capture.PNG

 

Suggested:

 

suggested.png

Right now Index a row / col from a 2D array is possible outside In-Place Element - as shown in Picture 1

 

Index-Replace 1D Array.JPG

But only one element index / replace is possible at a time inside In-Place element - as shown in Picture 2

 

Index-Replace In-Place.JPG

 

So it would be good if it is possible to index a row / col of a 2D array from inside the In-Place element structure. Only row index / col index could be allowed to wire without giving broken arrow. So one full row / col elements can be accessed and handled for any task.

Download All

Provide a way to save and recall sets of probes for a running application.  A developer could then provide sets of various probes that would help the end user.  The superprobe would remember the VI paths and locations in the block diagrams of the application's SubVIs and automatically load VIs from disk or monitor existing re-entrant copies in memory.  The superprobe would have a front panel layout, like a global VI, to look like a custom dashboard of important data values in the applicaton.

Please provide option to show list of running VIs in the warning dialog box given in the attachment while closing the project

Compound arithmetic allows you to invert inputs or outputs. I find myself often checking for a string or path to NOT be empty. It would be nice to be able to invert the output the "Empty String/Path?" function instead of needing to wire up the additional "Not" function. It would look kind of like this:

Empty String Path NOT.png

Thanks!

Please allow value signaling for the boolean button with latch mechanical operation.

Breakpoints are great for debugging.  But...I've never wanted to share them with another developer, and I've never liked it when they add the dirty dot to code that I haven't otherwise changed.  This can lead to unnecessary code changes which can add hassle to source control, and it can lead to other developers unintentionally inheriting your debugging breakpoints.

 

How about an option to manage breakpoints separately from source code, perhaps similar to how compiled code is handled?

We often do this
gnilsson_0-1613943616766.png

Why not have a right click option, use default if unwired, like on case outputs

gnilsson_1-1613943754973.png

 

It will be better to have a quick view of different cases for a case structure from which we can remove unwanted cases, like disabling break points using breakpoint manager. Its tedious to click and remove each cases from case structure when we have huge number of cases wanted to be removed as part of maintenance project.

In my block diagram, I may place a cluster by icon on a bundle by name. If I (right click) to replace that cluster with a different cluster, the new cluster is fully exploded. This explosion can cause my structures to resize to accommodate the new cluster. I would like for the new cluster to be it's icon (if the original cluster was an icon).

As it is now, the Concatenation tunnel mode only works on arrays.  It should work on strings too, like this:

tn.png

It would be useful if a special free label existed on the block diagram and/or front panel whose contents would be kept in sync with the contents of the VI description. For brevity, let's call this a Description-Linked or DL label. The screenshots below show an example.

 

1. The DL label shown on the block diagram

DL label 2.png

 

2. The DL label shown on the front panel.

DL label 1.png

 

3. The DL label shown in Context Help

DL label 3.png

 

4. A possible mechanism to show the DL label on the BD and/or the FP

DL label 4-edited.png

 

Suggestions

  • The DL label should have a distinctive background colour that cannot be changed (could be any pale colour)
  • It should be possible to show the DL label on both the BD and FP, only on the BD, only on the FP or neither in the BD nor the FP
  • Screenshot 4 shows a possible mechanism to show/hide the DL. There may be better mechanisms out there.
  • Selecting a DL label on the BD or FP and pressing DELETE (like when deleting a regular label) hides the DL label on the BD or FP respectively. Equivalent to unchecking one of the checkboxes in screenshot 4.
  • The two settings for showing/not showing the DL on the BD and FP should be stored within the VI. The settings should be preserved when creating a 'Save as...' copy of the VI.
  • It should be possible to independently resize and move the DL free label instance on the BD and/or FP (the size and position of the rectangle is not synced). Notice the size of the rectangle isn't the same in screenshots 1 and 2.
  • The DL label has no influence on whether other free labels exist in the BD or FP. Any number of free labels are still allowed.

This idea would ease the process of creating and maintaining well-documented code

  • When using a subVI inside a caller VI, the Context Help documentation is extremely useful (it may be the only documentation available if the subVI is part of a PPL)
  • When editing or inspecting a VI, the Context Help documentation is often not at hand. What is available at a glance is often a big free label comment somewhere on the BD or FP
  • As the VI is edited, the big comments on the BD and/or FP inevitably become out of sync with each other and with the Context Help
  • The DL label introduces the concept of having a 'master' documentation source, or a single source of truth
  • At Renishaw UK, some of us use an in-house scripting tool that searches for a free label containing the first word 'Description' on the front panel, and copies the remainder of the text into the VI Description. It's a useful workaround, but this idea would remove the need for such workarounds, and would add the benefit of two-way syncing (editing the VI Description to update the comments in the BD/FP).
  • drjdpowell suggested a similar idea (but not identical) in a comment to idea Subdiagram label for Block Diagrams too (screenshot below).

 

DL label 5.png

 

Thanks!

What is wrong with this VIs diagram?

 

Broken arrow.PNG

Nothing! It's a broken dependency:

Broken dependancy.PNG

 

It would be nice to see the difference without having to open the error dialog:

 

Broken Dep.png

 

Graphics should be improved...

 

The normal broken arrow should have priority over the other. First fix the VI, then the dependency... Wouldn't mind two icons, one for broken VI, one for broken dependency.

Hello,

 

Maybe it would be difficult to implemented it in a user friendly way, but the proposal is related to structures like typical event handlers or state machine handler.  This "typical structure" is a while loop with a couple of shift registers with an included case structure (handling all events or states).  (I know it's not correct what I write, "confusing" an event handler with a case structure, but let me address both with the name "case structure".)

A usual situation is that in most cases, the value of a shift register is "forwarded" from the old value to the new value, except in a couple of cases (where the value changes).

For "output tunnels" in case structure you have the (very useful) option to use the default value (although an optional settable default could be extra useful?).

The idea proposed here is to have an additional option "keep shift register value", so you don't need a lot of wires going from left to right (maybe with some corners to go via the upper or lower part of the diagram).  Of course, a difficulty is that it would be a possibility in the combination of an output tunnel and its connection to a shift register (but I believe LabVIEW can handle already more complex tasks...).

The main goals are:

    - keep case diagrams "clean"

    - focus case diagrams on "changing things"

    - because of the previous two: simplify programming (and formatting - which is sometimes taking time in graphical programming environments).

(If it's not clear, I can try to make a clear example.)

I do this a lot:

ref1.png

I'd rather do this:

ref2.png

I can't find an easy way to edit the value a set constant on a block diagram or event a set control on a front panel.

Currently I do something like this :

edit value of set constantedit value of set constant

The only option from the right clic menu is "empty set"... can't event insert / remove like in an array 😞

The right click, find options are great but limited. I would like to find events that are triggered by a given control/indicator; this is hard if you have many events and some handle many triggers. Currently I have two less than ideal work arounds.

 

First work around is a text search. It gives a lot of irrelevant data for the results I want.  

Second I begin the process of adding a new "fake" event, and guess at what type of trigger the control is using (mouse down?, value change, etc.) If I guess right and it is being used I get a warning saying it is used and the event number (golden but often off by one because it counts the case I am pretending to add). Again if I guess the wrong type of trigger I get no help. 

 

It would be great if there were any events that were triggered by the given control, that would be added to the list of options under the right click find (and not show up if none existed like find local variables etc.)

I don't like wasted space. I see a good deal of wasted space in a cluster array when the labels are shown. What if we could size the clusters optimally and still see the labels by drawing them for the first clusters content. 

Taylorh140_1-1586275414310.png

 


In my opinion, it's worth adding the option to pin the drop-down palette in the pop-up menu. It may look like this.

Now we have:

Obecnie.png

 And after modofication will be:

Z nagłówkiem i pinezką.png

A Diagram Disable structure lets all the code that isn't inside of it execute but not what is inside of it. I think it would be helpful to put a structure around a snippet of code and execute only what is inside the structure. I usually copy and paste it into a new vi but it would be helpful to have that functionality within the vi i'm working on.