LabVIEW Idea Exchange

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

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

Hello all,

 

It would be nice Smiley Wink to be able to drag a control or indicator from a block diagram, to a front panel or a "control editor" panel.  

 

DragAndDrop.png

 

For the moment you can only Smiley Sad drag "objects" ...

 

  • From a front panel to a front panel
  • From a block diagram to a block diagram

 

It would also be nice to be abble to drag ...

 

  • Constants from block diagram to front panels (Creating then a new control)
  • Constants from block diagram to "control editor" panel

 

Thanks.

 

Manu.net

You can open a type definition by right-clicking a diagram terminal, constan, or front panel control, but it is not possible to get to a type def file just from a wire.  There are a lot of times where I'm working on a diagram that uses a type definition that is only exposed as a wire.  Right now, the process of getting to the type def is to create a temporary constant from the wire, then right click the constant.  It would be nice to make it easier to get to the type def.  And of course, I would like to have the same functionality for LabVIEW classes.

select.png

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.

 

 

Use case:

I have multiple (sub)vi's open or in memory with "Retain Wire Values" enabled, because I don't know in advance which wires I need to probe.

 

Initial State: 
If I probe any wire now, they will all show "Not Executed".

 

First Execution:

After I have run my code, these (sub)vi's will show their values as promised and the parts of the code that have not been executed will display "Not Executed". 

 

Now I have learned from my first execution and I made some changes in my code.

 

Second Execution:

If I would run for the second time now, I'll expect that my code will behave differently. This can mean that some code that did run in the First Execution did not run in the Second Execution and therefore would retain the wire values from the first run. In such a case I am not able to tell if a wire value is from the Second Run or from a First Run and actually "Not Executed" in the Second Run.


Normally, I will Disable and then Enable the "Retain Wire Values" option to clear the wire values, but this can be quite a hustle if you have a lot of vi's with this function enabled.

 

My wish:

I would like to have some kind of "Clear all retained wires" button or something that put all my vi's in memory with "Retain Wire Values" enabled in the Inital State, so they will all show "Not Executed" when probed.

 

This seems a simple and effective solution to me.

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?

Currently, the only native way to display a JPEG in memory on a 2D picture control in LabVIEW is to

  1. save to disk
  2. read from disk
  3. display

See: 

Screen Shot 2014-02-18 at 11.09.39 AM.png

This is not only silly, but slow: on a reasonable fast machine with an SSD, this takes almost a second!

A simple request: A VI that can go straight from JPEG binary data (other formats would be nice) to a 2D picture control. This is very useful for applications that download images from a server - a pretty common thing to do.

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.

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?

 

a trueselect function, more powerfull Smiley Happy

 

 

d_a.png

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

When building an installer to let an application run on another computer one should select all the installers of products used in his porgram. This can be really tricky, especially to new users, that don't know if a VI was included in package A or B or if it's already included in the standrad runtime.

 

Therefore it should be possible to hit a button, that parses through the Application and determines which packages are used.

 

I though of writing something like this myself, but I can't be bothered Smiley Wink 

You'd just have to parse the Project, check all the VI names and relate it to a table that contains information, about where a VI comes from.

 

If this is a duplicate post, I'm sorry.

It would be nice if under options that highlight execution speed for debugging was configurable.  It could also be not an option but placed just next to the light bulb icon.  With experience we become able to folloe the code much faster and having 2 or 3 speeds of highlight execution could save some waiting time.  I know that there are many debugging options already but sometines the old light bulb is easiest.

 

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

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).

Hi all,

 

I often find when programming with LabVIEW that I don't have room on my block diagram for free label documentation.  I find it hard enough trying to keep clean and tidy code and even harder document it well.  Free labels take up lots of room and I end up not writing good documentation because I don't have room for it.

 

My solution to this problem is a Documentation Node where you can write comments in a free label, minimize it and use context help to read it in the future.

Before:

Before.png

After:

After.png

scroll.png

 

Make both the vertical and horizontal scroll get enabled only when the diagram is not able to fit inside the screen.

hello,

 

(sorry for my bad english, i will try to do my best)

it would be very useful to have direct Property Node for decorations.
This would avoid wasting time and having to implement a complicated code just to handle the resizing of decoration.

 

FOND.png

 

 

original4.png

 

 

 

I open a vi with a different version of my current version of Labview,
I make some changes and I would simply like to save it by keeping its original version.

 

Nothing to do with "save for previous version".

 

"save for previous version" ... keeps the file, opens a new folder, saves the file in this new folder ...

then i need to copy the file from this new folder, overwrite my first file, delete the folder.


Please ...

 

When the source version is different from the current version of LV

 

something like this would be very convenient,


in this case, LV simply overwrites the file and keeps its original version

 

 

SR2.png