LabVIEW Idea Exchange

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

Could i sugest that two new tabs be added to the NI Idea Exchange web page to further separate out  from the now large, 266 pages of ideas, those that are:

a) Declined ideas

b) Implemented  / completed Ideas

This, i believe, returns the group focus to only those new sugested ideas. (not a mixed basket idea listing) 

 

I sometimes use arrays of classic frameless colorboxes to quickly display a color table.

 

Unfortunately, the minimum size of these elements is 5 pixels :(, making a 256 element color ramp 1280+pixels wide, showing redundant information in 5 adacent pixel columns each.  If we display the color ramp vertically, it would not even fully fit on a common 1080p display!

 

This makes it too wide to correctly display them in the forum and forces a size reduction that makes all other text and diagram code illegible.

(Yes, we can right-click...open image in new tab, and click the image to display it 1:1 (in chrome), but that's more work and not everybody knows that)

 

It would be perfectly OK if we could make these elements only 2 pixels wide (or high), making the array display a much more reasonable 512 pixels and keeping the front panel to a more reasonable size.

 

 

Idea summary:

The minimum size of the classic colorbox (frameless) should be 2x2 pixels (or even 1x1?) Currently it is 5x5, i.e. too big.

 

 

The "%s" format specifier currently reads characters until a space, CR, LF or tab is encountered. This can be quite cumbersome in some cases:

 

Stirng format specifier - old.png

 

It would be nice to have an additional text format specifier to read text until a CR or LF is encountered:

 

Stirng format specifier - new.png

 

An even better solution might be to read text until a character from a user-defined character set is encountered (in this case 0D=CR; 0A=LF; 09=TAB):

 

Stirng format specifier - new 2.png

When using a Tab Control (Container) it would really be great to group icons so they do not float around the large container if used in combination with a case statement.  Being able to group icons and anchor them at a location would really make life allot easier.  This grouping should not alter position or arrangement during a clean-up operation.

 

Thanks!!

Okay, poor title but I can't summarise any better than that at the moment.

 

So I'm sure many of us use the old trick of creating a re-entrant VI so we can use a loop structure within the VI (that usually executes only one cycle per call) to allow us to store persistent (static) variables within the VI between calls. The problem with this is that all the headaches that come with a re-entrant VI in terms of not being able to run 'with the lightbulb on' to debug then arise.

 

Most of the time, I only need a single instance of this VI, so how about an alternative to re-entrancy like 'allow statics' that gives me the stored info but only allows a single instance to be used, and gives me the ability to run 'with the lightbulb'?

 

Of course, I have made an assumption that limiting to a single instance would make this feasible without major architectural modifications. If not then this is one for the scrapheap.

It happens quite often that to change my code I need to get rid of a block and just wire the input with the output.

Currently, we need to delete the block and then rewire the input with the output. That's a bit long, wires are dashed which sometimes does not help selecting them.

 

What if we could replace the block by a wire instead of another function (in case only one input and one output are present)? Or even better use a shorcut for this!

 

Thanks!

Pierre

I would like to be able to create on-screen instructions with Arrows pointing to details in a photograph. I was hoping to use the arrows from the decorations pallet, but I am dissapointed to see that they do not exist as programmatic objects, and therefore cannot be controlled using property nodes.    Might I suggest making them into indicators, of a sort, so that they can be controlled by the programmer?

In some cases, it would be very useful to be able to copy and paste the text of the selection box.

 

QD Copy Paste.jpg

If the Label Position is changed from default position there should be the option to retain the position, because finding the label in a very huge block diagram code is difficult as label is the only identification for the item

 

once the Un-Initializing the array(1D or Multi) Placed ,we can not select the Number of element to Enable.

byproviding the below option we can easily Enable the Elements in any array dimention.

 

Enable Elements.jpg

HI

When I use event structure

and I have quite lot of cases

adding new case causes I have to connect all input and output terminals

which doesn't change in that case.

 

The idea to is add a functionality to wire between input and output terminal

inside the event (and case) structure to "autowire in all cases".

In example I dont need to connect the wire in all cases but I eventually need

to disconect the wire in one of them.

 

It is important for references and other signals which can't be unwired and left with default values .

 

 Thanks

 

Currently the build specification name, the output filename and output path of the build is hard coded on the "information" page of the Build specification properties window.

 

It would be a HUGE help if optionally the version number from the "version information" page could be added to the build spec name / filename / path. Right now unless I continously change the filename and folder path the project explorer overwrites the existing build and just by looking to the file name I dont know which build is this exactly.

 

find.png Arrow.png PE.PNG

Some times it is not easy to find the actual edited vi in the project window.

I would recommend to add an additional entry in the icon pop up window (front panel and block diagram window) that finds the actual vi in the project window.

It should:

  • open Project window and brings it in front,
  • jump to the actual vi in the Items view ad selects it

for a very long period in a graph, it's be difficult to analyse the period and if the signal depend of meteo evenement, we don't have the time. I purpose to have the possibility that have the time in a graph in a date and clock.

date sur courbes.png

Hello,

I use several curves having different units. For it, I am obliged to create a graph for unit. Any curves on the same graph would be more practical.

multicurb.png

good.png

 

Sometimes I have to turn on some front labels of controls or indicators to see what the names of them are. It would be nice to have the

label name show up in the help window as you hovered your mouse over the controls and indicators.

 

Just a thought...

Please let me know if something like this exists, but I can't seem to find anything.

 

What I want is a tool to automate some of my subVI building and implementation. There are a few repetitive things I do during development that would be optimized if I was able to build a custom macro to complete these things with some simple customizing inputs.

 

Here is my scenario:

I have API for each module in my application. Each API VI passes an "Action" enum along with varient data. The "Action" enum is a type-def and the API uses the module's queue reference to pass the action and data to the main module VI.

Every time I want to create a new API VI for a module I have to complete the following steps:

Open a previous made API VI (or template API VI if I want to make one)

Save As my new API (i.e. ReadData.vi)

Open "Action" type-def enum

Edit Items of enum

Add "ReadData" option to enum

Close "Action" type-def

Change Action in API to ReadData

Change Icon in API to match

Save and Close

 

The only changing variables in my situation are:

Which module for which to create the API

Action name for th enum

 

 

This seems like the ideal application for a macro similar to an excel macro or other languages.

Thanks for reading!

Grouping objects on the front panel is helpful to avoid inadvertently destroying a UI's layout.

Unfortunately it comes at a cost: if you want to access block diagram counterparts of any of the objects in that group, you have to first ungroup them, select the object of interest, right-click and select what you are looking for, go there... and hope you won't forget to regroup the objects when you are done.

Surprisingly, you can actually access an individal's object properties and in fact access pretty much any of the right-click contextual menu items BUT the "Find" one. So no "Terminal", "References", "Property Nodes", "Invoke Nodes", Local Variables" access...

Why?

If there is no fundamental reason for this, please consider this as a request.

What I'm suggesting is a combination of an textring and a string control (BD-terminal is a string). The idea behind is, that I like to offer the user a list of pre-defined values (e.g. the values from the five latest program runs) but also the ability to enter a new string.

 

Of course I can get this functionality by adding two separate controls or by combining those in an XControl but I feel the combination would look better, is much easier to handle in the code and needs less space on the UI.

 

Please see the picture for better understanding.

string-enum.jpg