LabVIEW Idea Exchange

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

Whenever we add a new item in tree programatically using "edit tree item" node,

2018-09-15_1719.png

We are not sure what tag would be set to Child Tag. Because if that tag already exists LabVIEW will appends a number to make it unique.

From help of "Edit Tree Items:Add Item Method"

The default is the string you wire to Left Cell String. If an existing tag already uses that string, LabVIEW appends a number to the string to create a unique tag for the new item.

 

It would be great if we can get the value of "Child Tag" as output as well, which is set by LabVIEW.

I have VI's and projects saved in Chinese characters and they do not open in the English version of LabVIEW. LabVIEW is unable to read special character unless I change my system languages. I feel that LabVIEW should be able to read all different languages and not required to download different versions. 

I faced issues while creating an installer with a size of 2GB+. Unfortunately I had to upload the installer to a shared site that didn't accept files > 400MB. The want for a separate installer and process thereof delayed my delivery.

I remember from other software(s) having distro creation capabilities in size of lets say a standard CD size of 650MB, etc.

Wouldn't it help many if the app builder allowed splitting the installer in a defined packet size?

 

Good day forum. Can't seem to find a method to extract cluster element label names from cluster constants. Maybe through a malleable subVI? Would prefer to have that together with the control reference method. Thanks

I am struggling (yet again) with LabVIEW installation problems that appear to involve LabVIEW 2017 (and possibly LabVIEW 2016 f5 patches).  After having systems with multiple (sometimes only 2) LabVIEW Versions installed "go south" (typically by having MAX stop working and Block Diagrams with DAQmx code fail to load), I've tried to "Remove All" NI software, only to discover that "bits and pieces" still remain, both on Disk and (especially) scattered throughout the Registry.

 

I've been working with NI Support for 2-3 weeks trying to "recover" from a LabVIEW corruption probably caused by installing the 2016 f5 patch.  We finally decided to do the "Uninstall/Reinstall" route.  Although I got 2012 SP1 installed, 2014 SP1 failed (could not install NI Network Discovery 14.0, "Verify you have sufficient privileges to install Services").

 

My concern is that, short of reformatting my hard drive and reinstalling Windows (which I was forced to do on two of my PCs), there appears to be no way to fully uninstall all NI Software.  I would like to propose that NI develop an "Eraser" utility (like Eraser for Microsoft Office) that searches out all files that NI puts on the C: drive (not in User Space) during installation and all Registry entries that it scatters throughout the Registry, allowing the PC to be "rolled back" to a "pre-NI" state.  Such a tool might want to be restricted to Full or Professional licenses, or maybe provided on an "As Needed" basis by the NI Support Team, but I really don't want to have to rebuild yet a third PC ...

 

Bob Schor

Hello Guys,

 

as we are transforming our Testing Application deployed as Executables to something more "state-of-the-art", I found the Remote Panels solution could suite our needs.

Remote Panels are a nice solution, but they rely on LabView RTE and Browser Plugin on the Client Machine. I don't think this is state-of-the-art, since the Web Technologies Wars have are over and Plugins lost the Fight.

I found some similar ideas in the Idea exchange, but none of them hit the point directly. So heres my Proposal:

 

Replace the reliance on LabView RTE and Browser Plugin with a HTML 5,JavaScript and Websockets solution, that runs on any modern Webbrowser!

 

This would bring the following Advantages:

- support for any client operating system (even IOS, Android, etc. possible)

- seamless support for Remote Panels in modern browsers (neither Chrome, Firefox, IE will support NPAPI in the future)

- take advantage of all the PROS of modern web technology (e.g. responsive UI to support Touch UI targets)

- since no Plugin is needed, Clients will have no Security concerns (remember Adobe Flash concerns at Apple)

- no need for any NI customer to build an own HTML5 remote panel solution to bridge this obvious gap of Labview Functionality.

 

I know there are solutions for Windows Remote Control like VNC, but this does not offer a target UI adjustment for the application. So for example a Ipad Target will not change its UI to be Touch-friendly for the User.

 

