Softpedia >Mac >Developer Tools >LabVIEW >  Changelog

LabVIEW Changelog

What's new in LabVIEW 2015 SP1

Jun 27, 2016
  • Bug fixes:
  • 515054: Icon transparency of VIs is not maintained when building a Source Distribution
  • 530816: In rare cases, LabVIEW may crash when saving the results of the Compare VI Hierarchies tool when used on a reentrant VI
  • 530928: Internal warning when saving a VI with a Fixed-Point datatype for LabVIEW 8.2 or earlier
  • 534471: When building a packed project library containing classes, changes in class inheritance would not propagate to calling VIs
  • 537078: Case Structure auto-complete functions incorrectly when used with Enum Controls in LabVIEW 2015
  • 537780: Unregistering and re-registering an event while an event callback VI is running may crash LabVIEW when the callback VI returns
  • 538332: Make Space/Remove Space does not work when Bookmark Manager is open and there is a bookmark in the VI
  • 540922: Channel Wires are incompatible with Control & Simulation Loop tunnels
  • 543507: DAbort 0x2CADF6E3 caused by scrolling the mouse wheel within an array
  • 544852: In some cases, LabVIEW 2015 creates a minor internal warning when shrinking diagrams
  • 545175: In some cases, using Sort 1D Array and Array Max & Min or Less Than on a cluster would report incorrect data
  • 546121: Ctrl-A, then Delete does not delete the icon in the Icon Editor in LabVIEW 2015

New in LabVIEW 2014 14.0 SP1 (Apr 23, 2015)

  • NEW FEATURES:
  • LabVIEW 2014 SP1 includes the Profile Buffer Allocations window to identify and analyze buffer allocations in a LabVIEW application. Select Tools»Profile»Profile Buffer Allocations to display this window. You can use this window to complete the following tasks:
  • Identify the large buffers that an application allocates. Click Start to start profiling, run a VI or multiple VIs that you want to profile, and click Stop to end the profiling session. The Profile Data table displays the largest buffer allocations. The number of buffer allocations in the table is no greater than the Maximum buffers to display.
  • Analyze the cause of a buffer allocation. Double-click a row in the Profile Data table to open the block diagram of the VI that causes the buffer allocation. LabVIEW highlights the node, wire, or tunnel which causes the buffer allocation.
  • Save and load profiles for analysis. Select File»Save Profile to save the profile data to a binary file on the disk. You can load the saved profile back into this window by selecting File»Load Profile. You can also export the profile data to a CSV file by selecting File»Export Table. You can load the CSV file in either Microsoft Excel or Notepad.
  • This window includes the following components:
  • Application Instances—Filters application instances that contain buffer allocations. By default, the Profile Buffer Allocations window shows VIs from all the application instances that allocate large buffers during the profiling session.
  • Maximum buffers to display—Specifies the maximum number of buffer allocations to display in Profile Data.
  • Size unit—Specifies the unit of size (bytes, kilobytes, or megabytes) LabVIEW uses to display the results in Profile Data.
  • Profile Data—Displays a list of buffer allocations that LabVIEW identifies during the profiling session. Click the column header to sort data by column.
  • Time vs Memory Graph—Plots the size of a buffer allocation over time.
  • Threshold—Specifies the minimum size of buffer allocations to record. The Profile Data table only displays buffer allocations larger than Threshold.
  • Start/Stop—Starts or stops the profiling session.
  • BUG FIXES:
  • 476710: Opening a VI Server Reference to two or more identically named VIs, contained in separate LabVIEW libraries in a running executable, can result in Error 1031.
  • 487258: A LabVIEW 2014 Web Service does not run when it is built into an executable and then installed via an NI Installer.
  • 491159: Type Definition instance does not require manual update (new to LabVIEW 2014) if last element of enum was deleted.
  • 491225: Installing the LabVIEW 2014 Run-Time Engine via an NI Installer can prevent the NI System Web Server from starting if older versions of LabVIEW are also present or installed.
  • 491714: Using Probes while Remote Debugging with General Error Handler VI present can cause LabVIEW 2014 to hang.
  • 492159: Uninitialized array elements in block diagram array constants are less transparent in LabVIEW 2014.
  • 492898: Open VI Reference hangs on second call.
  • 493375: In certain cases, LabVIEW 2014 crashes when loading a VI with an updated type definition.
  • 500664: Under certain conditions, the LabVIEW Digital Waveform Graph appears blank even with valid data present.
  • Accessing the Help

