LabVIEW Idea Exchange

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

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

While and for loops should have diferent border color or texture whether they arre running or not. In 2009 there is significant improvement in

probe window, but stil it would be nice to know status of a loop without probing.

Tip strip on build array should show the index of input when you connect wire/probe - element[i]. The same on index array when index inputs are not wired. It's wery annoying to find element[27] on build/index array.

I16 is currently the only output representation of this function, and it is particularly unhandy - I typically end up typecasting it 90% of the time. I propose the output representation of this primitive can be changed via Right-Click Menu.

 

BoolOutputRepresentation.png

The IDE option to show constant folding is extremely powerful, but if you keep it checked, your block diagrams look like you're looking at a blurry CRT. This gets tough on the eyes, so I would appreciate a menu item called "Show Constant Folding" right next to "Show Buffer Allocations" that temporarily flashes the constant folding blurriness.

 

Below is an example of the blurry lines:

 

BlurryConstantFolding.png

When entering values into an array control, you can <tab> between the elements while the VI is running.  This same behavior should be available when editing elements in an array control (when the VI is not running) and an array constant.

A long time ago LabVIEW used to have a great set user interface design tools, and the buttons and objects looked great. Since then it seems that Visual Studio and other text based languages have surpassed LabVIEW in user interface design. I would like LabVIEW to once again become one of the greats for user interface design. For instance resizing of the application window during runtime is not the easiest thing in LabVIEW.

In the probe window it if you look at "value" it is just the 2D array flattened to a 1D array, which makes it very difficult to tell where one row stops and the other begins. I suggest making this work similar to how visual studio lets you expand teh elements of the array.

 

I also suggest the probe display array to have scroll bars on arrays so you can see elements a lot easier than clicking or typing in an index.  Also showing more than one element would be beneficial.

We have multiple developers working the same project. We all store our copy of the source code in different directories. When using Application Builder in the Project, you need to set an absolute path for the build destination. It would be great if this directory could be a relative path from the project file.

It would be nice to be able to configure the File Dialog view. I would like to be able to set the default to show details and sort the files in descending order.

Message Edited by VADave on 09-18-2009 05:29 AM

Whenever I built something (executable, installer) I want to go to the output location to change some filenames for distribution (e.g. I change "volume" folder of the installer to contain the name and version in the program name), zip things up to post on the server, etc.

 

On the final progress screen, where it tells me that the built has finished, I would like an additional button to open the target folder location(s) in explorer (similar to e.g. when downloading a file using IE) while dismissing the dialog.

 

Right now it says:

 

"The build is complete. you can locate the built at <very long and hard to remember path spread over 3-4 lines and that cannot be coped/pasted from this dialog anyway>."

 

Well, if the builder is smart enough to know where things are, why can't it just directly take me there as an option? 😄

Simply put, you should be able to put a URL hyperlink in a floating comment to link out to some site.

 

Imagine being able to add a hyperlink to the mathematical description of a VI that you used. Perhaps you have an internal server of IP Documentation. You could add a hyperlink to that in depth information directly in your VI. Perhaps you want to put your logo along with a link to your website at the top level of your source code. Whatever the reason, you need to be able to add a normal comment to the block diagram and populate that comment with text and hyperlinks.

 

As a extension, this new comment field could even take simple html tags for more formatting, embedding images, or maybe even an embedded video.

 

 

Comment_with_hyperlink.png

Message Edited by Rick K on 09-17-2009 12:06 PM

Currently, the Initializer Terminal on Feedback Nodes is always under the Feedback Arrow. I propose that a right-click menu item should allow you to choose whether the terminal is on top or bottom (the menu item would be next to "Change Direction").

 

CURRENTLY - (only bottom is an option)

FNBottom.png

 

PROPOSED - (both top and bottom are options)

FNTop.png

I like the concept of the probe watch window in LV 2009.  It is equivalent to using watch windows in other languages like Visual Basic.  However, I haven't used LV 2009 enough yet to get a feel for how I would use it.

 

With LV 8.6 and earlier, the probe windows are separate entities and detached.  This is good if you need to quickly jump to the front panel to hit a button or change a value and see the changes that are occuring the block diagram.  However, there are some issues with viewing them on the block diagram.

 

