labview2011的一些新功能！

cpubbs

LabVIEW Idea Exchange
How about an Error Cluster Constant on the Dialog and User Interface palette?

Status: In Beta In the LabVIEW 2011 Beta

cpubbs

Direct access to Plot Visible property on plot legend Status: In Beta by Sil3nc3r on 02-26-2010 03:54 AM
It'd be usefull for develloper and especially application user to improve graph control by adding to Graph direct access to Plot Visible property on plot legend.

For the time being, you have to go to color and choose transparent or to change visible property dynamically.

I propose control like that ... but we could find another idea to access Visible property.

Status: In Beta Available in NI LabVIEW 2011 Beta

cpubbs

Always Show the Connector Pane Status: In Beta by blawson on 12-03-2009 09:38 AM
My idea is simple: Put the connector pane on the front panel next to the VI icon.

Why: Right clicking to show the conpane means extra clicks that would not be necessary if it was always there.  It would also be solve the problem of saving the VI with the connector pane hiding the VI icon.

Status: In Beta Available in NI LabVIEW 2011 Beta

cpubbs

Allow the Distribute Tool to work on Wires Status: In Beta by JackDunaway on 06-12-2009 12:08 AM
Currently, the block diagram has an endlessly useful feature. I use it every day - the Distribute Tool.

The following feature would be AWESOME for expediting BD readability:

Status: In Beta Available in NI LabVIEW 2011 Beta

cpubbs

Boolean function accept Error Cluster Status: In Beta by Dany Allard on 06-01-2009 04:34 PM
Make possible that Boolean function accept error cluster as input as this example:

     

Status: In Beta Available in NI LabVIEW 2011 Beta

cpubbs

Create a proper connector pane when doing Edit -> Create subVI Status: In Beta by tst on 06-04-2009 05:51 AM
When creating a subVI from a selection, LabVIEW should do two things:

• Use the user's default connector pane pattern instead of selecting one matching the number of inputs and outputs. This will make easier wiring and allow users to add more IO later.
• If the user is using a "standard" pattern (e.g. 4-2-2-4), LabVIEW should try placing the error clusters at the bottom corners and objects or references at the top corners.
  

It should also try to make the FP of the subVI cleaner, but that's another matter.


Status: In Beta Available in NI LabVIEW 2011 Beta

cpubbs

Change error terminals of Variant to Data function to match every other VI and Function in LabVIEW Status: In Beta by David_L on 01-08-2010 11:46 AM
Almost every VI and Function in LabVIEW that uses error handling uses the 4-2-2-4 connector pane and has the error terminals perfectly line up.  However the Variant to data function (and perhaps others) has the terminals a few pixels up forcing bends in wire or the functions not to be lined up.  I think all VIs should be standardized to help make nicer looking block diagrams.





Status: In Beta Available in NI LabVIEW 2011 Beta

cpubbs

Visual indication that a constant is linked to TypeDef Status: In Beta by Broken Arrow on 08-07-2009 10:41 AM - last edited on 11-12-2010 09:26 AM
I would like to be able to see that a constant is linked to a typedef without clicking it, especially enums.
This could be a light border around the constant, marching ants, or a flag of some type such as the example I have posted. You can quickly tell that the top enum is not linked to a typedef, whereas the bottom one has the little "td" flag.












Status: In Beta Available in NI LabVIEW 2011 Beta

cpubbs

Create type def from block diagram constant Status: In Beta by crelf on 06-02-2009 01:05 PM
As mentioned here, "I lost count of the times where I have a cluster or enum constant that I want to make into a type def and have to first change it into a control, switch to the FP, and then select customize" - it'd be great to be able to right-click on a constand (like a cluster) on the block diagram and select Advanced -> Make Type Def (of course, you'd need to save the type def somewhere).

Status: In Beta Available in NI LabVIEW 2011 Beta

cpubbs

Set "Value Changed" as default event when defining new event cases Status: In Beta by Bruce Ammons on 06-02-2009 10:55 PM
When I use an event structure, the case I use about 99% of the time is "Value Changed".  This is a bit of a pain since it is alphabetically at the bottom of the list, so I have to scroll down the list every time to select the event.

Since I suspect most people use this event the most, I would like it to be the default value when defining an event.  This way, I could just select the control and be on my way!

Bruce


Status: In Beta Available in NI LabVIEW 2011 Beta

cpubbs

Ignore SubVI's Status: In Beta by Ravens Fan on 07-06-2009 03:08 PM
When loading a VI where some or many of the VI's are missing (like a forum post where the person used 3rd party driver subVI's you don't have or used numerous subVI's and typedef's that they did not bundle into their attachments) you have to click ignore on each subVI as it comes up with the dialog box as it searches for it on your system.  If there are only a few such subVI's, it is no big deal.  But some people will be missing dozens of VI's, and you have to continually click ignore over and over again until the main VI loads broken.

It would be good if that dialog box had an Ignore All button, so that once you come across the first subVI it can't find, it will ignore it and all other subVI's it can't find.  Then the main VI can load in it broken state in just one or two clicks.