I hope you support the Idea! Best regards and thanks for the Attention, Philipp

 

I imported and pasted a graphic (my company logo) onto the front panel of my VI, but apparently there's no simple way to resize it while constraining the aspect ratio (e.g. resizing it proportionally).

 

I'm not asking to do it programmatically; I'm asking simply about resizing it to fit the rest of the front panel's design. 

 

If I grab the handles and drag, it allows arbitrary resizing on both axes. If I hold down Shift it constrains it to resizing the vertical axis only. I've tried every combination of modifier keys, on both OS X and on Windows, and I can't seem to constrain the aspect ratio.

 

Most other applications that allow image resizing offer one or more of the following:

  1. Holding down a modifier key (typically Shift) while dragging a corner resize handle forces proportional resizing. The current behavior in LV makes no sense. Holding down Shift forces a vertical resizing only, but this can be done by dragging the top/bottom handle (e.g. not a corner handle).
  2. In the Set Width/Height dialog, have a checkbox to Preserve Aspect Ratio. If checked, any entry into height or width causes automatic calculation in width or height OnBlur.
  3. In the Set Width/Height dialog, support entry by % or by pixels, with the same option to constrain.

This will help all of us produce more professional-looking applications. 

If you change a font size to make something more easily readable, the assosciated control gets bigger but the increment/decrement buttons don't. They just do their own thing and it is annoying.

 

bad buttons.PNG

 

 

Hi

   My idea is to connect two nodes without the need to use the mouse to connect the wire. Just select two nodes and use some command(shortcut like (ctrl+n) or Right click and select from drop down)so that, both the nodes maybe connected to each other.

(Note: sorry if this idea already given)

 idea.PNG

regards

Senthil

 

 

Ever came across this BD-space killing case arrangement when trying to write a text parser for your external hardware?

CaseSelectorWildCardCurrent.png

I have this idea about a wild card (*) . Freeing up code-space quite a bit!

Of course also possible with a comma string list.

The inside case border of the wild carded case will have the before/match/after substring connectors of the MatchPattern.ViCaseSelectorWildCardProposal.png

This NIST site defines a non-integer factorial:

http://www.itl.nist.gov/div898/handbook/pmc/section3/pmc32.htm

 

The result of the computation is used in statistical process control.

 

I think that LabVIEW should have its VI's compatible with NIST, and "engineered for process control", seeing how they control processes.  The control shouldn't exclusively about operation, but should also have bounds, and quick/effective alerting for out-of-control condition.  (OOC).

Recently I have been coding for some general apps that do not include any instrumentation.  I've become frustrated by the Time Stamp control's resulting dialog when the Time/Date Browse button's  is clicked.  (I don't caret to use Microsoft .net controls)  I do want the user's entry limited to the format that is displayed in the control.  I don't want to confuse the user's by displaying a certain format in the control then imposing, or allowing, another format in the resultant dialog even if it isn't displayed that way in the control after the dialog is closed.

 

Also, the dialog itself could use some aesthetic improvements.  If the control is a 'Silver' control then popup a dialog containing 'Silver' controls, et al.

 

Illustrative examples:

 

If the Time Stamp control's Display Format is set as 24-hour time, have the time field in the dialog display 24-hour time.

 

If the Time Stamp control's Display Format does not define any decimal precision of seconds, do not display decimal precision of seconds in the time field in the dialog display.

 

If the Time Stamp control's Display Format does not define any seconds, do not display seconds in the time field of  the 'Set Time/Date' dialog.

 

If the Time Stamp control's Display Format does not define any time format, do not display any time field in the dialog. I suggest a default value of '00:00:00' for the time component of the time stamp when no time is defined in the Display Format.

 

If the Time Stamp control's Display Format does not define any date format, do not display the calendar/month/year in the dialog.  I suggest a default date of 1/1/1904 for the date component of the time stamp when no date is defined in the Display Format.

 