I'm watching a control loop subVI.  I've opened up a dozen probes to look at the values on the wires at different parts of the block diagram  (I'm not using highlight execution as I want things to run at full speed).  I scatter the probes around so that they are near the wires they represent.  That way at a glance I can see the path of data and how the decision structures are working.  However, if I need to scroll the block diagram, or move the whole window to look at something else, the probe windows stay where they are and obstruct the view of the other things.  Then it is difficult to relocate the window or scroll bars so that the probes line up with their wires again.  If I am doing this with a couple of subVI's, then all the probes intermingle and it is impossible to tell whether a value is from the visible subVI or a subVI that is hidden underneath a few other windows.

 

What I propose is an attached probe.  Once you place it on the block diagram, it stays associated with that location/wire.  move the window, it moves.  Scroll the diagram, it scrolls.  Hide the window, it hides as well.  Also make the window slightly smaller so you don't need all the space for the title bar, X button.

 

Go one step farther and instead of making it a probe, let it be what is essentially a front panel object on the block diagram.  So that it looks like a basic indicator, or a boolean LED, or even an array or graph.  You drop it on the BD and wire it up.  When you are done, you delete it.  Scroll the BD, move the window, things stay where you want.

 

See BD indicators.png for the proposed way and Current Way.png for the problems with the current way.  I did put the images in the message, but they filled the screen and overlapped other parts of the web page.

Message Edited by Ravens Fan on 09-16-2009 05:18 PM
Download All

If you have, for example, an 8-elements array, you can easily increase its dimension to 16 elements by left clicking its bottom line, and dragging it downwards. Then, simply enter a value on the 16th position (and enter all other new values according to your needs).

But if you have to perform the opposite operation, you must right click all the elements to delete one-by-one, and select "data operations -> delete element".

That can be really annoying: I'd like to see implemented the possibility to select multiple elements, and to delete them at once (or at least, to see an option like as "data operations -> delete all elements after/before").

 

Most of applications we write in LV are contained inside of a project. Saving it to disk creates a lot of files (.lvproj, .vi, .ctl, .aliases, etc) and subdirectories. This is convenient when you want to copy one VI or control to another project, but very inconvenient when sending this project to someone. In this case you have to create an archive to put everything together. Make an option to save all items contained in a project in one file.

 

Making a Windows Explorer plugin to automatically open such files as directories would be also a nice addition in this case.

 

Thanks

Have you ever wanted to place a probe on a loop iteration counter? I can't tell you how many VIs I have with a wire from the iteration counter to the loop boundary just so I can put a probe there (Maybe a pop up iter. count would suffice). Or probe an output terminal on a VI that is not wired. I know you can open the VI and put a probe on the wire but..

 

There are probably more cases.

 

Minor issue, but since we have a chance to ask..has been bugging me for about 20 years now.

 

 

Currently, if you use the stock one and two button dialog VIs in your code, they will block the root loop while being displayed.

For those of you who don't know what the 'root loop' is, this is the core process of LabVIEW that many UI functions must execute under.  One of the key functions that executes in the root loop is VI Server calls to open a new dynamic VI.  So, if your code has multiple threads all performing operations that involve dynamic calls to other 'plug-in' VIs and one part of your code calls one of these stock dialog VIs, then all the other threads will be blocked until the user clears the dialog.

As a result of this, I have had to write my own 'root loop safe' versions of these dialogs to prevent this from happening.

 

As a side note, dropping down a menu and leaving it down without selecting anything also blocks the root loop.  It would be great if they could fix this too!

 

 

I just made a build and received one error on why the build was unsuccessful. I tried to navigate to the perpetrating VI in the project, but lo and behold, the Build Error window is Modal! I had to take a screenshot of the build error (Hey, at least that window is resizeable!), then navigate to the proper VI. Having a floating window instead would not exclusively reserve mouse focus for LabVIEW.

Labview implements lots of functionality in the right click menu, resulting in large and deep menu hierarchies.  Often I want to select multiple items, but the context menu disappears after a single selection requiring me to go back to the original item and renavigate the menu tree.  That's a lot of repetitive, fairly precise mousing.

 

I'd like to have a hot key that prevents the context menu from disappearing after I select an item.  For example, if I held down the Ctl key while deselecting "Label," I could immediately move down to "Caption" and select it, making the whole process much easier.