New in LabVIEW 2014 14.0 (Aug 11, 2014)

  • LabVIEW Version- and Bitness-Specific System Tray Icons:
  • LabVIEW 2014 introduces the following new system tray icons that indicate the version and bitness of the installed LabVIEW.
  • You can use these new icons to help identify different versions of LabVIEW installed on a computer. For example, if you have LabVIEW 8.6 and LabVIEW 2014 installed, you can differentiate between the system tray icons to avoid opening a VI in the incorrect version of LabVIEW. Because the new system tray icons also display bitness, you can easily differentiate between LabVIEW 2014 (32-bit) and LabVIEW 2014 (64-bit) if both are installed.
  • Installing and Updating DataPlugins in LabVIEW:
  • In previous versions of LabVIEW, you must download and manually install DataPlugins from ni.com/dataplugins. In LabVIEW 2014, you can directly search, install, and update DataPlugins by using the Storage/DataPlugin VIs.
  • Block Diagram Enhancements:
  • LabVIEW 2014 includes the following enhancements to the block diagram and related functionality.
  • Automatic Shift Registers on For Loops and While Loops:
  • In LabVIEW 2014, when you place a For Loop or While Loop around existing code, LabVIEW automatically creates shift registers for any input and output that share the same data type and have a data flow dependancy, like error in and error out parameters.
  • New Default Behavior for Input Tunnels on For Loops:
  • If you place a For Loop around existing code, by default, LabVIEW automatically creates indexing input tunnels to pass data through the loop. LabVIEW creates non-indexing input tunnels if placing a For Loop around existing code would result in breaking the wire passing data from the input tunnel into the loop.
  • New Default Behavior for Input Tunnels on While Loops:
  • If you place a While Loop around existing code, by default, LabVIEW automatically creates non-indexing input tunnels to pass data through the loop only if the wire that will connect to the input tunnel is not broken. If the wire that will connect to the input tunnel is broken before you place the While Loop around the code, then LabVIEW creates an indexing input tunnel if indexing will fix that broken wire.
  • Automatically Wiring Objects in a VI:
  • In LabVIEW 2014, you can use a Quick Drop keyboard shortcut to quickly wire multiple block diagram objects together. Highlight one or more parallel rows of objects and press to open the Quick Drop dialog box. Once the Quick Drop dialog box appears, press . LabVIEW automatically wires the highlighted objects together. You also can press to wire one or more parallel rows of block diagram objects together and clean up the highlighted code.
  • Front Panel Enhancements:
  • LabVIEW 2014 includes the following enhancements to the front panel and related functionality.
  • Using Silver Style Controls:
  • In LabVIEW 2014, use the new Decorations palette on the Silver palette to easily access silver style decorations.
  • Troubleshoot Errors Caused by Missing SubVIs:
  • In LabVIEW 2014, you can use the Error List window or the Context Help window to determine the location of missing subVIs. In previous versions of LabVIEW, the Error List window indicates when a subVI is missing but does not provide details about the location of the missing subVI. In LabVIEW 2014, the Error List window lists the driver, toolkit, or module that contains the missing subVI and provides information for resolving the error caused by the missing subVI. The Context Help window also lists the path to the missing subVI.
  • Reviewing and Updating Type Definition Instances:
  • In LabVIEW 2013 and earlier, when you apply changes from a type definition to instances of that type definition, LabVIEW may lose or incorrectly preserve the default values for the instances you want to update.
  • In most cases, LabVIEW 2014 automatically preserves the default values of each instance you update from a type definition. When an instance cannot be automatically updated, LabVIEW places the instance in an unresolved state until you manually update using the Review and Update from Type Def. dialog box.
  • You can view the Review and Update from Type Def. dialog box by right-clicking an unresolved instance and selecting Review and Update from Type Def. The Review and Update from Type Def shortcut menu item replaces the Update from Type Def shortcut menu item that appears in LabVIEW 2013 and earlier.
  • Dialog Box Enhancements:
  • LabVIEW 2014 includes the following dialog box enhancements.
  • Troubleshoot Error Codes from Error Dialog Boxes:
  • In LabVIEW 2014, you can easily locate troubleshooting information for error codes from the Explain Error dialog box and the Simple Error Handler VI dialog box. Click the new Search ni.com for error hyperlink to display search results for the error on ni.com in the default web browser. By default, the hyperlink also appears in the General Error Handler VI dialog box. The hyperlink appears only in the development environment.
  • New VIs, Functions, and Nodes:
  • LabVIEW 2014 includes the following new VIs, functions, and nodes.
  • Actor Framework VIs:
  • Actor:Launch Root Actor–Launches an asynchronously running VI that performs tasks and handles messages for the Actor. This VI returns a reference to an enqueuer that you can use to send messages to the newly launched actor.
  • Actor:Launch Nested Actor–Launches an asynchronously running VI that performs tasks and handles messages for the Nested Actor. Use this VI to launch nested actors. This VI returns a reference to the enqueuer that you can use to send messages to the newly launched actor.
  • Actor:Send Launch Nested Actor Msg–Sends a message containing an actor to another actor. The actor receiving the message will launch the payload actor as a nested actor. Use this VI only to send a message from an actor to itself.
  • Storage/DataPlugin VIs:
  • Open Data Storage–The Get More DataPlugins from ni.com/dataplugins button in the configuration dialog box of this Express VI is replaced by the Install/Update DataPlugins button. Click Install/Update DataPlugins to launch the Install/Update DataPlugins dialog box, which allows you to search, install, and update DataPlugins from the National Instruments website at ni.com/dataplugins.
  • List DataPlugins–This VI includes the new source input, which specifies whether LabVIEW lists DataPlugins from the local computer or the National Instruments website.
  • Register DataPlugins–This VI includes the new Install DataPlugin by Name instance. You can use this instance to install DataPlugins to the local computer from ni.com/dataplugins.
  • Miscellaneous VI and Function Changes:
  • Get Class Hierarchy from Class Name–Returns an array of class names in descending order using a specified Class Name that inherits from Generic. For example, if Class Name is WhileLoop, this VI returns the following array: [Generic, GObject, Node, Structure, Loop, WhileLoop]
  • High Resolution Relative Seconds–Returns the value of the timer. This VI is similar to the Tick Count (ms) function, except that this VI provides a time stamp with a much higher resolution. You can use this VI to benchmark code with high precision.
  • Is Path and Not Empty?–If Path is a value other than an empty path or , this VI returns TRUE. Otherwise, this VI returns FALSE.
  • Variant Constant–Use this constant to pass an empty variant to the block diagram. LabVIEW always drops an empty variant when you use this VI. LabVIEW does not allow you to edit the value of the variant.
  • Report Error Msg:Send Error Report–Use this VI to send an error to an actor. The error will be handled by the Handle Error VI of the actor. If the error is not handled there, it will cause the actor to stop running.
  • TDMS Set Properties–This function includes improvements to the NI_MinimumBufferSize property by enabling you to set the minimum buffer size at the group or file level for a .tdms file.
  • Clear Errors–This VI includes the new specific error code to clear input, which ignores only the specific error code wired to this input. This VI also includes the new specific error cleared? output, which indicates whether the error referenced by specific error code to clear has been cleared.
  • Deploying Installers to Windows Embedded Standard Targets:
  • You can deploy a built installer to a target that runs the Windows Embedded Standard operating system. In the Project Explorer, under the Windows Embedded Standard target, right-click the build specification and select Deploy or Install.
  • Improvements to Loading Packed Project Libraries and Shared Libraries with the Same Library Version:
  • To simplify the task of loading shared libraries from VIs or packed project libraries that share the same version, LabVIEW 2014 suppresses the Load Warning Summary dialog box that earlier versions of LabVIEW launch when you cross-link shared libraries or packed project libraries. Cross-linking occurs when you load a shared library from a VI or packed project library and then load another shared library with the same name from another VI or packed project library in a different location while the first library is still in memory. When loading the second shared library, LabVIEW links to the location of the first shared library. Shared libraries or packed project libraries must have the same version number to be the same version.
  • Excluding Dependent Packed Project and Shared Libraries from a Build Specification:
  • In LabVIEW 2014, you can reduce the number of files LabVIEW copies when you create multiple build outputs that include the same libraries. You can specify to exclude dependent packed libraries and shared libraries from a build specification, and LabVIEW retains relative links to the source location of the excluded files. Otherwise, LabVIEW duplicates the packed project libraries and shared libraries in each subsequent output. To exclude these libraries, enable Exclude dependent packed libraries and Exclude dependent shared libraries on the Additional Exclusions page of the Properties dialog box for the build specification.
  • Setting the Destinations of Packed Project and Shared Libraries You Include with a Build Specification:
  • In LabVIEW 2014, you can specify the destinations of dependent packed project libraries and shared libraries included as part of a build specification configuration. To specify the destinations of dependent files, select Dependencies on the Source Files Settings page of a build specification. Enable Set destination for all contained items and Set destination for packed and shared libraries, and select destinations from the drop-down menu.
  • New LabVIEW Suites:
  • To enable you to meet visualization, analysis, distribution, and software engineering needs and build systems with confidence, LabVIEW Suites contain LabVIEW Professional Edition in addition to our most popular application software and add-ons in one package. You can select from the following three LabVIEW suites built around different application areas -
  • LabVIEW 2014 Automated Test Suite
  • LabVIEW 2014 Embedded Control and Monitoring Suite
  • LabVIEW 2014 HIL and Real-Time Test Suite
  • Enhanced Security for LabVIEW Web Services:
  • LabVIEW 2014 updates Web services to use the 1.0.1g release of the OpenSSL security protocol.
  • Linking VIs to Web-Based Documentation:
  • To link a VI to web-based documentation from the Context Help window, select the Web-based Help option from the drop-down menu on the Documentation page of the VI Properties dialog box. Use the Help URL text box to specify the URL of the topic you want to link to a VI.
  • Linking VIs to Local Documentation:
  • To link a VI to local documentation from the Context Help window, select the Local Help File option from the drop-down menu on the Documentation page of the VI Properties dialog box. Use the Help path text box to browse to custom documentation on the local computer. Optionally, use the Help tag text box to link a VI to an HTML topic within a compiled help file or to link a VI to a bookmark within an HTML help file. Otherwise, leave the Help tag text box empty.
  • For example, if you specify a path to a compiled help file named My Custom Help.chm in the Help path text box, you can enter GettingStarted.html#Intro in the Help tag text box so the Detailed help link and the Detailed help button in the Context Help window link directly to the introductory information you provide in the custom compiled help file.
  • Programmatically Linking a VI to Web-Based or Local Documentation:
  • Use the Help:Use Web UR property in the Properties class to indicate you want to link a VI to a web-based help file. To specify the URL for the help file, use the Help:Document Web URL property in the Properties class.
  • You can link a VI to a local help file by wiring a VI Reference to the Document Path property and specifying the location of the help file on the local computer. Optionally, you can use the Help:Document Tag property to link to an individual HTML topic within a compiled help file or to a bookmark within an HTML file.
  • Protecting Data from Modifications with Write Filter VIs:
  • LabVIEW 2014 includes the Write Filter VIs on the Advanced File VIs and Functions palette. Write filters protect data from unwanted modifications by redirecting write operations to another location or overlay. Use enhanced write filters (EWF) to protect volumes and redirect writes to a disk location on another volume or to the RAM. Use file-based write filters (FBWF) to protect files and folders in a volume and redirect writes to the memory cache.
  • Previously, the Write Filter VIs required the LabVIEW Touch Panel Module. In LabVIEW 2014, the Write Filter VIs are available when you develop a touch panel application in the Project Explorer window. Support for touch panel applications requires the LabVIEW Application Builder, which is available with the LabVIEW Professional Development System.
  • Using the Touch Panel Project Template and Touch Panel VI Template:
  • The Touch Panel Project template helps you create projects that target a touch panel device running the Windows Embedded Standard 7 operating system. The project template includes a VI template that you can adapt for your specific touch panel application. Select File»Create Project and browse to the Touch Panel Project template. Use the Create Project dialog box to configure project settings, including the touch panel target and VI template. Refer to the Project Documentation folder in the Project Explorer window for more information about how to modify the project.
  • You also can add a touch panel VI template to an existing touch panel target. LabVIEW includes portrait and landscape templates whose user interfaces are preset to the touch panel device. These templates include controls and indicators that you commonly use in touch panel applications. Right-click a touch panel target and select New VI Template to add a touch panel VI template to the target. The Select a template dialog box appears. Select the VI template to use with the target.
  • Working with Touch Panel Targets:
  • LabVIEW 2014 includes support for developing, debugging, and deploying LabVIEW applications to a touch panel target that runs the Windows Embedded Standard 7 operating system. Previously, developing, debugging, and deploying touch panel applications required the LabVIEW Touch Panel Module. With LabVIEW 2014, you develop and debug touch panel applications on the host computer, from which you can deploy the touch panel application to the touch panel target. Support for touch panel targets requires the LabVIEW Application Builder. The LabVIEW Professional Development System includes the Application Builder.
  • LabVIEW Third Party Licensing and Activation Toolkit:
  • With LabVIEW Third Party Licensing and Activation Toolkit 2014, you can provide the option for users to deactivate an add-on if the add-on is licensed with the toolkit. To deactivate an add-on, select Help»Activate Add-ons to open the Third Party Add-on Activation Wizard. Select the add-on, click Deactivate, and follow the steps in the wizard.
  • BUG FIXES:
  • 46534: Enhance error filtering in Clear Errors.vi
  • 122057: Joining Numbers of Different Widths Produce Unexpected Values
  • 125936: Printing entire VI hierarchy does not include dynamic dispatch subVIs
  • 187861: A VI Snippet that contains a Property node for a front panel object results an invalid reference
  • 201104: Toggling Y scale visibility with multiple scales causes unreadable display of data on waveform graphs
  • 212845: When creating a VI snippet that contains a local variable, the VI snippet changes the variable to a Property Node and a Reference
  • 250791: In certain cases, the build array function does provide the option to concatenate arrays
  • 255617: Error 1502 can occur if dependencies are placed in non executing case structures
  • 276765: Classic controls do not have distinct names in QuickDrop
  • 276988: A Large Picture Ring constant can cause fpsane.cpp line 442 error
  • 277283: When creating a VI Snippet with code that contains a tab control, the snippet does not properly save the contents of each tab.
  • 286661: Issue with the LabVIEW Icon Editor opening with a white background when it should be transparent
  • 292652: VI Snippet can't be dragged from Chrome, Firefox or Safari
  • 306189: Deploying a Variable Library with an IO Alias to a RT Target Programmatically Returns Error 1
  • 308748: Memory leak when Using .net TextBox Append Method
  • 312130: Show Buffer Allocation tool shows that all inlined VIs are inplace
  • 313075: In some cases, wiring a constant to a case structure would result in the inability to build a LabVIEW executable with Error 1502
  • 362970: Can't link VI context help to an anchor in an HTML file
  • 367468: Wiring multiple inputs to Split Signals.vi causes LabVIEW to crash
  • 368959: LabVIEW crashes by replacing a cluster constant that is being viewed as an icon with either a string or a boolean constant
  • 369119: Renaming a library that contains a class which contains a strictly typed VI Refnum causes errors because the namespace in the refnum is not updated
  • 371391: For a specific VI, enabling debugging caused an order of magnitude performance degradation
  • 372668: The channel order is incorrect for the first TDMS group after using NI_MinimumBufferSize property.
  • 376763: Removing an item in an enum does not change focus to the next item in the list
  • 377978: When compared to the Index Array function, Delete From Array function has performance overhead when using it to index the last value of an array
  • 381960: LabVIEW runs out of images and crashes if you have large number of VIs in your user.lib palette
  • 382652: It is possible to make changes to the items of a typedef enum constant in the properties menu, but the changes do not take effect
  • 384551: A breakpoint inside the disabled case of a disabled structure is still hit when the VI executes
  • 386963: Creating a typedef from a cluster that contains an empty array constant throws a DWarn 0x283E632F in replace.cpp
  • 393436: Build.vi does not return any generated files when running an installer build specification
  • 397393: Internal Warnings 0xD1EED773 and 0x667BD7ED while changing name of a control
  • 397845: In rare cases, LabVIEW hangs when merging VIs with missing subVIs
  • 397918: Error 1502 sometimes occurs when building an application containing unreachable code in a case structure with a constant wired to it
  • 401646: Toggling the visibility of axis on a Waveform Graph with multiple axis causes the axis to overlap
  • 401731: Add valid "Window Run-Time Positions" from VI Properties to app builder Source File Settings - Customize VI Properties
  • 403179: LabVIEW crashes when wiring a variant constant to a digital waveform graph and save the VI
  • 403202: The Remote Front Panel Plugin for Chrome and Firefox needs to be installed on a repair
  • 403213: Creating a source distribution does not allow you to have a mix of code that is source only and not source only
  • 403263: Bookmark Manager shows bookmarks in the LabVIEW resource folder
  • 404038: Unevenly Sampled Signal Spectrum VI Uses Incorrect Sample Weighting
  • 404257: Merging two source only VIs resets the source only setting and makes the resultant VI not source only
  • 404512: Compiler Error csrc=0x3F when Match Pattern.vi is wired to a conditional tunnel
  • 404637: ctrl+z sometimes types a z character. The same behavior occurs for ctrl+c and ctrl+x
  • 406710: LabVIEW Crash when Inlined SubVI with Feedback Node inside of Parallel For Loop is called.
  • 407147: Opening the LabVIEW Icon Editor resets invisible layers to visible
  • 407471: .NET invoke and property nodes do not always load or relink to the correct assembly version
  • 407678: LabVIEW will crash if closed while a local debug web service is running
  • 408437: MouseWheel "ButtonMods" event data appears in English in French LabVIEW
  • 408624: Rare LabVIEW crash when a FPGA Target parent is drag-dropped and LV FPGA not installed or not licensed
  • 409889: "Build All" Fails while Building an installer when multiple build specifications are in a project
  • 410733: Ramp Pattern VI does not produce expected results
  • 410846: LabVIEW crashes when using concatenating tunnel mode on fixed-size array
  • 412912: LabVIEW Crash when VI has String Control Wired to Generate User-Defined Trace Events is Traced.
  • 413400: When configuring a new project in LabVIEW, the Project Root directory cannot be set to a network drive
  • 413502: Desktop Execution Trace Toolkit does not accurately identify creation/destruction of Data Value References
  • 417188: Officially support using VariantFlattenExp to flatten variants to previous versions
  • 417506: Building a Real-Time Executable with MathScript functions quadprog or fmin_qp causes LabVIEW to crash with DWarn 0x1472AD65
  • 417953: LabVIEW will crash on run if array on connector pane is wired to Flatten to JSON primitive
  • 418199: The reference to typedef objects returned by the FocusObj event structure terminal cannot be compared to regular object references
  • 418330: Rare LabVIEW crash while quick-dropping a primitive onto the diagram
  • 420007: Open URL in Default Browser.vi does not correctly handle hashtags in Compiled Help Files
  • 421458: Digital Waveform Graph can hang LabVIEW when writing badly overflown data
  • 422283: Renaming specific .lvlibs in a project can cause typedef enum constants to revert to default values
  • 422905: Attaching a comment to an object with a long label, the comment arrow will not point at the object
  • 424094: In certain cases, VI Scripting: RearrangeFrameByIndex function can crash LabVIEW
  • 424541: Upgrading code that contains an inplace element structure with auto grow disabled will turn auto grow back on
  • 424616: Block diagram constants don't inherit a typedef's default data when a new element is added
  • 425582: LabVIEW issues an internal warning when failing to save a VI in an unattended mode
  • 426108: Using an annotation list to visualize labels and arrows with offset in a XY Graph the offset for the labels sometimes disappears
  • 426280: Modifying the Minimum Value in the properties of a numeric control configred to Absolute Time can crash LabVIEW
  • 426285: In rare cases, a corrupt listbox does not output correct values
  • 426523: A specific large project fails to build with a GenIL error and then crashes if you do not select Disconnect Type Defs
  • 426788: Reading LinkedControl.Label.Text property of an implicit property node crashes LabVIEW
  • 426792: LabVIEW crashes when waveform graph cursors contain invalid scale values
  • 427421: In certain cases, LabVIEW would stall during installation at the NI Error Reporting section
  • 427673: The Actor Framework cannot be packed into a packed library
  • 428197: Creating an i8 array indicator/control for a property node adds a u8 array instead
  • 428253: If LabVIEW 2013 is installed, Application Builder includes the LabVIEW 2013 web service installer when building from LabVIEW 2012
  • 428273: Add High Resolution Relative Seconds VI to the Timing palette
  • 428357: Comparisons fail between empty fixed sized arrays and compare aggregates
  • 428767: Create SubVI does not respect the Options settings for terminal label position
  • 428872: System State Publisher incorrectly reports cached memory as "used" memory on Linux Real-Time
  • 429396: Application directory VI incorrectly returns paths when used within a .NET Assembly or LabVIEW built DLL
  • 429516: VI Snippets not working as expected in certain browsers
  • 429902: Application Builder Lists Windows XP SP2 as the system requirements when the LabVIEW Readme requires XP SP3
  • 430579: The Cubic Spline Fit does not output a linear function when the balance parameter is zero and the input arrays are less than seven elements
  • 431956: Calling a LabVIEW web service repeatedly causes a memory leak
  • 432447: "Adapt to source" doesn't work for FXP inside a cluster
  • 432614: Remote Front Panels in LabVIEW 2013 do not release the VxWorks targets after being disconnected
  • 433514: Dragging and dropping groups of arrays between clusters will sometimes cause a rare LabVIEW crash
  • 433551: LabVIEW crashes when deleting an realtime target target from a project without realtime support installed
  • 433687: Application Builder doesn't provide a way to set the CFBundleIdentifier in the Info.plist file on Mac
  • 435028: Array constant does not auto resize when inner control is edited and resizes
  • 435029: Updating a typedef does not cause a block diagram constant to resize correctly
  • 435259: LabVIEW Dialogs sometimes display offscreen with multiple monitor setups
  • 436784: Scripting method ClusterConstant.AutoSize crashes LabVIEW
  • 437814: Open Sessions VI from visa.llb does not work properly in LabVIEW 2013
  • 438528: Subdiagram Label changes are not tracked in a VI, which does not mark the VI as needing to be resaved nor prompt the user when closing the VI before saving
  • 438550: Mouse Wheel events show the incorrect coordinates for Controls and Splitters
  • 438646: LabVIEW sometimes crashes when viewing the context help and deleting an input wire to a polymorphic VI that automatically adapts to inputs
  • 439026: Building an Application with Enable ActiveX server selected will crash all localized versions of LabVIEW
  • 439041: In certain cases, a memory leak occurs when using User Events
  • 439642: LabVIEW 2013 SP1 on Mac has an incorrect installer warning claiming we do not support Mavericks
  • 439710: Launching a right click menu on an xcontrol causes an increase in CPU usage
  • 440114: Executing a TestStand sequence with LabVIEW VIs in a user interface running in the LabVIEW 2013 Development System causes delays at the beginning of execution
  • 441769: Long build path on Mac OS X results in temporary files that prevent build
  • 441783: LabVIEW Class VIs loaded from an unexpected path can sometimes load broken
  • 441892: Quick Drop shortcut Ctrl-T does not work correctly for matrix and array constants
  • 441894: Moving the label of a typedef constant through scripting moves the constant instead of the label
  • 442743: Cutting text from one free label and pasting into another with the autotool disabled crashes LabVIEW
  • 444095: Remove Stacked Sequence Structure from the palette
  • 444412: LabVIEW sometimes crashes with exception 0x558A98DB when searching a block diagram containing tab controls using the find dialog
  • 445027: Calling multiple LabVIEW built .NET assemblies from any .NET language fails with Error 1
  • 445456: webservices.ini is not installed on Linux RealTime
  • 445981: A memory leak occurs when calling a custom ActiveX Control function which returns a UInt64
  • 446265: Duplicating and renaming a LabVIEW project and saving to the same folder can result in the deletion of non-NI files, such as a text file
  • 446367: Excel reports sometimes appear empty until user forces a redraw of the data-sheet, for example by double-clicking on the graph.
  • 447072: Wait (ms) VI does not work on NI Linux RT Target if wait is longer than 30000 ms
  • 450094: The menu option Project>Create Project will sometimes open a file explorer window to the template folder
  • 450755: Modifying Meter, Gauge, or Knob dimensions in a tab control resizes controls incorrectly
  • 451107: In some cases, LabVIEW asks to save code changes when no changes were made
  • 451499: LabVIEW Run-Time Engine crashes when it loads a lvproj containing Network Variables using Strict TypeDefs
  • 453896: Error message encountered during TestStand Deployment Utility build process may show incorrect list of VIs
  • 457434: In LabVIEW 2013 SP1, removing a file from a class and then adding that file back to the same class can crash LabVIEW
  • 461051: In certain cases, configuring a For Loop for parallelism which contains a Wait on Asynchronous Call function can crash LabVIEW
  • 461196: Scan From String VI returns Error 1 with "%t" as the format string input
  • 466641: Using a User Event reference in a reentrant ActiveX callback VI can cause LabVIEW to hang
  • 470943: When registering multiple .NET callbacks in one Register Event Callback function, LabVIEW 2013 SP1 returns Error 1172