Often I need to grab a VI that's part of a class or just a loaded VI from the project explorer. In normal cases I have about 10 - 30 windows open and thus it takes some time to find the project explorer of the active VI, especially when I don't remember the name or there are dozens with the same name thanks to OOP. Luckily there is the option to find it through the menu Window >> Show Project. However.

 

As I'm already a heavy user of the keyboard with all the shortcuts in LabVIEW, it would be nice to have a shortcut combination to switch quickly to the project explorer of the active VI. Which combination is not important for me, as anything could memorized. 

When I have a VI with several inputs and outputs on the connector pane, I occasionally have to re-organise the connector pane to follow a standard or even just to simplify the block diagram appearance. When this is needed, I have to reset the required status of the controls in their new position.

 

The idea is to allow a control to have its connection type defined, rather than the connector pane.

This gives the following benefits:

  1. If a control is set as 'Required' but does not appear in the connector pane, we can get an error.
  2. If we move a control in the connector pane, the required setting moves with it.
  3. Copying a control from one VI to another could take this property with it.
  4. The context help could potentially show if the connector is required/recommended or optional,

The connector would perhaps need 4 type setting: required, recommended, optional, connector pane.

The final setting means that the value from the connector pane is adopted.

Setting any other value, overides the connector pane setting.

 

I would like to propose the idea to have a way to save your labview development environment settings from one version of labview to the next.  I find it a bit tiresome to have to configure labview the way I like it everytime I get the updates (twice a year if you have a service subscription).  Having to toggle to grid snaps and changing the front panel controls icons.  I find its hard to remeber which settings you changed.  I would be nice if those preferences could be exported to a file then imported into the latest version so that you can more seamlessly update your development environment.

Allow a multi-line Format String, with Format Into String treating new lines as though \n was in Format String.  Here's an example, where the output appears as three separate lines (and the Format String also looks like three separate lines, shown on the left, with the "correct" and only "legal" way to do this shown on the right).Format String Idea.png

Not realizing this would be a problem, I just created an 11-line "content" for an INI-like file, not expecting it would "reformat" itself as a line containing 198 characters ...  Oops.

 

Bob Schor 

Sometimes one has a 2D array of data that one wants to display in nice-looking rows and columns.  The "obvious" way to do this is as a 2D array, but the row and column "dividers" can interfere with the desired "unified" Spreadsheet look.  One solution is to use Array to Spreadsheet String, which creates a single String with a default "tab" separating columns and an "eol" separating rows, but aligning columns becomes very difficult, especially with a non-monospaced font.

 

I'd like to propose a "special" (I don't have a name for it -- maybe SpreadSheet String?) String Array Indicator that behaves like any other Array Indicator except that the "visual separators" between the rows and columns can be made "invisible", possibly by a right-click option.  Now the Front Panel Designer can lay out rows and columns, adjust widths and heights, then make the interior walls vanish so when the user "fills in the blanks", it appears as a nicely aligned series of row and column data.  If the data are strings, the user could even set Right, Center, or Left justification for the standard cell, again simplifying formattting.

 

Bob Schor

I find it difficult to pinpoint the local variables and property nodes in a program with many layers (cases, events...). It would be very helpful if LabVIEW had a list of all property nodes and local variables in one place, like a table, and with a click one could jump directly to the selected instance.

Double clicking a reentrant defined Vi opens always it clone instance. But nearby most of the time i have to edit the function and thus need the original VI open instead of the cloned instance.

It would be comfortable if you add an entry in the context menu like 'Open Prototype VI', so i don't need the navigate through the project explorer to the desired VI for editing.

When you have a probe to se the data in an array, you se all elements in one row (in the Value column) and just one element in the Probe Display area. If you have a large array, it is difficult to get a good overview.

 

My suggestion is that in the part of the probe window called Probe Display, you should be able to pull the bottom right corner and see several elements simultaneously.

 

Probe 4.png

 

An extra feature would be to also show the array size anywhere in the probe window.