Status: In Beta Available in NI LabVIEW 2011 Beta

cpubbs

Enable "Undo" even after saving the VI! Status: In Beta by mishklyar on 06-08-2009 03:39 AM
Instead of saving few versions of the same VI, it would be nice to have "Undo" even after saving the VI.

Status: In Beta Available in NI LabVIEW 2011 Beta

cpubbs

Asyncronous Call By Reference Status: In Beta by Jim Kring on 06-10-2009 10:13 AM - last edited on 06-10-2009 10:14 AM
Here is an idea that I have wanted to make happen for a while. It is the Asyncronous Call By Reference. Basically, it is just a Call By Reference, but split in half so that the call is not syncronous (blocking), and return data can be obtained from multiple locations.  Plus, there should be ways to check the status of the asynchronous call and kill it.  I've even implemented this, to some degree, here http://forums.openg.org/index.php?showtopic=88



Message Edited by Jim Kring on 06-10-2009 08:14 AM


Status: In Beta Available in NI LabVIEW 2011 Beta

wdyjz

一起来分享

wdyjz

已经申请了beta版，下载安装后试用了，挺好的。
LabVIEW 2011 Features and Changes
The Idea Exchange icon  denotes a new feature that originates from a product feedback suggestion on the NI Idea Exchange discussion forums at ni.com.

Refer to the LabVIEW 2011 Upgrade Notes for a complete list of new features and changes, for information about upgrade and compatibility issues specific to different versions of LabVIEW, and for upgrading instructions.

Refer to the readme.html in the labview directory for known issues, a partial list of bugs fixed, additional compatibility issues, and information about late-addition features in LabVIEW 2011.

Installing LabVIEW
(Windows) With LabVIEW 2011 you can install LabVIEW and select modules and toolkits from the LabVIEW Platform DVDs. Refer to the Installing LabVIEW 2011 section of the LabVIEW Release Notes for more information.

TopNew Example VIs
Refer to the New Examples for LabVIEW 2011 folder on the Browse tab of the NI Example Finder to view descriptions for and launch example VIs added to the current version of LabVIEW.

TopBlock Diagram Enhancements
LabVIEW 2011 includes the following enhancements to the block diagram and related functionality.

Miscellaneous Block Diagram Enhancements
LabVIEW 2011 includes the following miscellaneous block diagram enhancements:

  When you define a new event case for a control or indicator, Value Change is the default event. [Idea submitted by NI Discussion Forums member Bruce Ammons.]
  You can identify the instance of a type definition or strict type definition on the block diagram with a glyph marking the upper left corner of the instance . If you hover the cursor over the glyph, a tip strip displays the name of the type definition or strict type definition. [Idea submitted by NI Discussion Forums member Broken Arrow.]
  You can use the Align Objects and Distribute Objects pull-down menus to align and distribute wires on the block diagram. [Idea submitted by NI Discussion Forums member JackDunaway.]
  In LabVIEW 2010 and earlier, you can create a type defintion only from the front panel. In LabVIEW 2011, you can create a type definition from the block diagram or front panel. Right-click the constant, control, or indicator you want to make a type definition and select Make Type Def. from the shortcut menu. [Idea submitted by NI Discussion Forums member crelf.]
  You can wire an error cluster directly to a Boolean function (And, Or, Exclusive Or, Not, Not And, Not Or, Not Exclusive Or, and Implies). Use this feature to handle errors using logical operations. If an error occurs, the error cluster passes a TRUE value to the Boolean function. [Idea submitted by NI Discussion Forums member Dany Allard.]
TopFront Panel Enhancements
LabVIEW 2011 includes the following enhancements to the front panel and related functionality.

Choosing Which Plots to View on a Graph or Chart
  To choose whether to display a plot on a graph or chart, right-click the glyph in the plot legend and select Plot Visible from the shortcut menu. If there are multiple plots, you can right-click the plot legend and select Visible Items&raquolot Visibility Checkbox from the shortcut menu to display a checkbox next to each plot. Use the checkboxes to select which plots you want to display in the plot area. You also can use the Plot Visibility Checkbox Visible property to display the checkboxes programmatically. [Idea submitted by NI Discussion Forums member Sil3nc3r.]

Miscellaneous Front Panel Enhancements
LabVIEW 2011 includes the following miscellaneous front panel enhancements:

  Every VI displays the connector pane in the upper right corner of the front panel next to the VI icon. You can add or edit terminals at any time without having to switch back and forth from the VI icon to the connector pane. [Idea submitted by NI Discussion Forums member blawson.]
TopEnvironment Enhancements
LabVIEW 2011 includes the following enhancements to the LabVIEW environment.

Dialog Box Enhancements
LabVIEW 2011 includes the following dialog box enhancements.

Miscellaneous Dialog Box Enhancements
LabVIEW 2011 includes the following miscellaneous dialog box enhancements:

