LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

Currently (up through LV2010) the only run-time menu (RTM) available for a tab control is for the entire tab control, not for the individual pages (tabs). The right-click context menu (Description and Tip, Help, etc.) for each page only works at design time, not at run time. This is true of both the default or a custom RTM.

Why is it called a "run-time menu" if it doesn't work at run time? I consider this a bug, but it probably is just an oversight in the design. (I suppose that technically this is not a "bug" because I cannot find this feature, an RTM for each tab or page, documented.)

Anyone else think this a useful product improvement?

Ed S.

Replace feature for Enum and Ring

Upgrading from older versions

Give the user the ability to upgrade versions of Teststand or labview without bringing the test equipment down for several hours. Currently it is quicker to image the whole pc than install a new NI software version. Some of the software (from other vendors) we run has propretiary configuration and imaging isn't always feasible. I would like to be able to upgrade from Labview 8.6 to 2010 without stopping production, just upgraded from 8.2 to 8.6 and on 50computers, on a production floor, it was logistically difficult. It would be a while before I consider upgrading again, with the current setup.

Waveform Graphs Axis drop down menu

I have an application where it would be nice to change the data displayed by clicking on the y-axis or x-axis labels themselves as oppose to a separate enum type, button or switch residing outside the graph.

For example:

If I want to look at Voltage or Current vs frequency or time currently you could use enum types outside the graph. It would be handy to select the y-axis label in real-time (during or prior to runtime) and change the data displayed. If you click on the y-axis label you can have enum type drop-down that is read horizontally and when you select the unit you want the label would be displayed vertically or make it custom depending on what the user prefers.

The same thing can be done for the x-axis. So in one graph I can click and select the x-axis label and select Time and selelct Current for the y-axis and depending how I set my program see the data displayed as it should be in real time in one clean graph. No side buttons or switches.

Would anyone else like to see this feature? Thanks.

A new feature that would act similarly to the "Automatically close VISA sessions" option and close all open file references once the top level VI has stopped running.

This new function would preclude the situation where LabVIEW locks, and keeps a file locked until the entire development environment is closed.

(I would even be happy with a menu option to explicitly close all open file references.)

The primary use case would be during development/debugging. If you stop or abort your top level VI without closing a file reference, LabVIEW will hang on to the reference keeping it open, but inacessable, until the dev environment is shut down.

It seems that if there is not an open reference to the file on the block diagram or the top level VI has stopped running, and certainly when all open VIs are closed, then all files should be closed and locking handles should be released.

I suppose this concept could be expanded to cover any reference type that LabVIEW does not implicitly close when the top level vi goes idle.

Table property changing

Maybe there is a very good technical reason why this idea is not a good one.

Problem: If I want to load a vi into my application the subvi's of the dynamically loaded vi can not be found.

My Plug-In Application (EXE) is Not Calling My Plug-Ins Correctly

Solution: Add a boolean input (or an options flag) to Open VI Reference which will load the vi and modify the search path so the subvis can be found.

I know there are several workarounds but I would like this to be easier.

In most every text-based programming language there are built-in functions to convert a character to its decimal ASCII code and a decimal ASCII code value to its associated character. In BASIC, for example, ASC(character) does the former and CHR$(code) does the latter. In LabView you have to implement these functions yourself from scratch with a CASE structure. If you want to do the whole 7-bit character set you need 128 cases. This is a waste of time! Since many instruments use single ASCII charcters as their commands why not include such functions in LabView?

I tend to use a lot of floating windows that can be suppressed by the user if they don't want to see them any more, to convey various messages.

But in doing so, either Windows or LV is playing three card Monty with the order that they show up in the open programs list. Is it possible to leave them at their original ordering? When you have a lot of VI's open, this can be quite irritating. This might be something that can't really be worked around because of Windows quirks, but I don't know enough of the Win kernel to say ... maybe the floating status of a VI is actually a Windows flag that you have no control over.

Also, would it be possible to not have floating LV windows disappear from the Windows task list? This seems like it's directly related to the same cause of the previous issue.

Thanks,

-Ben

Dionex Pump Driver

Easy Set Breakpoint

In the Run Mode we can set the breakoint by pressing the <Ctrl> key and left click over the probe. To remove it the vice versa applies...

In the Edit mode it would be more handy to set the Break point by Pressing <Ctrl><Shift> key and left click over the probe to set and remove the Break points.

I have checked the Functionaltiy of the <Ctrl><Shift> key when both are pressed the mouse pointer changes into a hand tool and we can move the BD on anyside but it doesn't have any effect over the probe and on the Front panel.

So this idea would defenetly help to make easy debugging..

View All (2)

It's good to have tool like Quick Drop...........but it will great if we can see our own VIs/Custom Controls/Custom Indicators/objects present in my PC in the list.

This can be achieved by remembering them while they are made or being used for the first time. So that every time I don't have to got to Select Vi, search the path & call a VI.

The only option to do this right now is by placing the VIs in user or inst directory of Labview.

But this not what we always do right? We manage the folders & VIs in different locations.

Just as good function as any desktop search.

LabVIEW Idea Exchange

Tab Control Run-Time Menu for Each Tab (page)

Replace feature for Enum and Ring

Upgrading from older versions

Waveform Graphs Axis drop down menu

Automatically close file references

Table property changing

Dynamically Load VI Into Application With Dependencies

Can you include the Tools palette when you right click to display the short cut menu in the Front Panel or the Block Diagram

Wire Entry/Exit to Structures From Sides Only

Add built-in character-to-ASCII code and ASCII-code-to-character functions.

Append to report.vi: keep the current font size

Floating windows become last active window when top-level VI is stopped

Ability to export graph properties along with graph data from subvi without resorting to "references" to access changed properties of graphs in a subVI

Dionex Pump Driver

Easy Set Breakpoint

Quick Drop should show VIs & control/indicators/object present on PC..............like desktop search

case structure renumbering

Accommodate C++ Class DLLs

Allow the configuration portion of DLL nodes to see mangled function names

Setting Conditional expressions for CONTROLS/INDICATORS in the properties Window