Certain LabVIEW add-ons, such as the LabVIEW Robotics Module, include additional environment settings that allow you to focus on a particular subject area. If you install one or more of these LabVIEW add-ons, you can use the Choose Environment Settings dialog box to change from one environment to another without restarting LabVIEW.
On the Appearance page of the String Properties dialog box, the Display Style Visible checkbox allows you to display the style of the string object.
Use the Clear Compiled Object Cache dialog box to clear compiled code from the Application Builder object cache by selecting Application Builder from the Cache list.
Use the new Size page of the Properties dialog box for arrays to specify the number of dimensions in an array.
Palette Enhancements
LabVIEW 2011 includes the following palette enhancements:


Miscellaneous Environment Enhancements
LabVIEW 2011 includes the following miscellaneous environment enhancements:

  You can perform an undo operation after you save a VI. [Idea submitted by NI Discussion Forums member mishklyar.]
The Help menu includes the new Check for Updates menu item, which opens the NI Update Service window.
  As you load a VI, you can select Ignore All to ignore loading all missing subVIs. [Idea submitted by NI Discussion Forums member Ravens Fan.]
Application Builder Dialog Box Enhancements
LabVIEW 2011 includes the following enhancements to the LabVIEW Application Builder and build specifications:


TopLabVIEW Project Enhancements
LabVIEW 2011 includes the following enhancements to the LabVIEW project and related functionality.

Deleting Previously Built Files
To delete the previously built files of a build specification, right-click the build specification and select Clean from the shortcut menu. Selecting Clean deletes all files that only the previous build generates, not files created before the previous build. You can delete previous build files for stand-alone applications, .NET interop assemblies, packed project libraries, shared libraries, source distributions, and web services.

Miscellaneous Project Enhancements
LabVIEW 2011 includes the following miscellaneous project enhancements:


TopNew and Changed VI, Function, and Node Enhancements
LabVIEW 2011 includes the following new and changed VIs, functions, and nodes. Refer to the VI and Function Reference book on the Contents tab of the LabVIEW Help for more information about VIs, functions, and nodes.

New VIs and Functions
LabVIEW 2011 includes the following new VIs and functions.

Application Builder VIs
The Application Control palette includes the new Application Builder palette with the following new VIs:

Build
Deploy
Clean
Miscellaneous New VIs and Functions
LabVIEW 2011 includes the following miscellaneous new VIs and functions:

The Optimization VIs palette includes the Global Optimization VI.
The HTTP Client VIs palette includes the Config SSL VI.
The Probability & Statistics VIs palette includes the Skewness and Kurtosis VI.
The Packed Library VIs palette includes the Get Exported File Path VI.
Changed VIs, Functions, and Nodes
The following VIs, functions, and nodes changed in LabVIEW 2011.

TDMS Read—This function contains a new return channels in file order? input, which specifies whether the TDMS Read function returns data channels in the same order as they exist in a .tdms file. If the value of this input is FALSE, this function returns data channels in the same order as you specify in the channel name(s) in input. The default is FALSE.
Geometry VIs

The Geometry palette includes the following changed VIs.

The following VIs include a rotation order input, which specifies the order of the axes to rotate the coordinates around.

3D Cartesian Coordinate Rotation (Euler)
Direction Cosines To Euler Angles
Euler Angles To Direction Cosines
Miscellaneous VI, Function, and Node Changes
LabVIEW 2011 includes the following miscellaneous VI, function, and node changes:

  The error terminals of the Variant to Data function now line up evenly with the majority of the error terminals of other functions and VIs. [Idea submitted by NI Discussion Forums member David_L.]
The General Linear Fit VI includes the Weight Out output that returns the actual weight of general linear fitting or returns the value you enter for Weight, depending on the method you specify.
TopNew and Changed Classes, Properties, Methods, and Events
LabVIEW 2011 includes new VI Server classes, properties, methods, and events. Refer to the LabVIEW 2011 Features and Changes»New VI Server Objects topic on the Contents tab of the LabVIEW Help for a list of new classes, properties, methods, and events.

VI Server Properties and Methods
LabVIEW 2011 includes the following VI Server method changes:

Scene:Read Scene File—Supports .dae files.
Scene:Write Scene File—Supports .dae files.
Enhancements to .NET Support in LabVIEW
Debugging Unexpected Behaviors of .NET Assemblies in LabVIEW
.NET objects can exhibit unexpected behavior when LabVIEW has a different version of the assembly in memory than the version you want to use. To identify this discrepancy and debug the assembly calls, refer to the .NET Assemblies in Memory dialog box. If you determine that LabVIEW loaded the wrong version of an assembly, you can adjust assembly locations on disk, create a configuration file, or reload updated assemblies to ensure that LabVIEW loads the correct assembly.

Loading .NET 4.0 Assemblies in LabVIEW
The most recent programming environments for .NET assemblies target new assemblies to run in the Common Language Runtime (CLR) 4.0 by default. Thus, although LabVIEW is still most compatible with the CLR 2.0, you can force LabVIEW to use the CLR 4.0 to load .NET 4.0 assemblies.