ID | Known Issue |
---|
223483
3PD8N0M8
Return | LabVIEW uses large amounts of memory when reading an entire wave file at once
The Sound File Read VI uses large amounts of memory to read an entire .wav file.
Workaround: Read the data from the .wav file in sections rather than in one large file.
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
36889
4999TKGI
Return | Import Shared Library wizard cannot recognize a function if the function declaration contains a default value
In the Import Shared Library wizard, LabVIEW cannot recognize a function in a header (.h) file if the function declaration contains a default value for a function parameter.
Workaround: Remove the default values of parameters in the header file. Instead, add the default values to the Configure VIs and Controls page of the Import Shared Library wizard.
Reported Version: 8.5 | | Resolved Version: 2009 32-bit | | Added: 09/01/2007 |
|
37020
4A37JOV9
Return | DataSocket functions do not handle Domain security correctly.
The DataSocket Open function returns error 1179 for any attempt to connect to a shared variable that has security enabled, even if the correct user is logged in.
Workaround: Drop a shared variable node on the block diagram and run the VI once; you can delete the variable node and DataSocket security will continue to work.
Reported Version: 8.2.1 | | Resolved Version: 2009 32-bit | | Added: 09/01/2007 |
|
37271
45I650CI
Return | The Import Shared Library wizard does not support macros inside of function declarations
The Import Shared Library wizard does not support macros inside of function declarations in the header (.h) file.
Workaround: Move any macros outside of function declarations in the header file.
Reported Version: 8.5 | | Resolved Version: 2009 32-bit | | Added: 09/01/2007 |
|
37448
44CEN7MQ
Return | Import Shared Library wizard cannot recognize multiple function declarations in a row
If you have a header (.h) file that contains multiple function declarations in a row, the Import Shared Library wizard recognizes only the first function declaration.
Workaround: Separate the function declarations in the header file.
Reported Version: 8.2.1 | | Resolved Version: 2009 32-bit | | Added: 09/01/2007 |
|
37575
3PD8N0M8
Return | LabVIEW uses large amounts of memory when reading an entire wave file at once
The Sound File Read VI uses large amounts of memory to read an entire .wav file.
Workaround: Read the data from the .wav file in sections rather than in one large file.
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
39161
401FEQTL
Return | The device ID input of the Play Sound File VI does not work on Windows
On Windows, LabVIEW ignores the device ID input of the Play Sound File VI. This VI plays sound only on the default sound card.
Workaround: Use the Sound Output Configure VI and the Sound Output Write VI with the Sound File Open VI and the Sound File Read VI or the Sound File Simple Read VI. Refer to the Sound File to Sound Output example VI for an example of this workaround.
Reported Version: 8.0.1 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
39604
49UBP4LE
Return | Write to Clipboard Method takes minutes and a lot of CPU
If you try to copy a large amount of data from LabVIEW to the clipboard, LabVIEW slows significantly and might become unresponsive. This was previously tracked as CAR 90497 and 3YJ87JCM
Workaround: N/A
Reported Version: 8.2.1 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
39823
4AIGSL00
Return | The progress bar in the Import Shared Library wizard appears to hang
When you use the Import Shared Library wizard, LabVIEW displays a progress bar. This progress bar might appear to hang, even though the tool is working correctly.
Workaround: Wait until the generation finishes.
Reported Version: 8.5 | | Resolved Version: 2009 32-bit | | Added: 09/01/2007 |
|
39908
4AIBSAFF
Return | When synchronous display is enabled, disconnecting and reconnecting to a LabVIEW Real-Time target performing image display in a loop causes the Real-Time target to hang
If you enable synchronous display on an image display control and then update the control in a loop on a VI running on an Real-Time target, LabVIEW hangs after disconnecting and reconnecting to the target. This issue might occur when you want to run an application that can perform a headless operation, but you still want to perform image display in a loop.
Workaround: Right-click the image display control and select Advanced»Synchronous Display from the shortcut menu to disable synchronous display.
Reported Version: 8.5 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
41530
4DJFJM00
Return | Advanced Storage VIs Do Not Work in a LabVIEW Development System with a Different Language
If you move the Advanced Storage VIs to a LabVIEW development system with a different language, the VIs do not work because the object types and property names do not match the names in other languages.
Workaround: To correct this problem, use the internal, language-independent object types and property names.
Reported Version: 7.1 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
41531
4DJFK100
Return | If you create a new, untitled VI while using the Storage VIs, the numbering of the untitled VI might be inconsistent.
Workaround: This issue is does not appear to be reproducible in LabVIEW 8.5
Reported Version: 8.5 | | Resolved Version: 8.6 | | Added: 09/01/2007 |
|
46442
2BCDF100
Return | Remote Panel not correctly displaying hidden/disabled controls when server is a built app.
Clients viewing a front panel remotely might see different behavior depending on whether the front panel they are connecting to is from a built application. Specifically, if the front panel is from a built application, any programmatic changes to the front panel made before the client connects to the front panel are not reflected on the client computer. For example, if a Property Node changes a caption on a control before a client connects to that front panel, the client will see the original caption of the control, not the changed caption.
Workaround: N/A
Reported Version: 6.1 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
46449
2JQ91R6I
Return | LabVIEW's Hierarchy Window does not show the labels of the VI's for print out
When you print the VI Hierarchy window, LabVIEW does not print the VI labels.
Workaround: This is already hadled in LV2009; In the right-click "View" menu choose "Always show Labels". Then go ahead and print
Reported Version: 6.1 | | Resolved Version: 2009 32-bit | | Added: 09/01/2007 |
|
46630
2VO0SF00
Return | DataSocket/OPC Leaks Memory when repeatedly using ActiveX VIs to perform open-write-close
If you call the DataSocket Open, DataSocket Write, and DataSocket Close functions in succession repeatedly, LabVIEW leaks memory.
Workaround: To correct this problem, call the DataSocket Open function once, use the DataSocket Write function to write multiple times, and then use the DataSocket Close function.
Reported Version: 7.0 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
46965
38ECIGX3
Return | DataSocket HTTP protocol does not work in a LabVIEW built DLL
You cannot use the http protocol with the DataSocket VI and functions in LabVIEW-built shared libraries.
Workaround: N/A
Reported Version: 5.0.1 | | Resolved Version: 8.6 | | Added: 09/01/2007 |
|
47103
3BS49JS8
Return | Dialog box and open datasocket conflict
If a dialog box is already open, you cannot use the DataSocket Open function.
Workaround: This is due to threading deadlock in LabVIEW -- both attempt to utilize the UI thread. Avoid using dialog boxes when other threads require the UI thread in this and future versions of LabVIEW.
Reported Version: 7.0 | | Resolved Version: 8.6 | | Added: 09/01/2007 |
|
47212
3EIB4MS5
Return | No prompt to add a comment in the revision history on close
If you select the Prompt for a comment when the VI is closed option on the Revision History Properties page, LabVIEW does not prompt you to add a comment to the History window when you close the VI.
Workaround: Select the Prompt for a comment when the VI is saved option on the Revision History Properties page
Reported Version: 7.1 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
47436
3IKBUP99
Return | Zip build provider and Zip VIs do not support multi-byte character encodings.
The Zip build provider and the underlying Zip API provided in the File I/O palette do not support paths with multibyte character encodings. Some upper or lower bytes of multi-byte characters decode into disallowed ASCII characters when not configured correctly.
Workaround: Ensure that the full filepath to zipped files does not contain multi-byte characters.
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
47791
3MRDJ300
Return | Subpalettes need to be context aware, i.e., need to show/hide when owning library is locked/unlocked
LabVIEW does not correctly hide subpalette menus that belong to locked project libraries.
Workaround: N/A
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
47819
3N68LE00
Return | 2GB file size limit of datalog files
The maximum size of datalog files is 2 GB.
Workaround: N/A
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
47857
3NHFKMSU
Return | ActiveX event unregistration did not execute properly after the VI goes idle
If you register an ActiveX event, you must unregister the event explicitly. Otherwise, memory leaks might occur because the ActiveX control does not know that the client has disconnected.
Workaround: Always unregister event using "Unregister For Events" node.
Reported Version: 7.0 | | Resolved Version: 8.6 | | Added: 09/01/2007 |
|
47891
3NRGJTI7
Return | Sound Output Set Volume VI doesn't set the volume on a per-channel basis
The Array instance of the Sound Output Set Volume VI does not use the volume input to set the volume on a per-channel basis. Instead, this VI uses the first element of the volume input as the sound level for all channels.
Workaround: N/A
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
47977
3OLE2573
Return | DataSocket and Fixed Size Array Do Not Work
You cannot use front panel DataSocket data binding with fixed-sized arrays.
Workaround: Uncheck autopreallocate arrays and strings in the VI properties execution category for all VIs not intended to run on an FPGA.
Reported Version: 7.1 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
48016
3P7CBB4Q
Return | Unsigned int32 loses value in formula node when you write to the most significant bit
If you wire a hex value greater than x7FFFFFFF as an unsigned, 32-bit integer to a Formula Node, LabVIEW coerces the value to 0. If you use a negative number for U32 input/output variable, LabVIEW will coerce the value to 0.
Workaround: 1. Use the Mathscript node or LabVIEW code for the operation that involves an unsigned, 32-bit integer. 2. Use signed 32-bit integers instead of unsigned 32-bit integers in the formula node.
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
48100
3PCAD0J1
Return | Save As»Substitute Copy affects all projects in memory, not just the one that does the Save As operation.
If you have Alpha.vi loaded into two separate projects, these are two independent VIs in memory. If you do Save As»Rename then, LabVIEW correctly renames the VI in both projects since the actual source on disk has changed. However, if you do Save As»Substitute Copy, only one project should change.
Workaround: Close any projects that you want to contain the original VI before performing the Save As»Substitute Copy operation.
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
48195
3Q9DN1ZU
Return | Deployment fails for all Variables in a Library if one Variable has a bad binding
LabVIEW fails to deploy all shared variables in a library if one shared variable has an invalid binding.
Workaround: To correct this problem, either delete the shared variable that has an invalid binding or unbind the shared variable.
Reported Version: 8.0 | | Resolved Version: 2009 32-bit | | Added: 09/01/2007 |
|
48349
3R8EFNKY
Return | VarClient on cFP reports "variable does not exist" if the variable is published by a host that has two ethernet adapters
Network-published shared variables do not function properly if multiple network adapters are enabled on the same computer.
Workaround: You can bind variable communication to a specific network adapter. This will allow variable communication to function normally on the bound adapter. It is not currently possible to perform shared variable communication on two network adapters simultaneously. For instructions on binding variable communication to a network adapter see KB 3WK9NH9A: Deploying Shared Variables to a Specific Network Card.
Reported Version: 8.0 | | Resolved Version: 2009 32-bit | | Added: 09/01/2007 |
|
48855
3W6K2TMQ
Return | Undo on a private data control can leave you in a state where File»Apply Changes is needed but disabled
Editing a private data control and then undoing the edits removes the documentation modification on the class. However, while the owning class is broken and expects you to apply the changes you made, the File»Apply Changes menu option is disabled on the private data control.
Workaround: Select File»Save or File»Close to save or close the private data control.
Reported Version: 8.2 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
48913
3WGFQJ2K
Return | LabVIEW class save prompts sometimes come at incorrect times.
If you right-click a control in the Project Explorer window, select Convert Contents of Control to Class from the shortcut menu, and then undo the conversion, LabVIEW might appear as if the class still exists and you might not be able to load a class of the same name as the control.
Workaround: Save all files that reference the class you created from the control. This clears the backups of the files and allows the class to leave memory.
Reported Version: 8.2 | | Resolved Version: 2009 32-bit | | Added: 09/01/2007 |
|
49093
3XHF1O2K
Return | Running a dynamic dispatch VI as top-level and another VI that calls the dynamic at the same time can cause unexpected termination of running VIs
When you run a VI by pressing its run arrow, that VI is referred to as the "top-level VI". A VI that is running top-level cannot be used as a subVI by another top-level VI. Normally if you run a VI top-level, any callers of that VI are broken until the VI finishes its execution. If you you run a dynamic dispatch VI as the top-level VI, callers of that VI are NOT broken. If you then try to run one of those callers, the dynamic dispatch VI might become idle. Eventually, any VIs using the class that the dynamic dispatch VI belongs to might break, or, in some cases, VIs may be in the strange situation of being editable while running.
Workaround: N/A
Reported Version: 8.2 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
49355
3YLB3DDX
Return | Instance VIs can be reported bad in mass compile log
If you mass compile VIs last saved in a previous version of LabVIEW and the VIs contain MathScript Nodes, LabVIEW might return error messages, but LabVIEW compiles and saves the VIs correctly.
Workaround: N/A
Reported Version: 8.2 | | Resolved Version: 8.6 | | Added: 09/01/2007 |
|
49753
40M9C8N8
Return | After you flatten a LabVIEW class to variant data, the private data control hangs if opened from the VI Hierarchy window
If you open the private data control of a LabVIEW class from the VI Hierarchy window, LabVIEW might hang when you try to close the Control Editor window for the private data control. This issue occurs if the only LabVIEW class data in memory is contained in variant data. For example, you might delete all LabVIEW class controls and constants and then remove all LabVIEW classes from the LabVIEW project, but variant data with class data still might exist in memory.
Workaround: Close the VI that contains the variant data with the value of the LabVIEW class.
Reported Version: 8.2 | | Resolved Version: 8.6 | | Added: 09/01/2007 |
|
50061
42NAR8SA
Return | Center justified tables display improperly when overlapping with the front panel origin
When you add a table control to the front panel so that it overlaps with the vertical origin of the front panel, LabVIEW displays center justified columns off center when you type text. The cells appear to float or move horizontally until aligned with the vertical origin.
Workaround: Move the table away from the front panel's vertical origin.
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
50165
4367OV4I
Return | VI in web browser with top-level window or dialog window style does not draw.
If you create a VI, select Top-level application window or Dialog options from the Window Appearance page in the VI Properties dialog box, and publish the VI to the web, when you view the VI, it uses the default window style instead of the style you selected. This issue was formerly documented as issue 51263/47MA31QO.
Workaround: N/A
Reported Version: 8.0.1 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
50420
44CG88SN
Return | Update the Pulse Transition Measurement Express VI
The terminology and measurement definitions for the Transition Measurements VI comply with IEEE Standard 181-2003, IEEE Standard on Transitions, Pulses, and Related Waveforms. However, the Timing and Transition Measurements Express VI does not comply with this IEEE Standard.
Workaround: The Slew rate refers to the transition slope. The Preshoot refers to the pre-transition undershoot (rising pulse) or the pre-transition overshoot (falling pulse). The Overshoot refers to the post-transition undershoot (rising pulse) or the post-transition overshoot (falling pulse).
Reported Version: 8.5 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
50616
45ME5NJ1
Return | Cannot create an override member VI for both a child class and a grandchild class unless you first save the VI that contains the child class
You cannot create a VI that overrides the functionality of a child class and then create another VI that overrides the functionality of a grandchild class unless you first save the VIs you want to override. Thus, if you right-click a LabVIEW class in the Project Explorer window and select New»VI for Override from the shortcut menu to create child:A.vi, you cannot select New»VI for Override for the grandchild class to create grandchild:A.vi until you save child:A.vi. This issue occurs because you cannot have two VIs in memory with the same filename that have never been saved.
Workaround: Save the VI before you try to override any LabVIEW classes in that VI.
Reported Version: 8.2 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
51185
47FGSQCS
Return | Cannot save VI as the same name as missing library member VI
If a library contains a VI and the VI is missing, you should be able to save a VI as the same name as the missing VI in order to rebuild the missing VI. Currently, LabVIEW does not allow this.
Workaround: Delete the item from the library, save the new VI as the same name as the missing VI and then move the VI into the library.
Reported Version: 8.5 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
51311
477DKPBQ
Return | LabVIEW does not maintain child-only item setting when dragging an item within a tree
If you have a tree item with the child-only setting, and then drag it within the tree, LabVIEW loses the child-only setting.
Workaround: Use tree events to (1) get the child-only flag setting when the user begins a drag, and (2) reset the child-only flag after completing a drop.
Reported Version: 8.2.1 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
51862
49GE2P00
Return | Stand-alone application cannot load a class that includes polyVIs
A LabVIEW-built application that uses a LabVIEW class which contains a polymorphic VI does not function if the build options are set to include unused polymorphic VI instances, or if the polymorphic VI is in a plug-in to a built application that is outside the application.
Workaround: Choose to exclude unused polymorphic VI instances by selecting the Remove unused polymorphic VI instances option on the Additional Exclusions page.
Reported Version: 8.2.1 | | Resolved Version: 8.6 | | Added: 09/01/2007 |
|
52027
4A4GRP00
Return | Cannot use the 'New>>VI for Override...' dialog to create override of password-protected VI unless you have the password
You use the 'New>>VI for Override...' dialog to override an ancestor VI in a LabVIEW class if the VI you want to override is password-protected.
Workaround: Make a public VI which wraps the functionality of the the private VI, and instruct others to override the public VI.
Reported Version: 8.5 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
52263
4AJA41TQ
Return | Some operations on integer waveforms lose dt value
Some functions, such as Absolute Value and Logarithm Base 10 operate as you expect with DBL Waveforms, but when you apply the same functions to an I16 waveform, for example, the Absolute Value function works as you expect while the Logarithm Base 10 function loses the sampling interval dt value. LabVIEW resets the sampling interval dt value to 1.00. If the input waveform to the log function has a time stamp for t0, that value is also lost.
Workaround: Extract the Y-array of the waveform and perform the needed operations on Y before re-building the waveform.
Reported Version: 8.0.1 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
52297
4AIFC0R0
Return | Internal error related to locked tab control at fpsane.cpp line 369 and line 367.
If you lock a tab control that is already locked using Group»Lock, you might see two internal errors and LabVIEW may crash.
Workaround: Do not lock a control that is already locked. After the fact: copy the Tab Control from the block diagram into a new VI. It will show up unlocked in the new VI.
Reported Version: 8.5 | | Resolved Version: 2009 32-bit | | Added: 09/01/2007 |
|
52615
4BMANBJ1
Return | Multi-frame structures do not switch frames on undo
If you place a multi-frame structure (Event Structure, Case Structure, etc) on the block diagram, edit a frame in the structure, switch to a different structure and then press ctrl-z to undo the edit, LabVIEW does not switch to the frame that contains the change that you are undoing.
Workaround: N/A
Reported Version: 8.2 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
52990
4DJFMT00
Return | If a LabVIEW MathScript ignores findobj and gco function
If a LabVIEW MathScript contains a findobj or gco function, LabVIEW ignores the function and executes the remainder of the script as normal. LabVIEW does not return errors or warnings for these functions in a script.
Workaround: N/A
Reported Version: 8.5 | | Resolved Version: 8.6 | | Added: 09/01/2007 |
|
54942
41CE6I39
Return | Storage VIs do not recognize DIAdem date/time channels
The Storage VIs do not recognize the date/time format used in DIAdem date/time channels. When you use the Storage VIs to read data from a DIAdem date/time channel, LabVIEW converts the date/time data to a double-precision, floating-point number that represents the number of seconds since 01/01/0000.
Workaround: After LabVIEW converts the DIAdem date/time data to a double-precision, floating-point number, you can convert the double-precision, floating-point number to a more meaningful value.
Reported Version: 8.2 | | Resolved Version: 2009 32-bit | | Added: 09/01/2007 |
|
56958
4388O1FI
Return | Using a higher number of shared variables in a VI makes the VI respond slowly during development.
A VI with many shared variables on the block diagram, for example, 50, might respond slowly if you place another block diagram object, for example, a numeric constant on the block diagram.
Workaround: Place the Shared Variable node inside a subVI and use the subVI to access the Shared Variable node. If you already have a Shared Variable node on the block diagram of a main VI and you have already wired inputs and outputs, you can right-click the Shared Variable node and select Create SubVI from the shortcut menu. If you experience any additional issues after creating a subVI from the Shared Variable node, consider making the subVI reentrant.
Reported Version: 8.2 | | Resolved Version: 8.6 | | Added: 09/01/2007 |
|
57794
4API8A00
Return | Logos fails on Vista when PC-cillin is installed
If you have a version of PC-cillin Internet Security installed on Windows Vista, Logos does not work. Because of this issue, you cannot communicate with Ethernet instruments, such as FieldPoint modules, that use Logos.
Workaround: N/A
Reported Version: 8.5 | | Resolved Version: 8.5.1 | | Added: 09/01/2007 |
|
62996
48OAL61W
Return | View»Browse Relationships»This VI's Callers is disabled for dynamic dispatch VIs.
LabVIEW disables the View»Browse Relationships»This VI's Callers option for dynamic dispatch VIs. Because LabVIEW calls dynamic dispatch VIs dynamically, the VI Hierarchy window does not recognize dynamic dispatch VIs as callers because there are no calls until run time.
Workaround: N/A
Reported Version: 8.2 | | Resolved Version: 8.6 | | Added: 09/01/2007 |
|
63686
4A8CI3BW
Return | Import Web Service Wizard hung generating wrapper VIs
The Import Web Service Wizard hangs due to a recursive process when you attempt to generate a wrapper VI for a method or property that returns a reference to an object of the same class that the original method or property belongs to.
Workaround: 1) Try selecting only those methods that you want in the web service, and deselecting methods that you do not want to include. You also can select a single method, then after the wizard generates a wrapper VI which includes an open and close method, you can manually add a Invoke Node, then select the method you want. 2) If the wizard does hang, the selected methods might have a chain structure as a parameter. Web Service Import Wizard does not support that datatype. Click the Cancel button and exit the wizard.
Reported Version: 8.5 | | Resolved Version: 8.5.1 | | Added: 09/01/2007 |
|
63958
4AKFM1J1
Return | Changing the label of controls in private data control does not update actual class data type
If you use the Bundle by Name or the Unbundle by Name functions on a LabVIEW class and you change the name of a control in the private data control, the elements available for bundling or unbundling do not change. LabVIEW does not register the name as changed unless or until you make another more substantive change to the data type of the private data control.
Workaround: Modify the private data control by adding another element to the cluster, then choose File>>Apply Changes, then delete the extra element and do File>>Apply Changes again.
Reported Version: 8.5 | | Resolved Version: 8.5.1 | | Added: 09/01/2007 |
|
64067
4B24T15I
Return | When trying to write to a read-only .m file, MathScript does not show an error dialog box
Workaround: Remove the Read-only attribute from the file to be written
Reported Version: 8.2 | | Resolved Version: 8.5.1 | | Added: 09/01/2007 |
|
64174
4ARD3OV2
Return | Inserting Bundle by Name function into the LabVIEW class wire behaves differently than cluster
If you right click a class wire and select Insert»Bundle by Name, then the class wire gets inserted into the bundle node's element input (cluster value terminal), not the input cluster (cluster type terminal), as happens when the same procedure is done for a cluster.
Workaround: N/A
Reported Version: 8.2 | | Resolved Version: 8.6 | | Added: 09/01/2007 |
|
64277
4BCH23FN
Return | Dragging a Variable between projects if a Multiple Variable Editor window is open can hang LabVIEW.
If you've got a Multiple Variable Editor window open, and drag a variable from one project to another, LabVIEW hangs.
Workaround: Close all open instances of the Multiple Variable Editor window before dragging variables between projects.
Reported Version: 8.5 | | Resolved Version: 8.5.1 | | Added: 09/01/2007 |
|
65071
4C5FFLRK
Return | Data corrupted in place when modifed using property node in sub-VI
Updating an indicator within a sub-VI, then using a property node to update the value of that indicator overwrites the value of the wire in the top-level VI. This in essence passes data "backwards" through a wire, corrupting that wire's data in other places in the application. If the wire passed into this sub-VI has a constant for the source, the constant's value is modified to match the value written to a property node in the sub-VI.
Workaround: Workaround 1:
In LabVIEW 8.5, use an "Always Copy" primitive to on the wire that is passed to the sub-VI. This forces LabVIEW to create a copy for each branch in the wire, avoiding the corruption.
Workaround 2:
In the sub-VI, use a local variable to update the value of the indicator.
Reported Version: 6.0.2 | | Resolved Version: 8.5.1 | | Added: 09/01/2007 |
|
88787
3J0A89J1
Return | Zero element clusters not reported as an error for Type Defs/Custom Controls
Type Defs should not contain zero element clusters, but LabVIEW does not report an error if you have a type def with zero elements.
Workaround: This behavior has existed in LabVIEW for a very long time; this issue will be removed from the Known Issues Document in future versions. Please contact NI if you have questions on this issue.
Reported Version: 7.1 | | Resolved Version: 2009 32-bit | | Added: 09/01/2007 |
|
91250
453BD7Q6
Return | LabVIEW crashes on Japanese Vista if system locale is set to a Western European codepage
If you have a user name that uses Japanese characters and change the system locale to something other than Japanese, LabVIEW crashes.
Workaround: Make sure your locale and user name match.
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
91672
477M7K00
Return | Large amounts of data in combo box can appear to hang LabVIEW.
If you place a large amount of data in a combo box, on the order of megabytes, LabVIEW appears to hang by taking a long time to calculate wrapping.
Workaround: N/A
Reported Version: 8.2 | | Resolved Version: N/A | | Added: 09/01/2007 |
|
92298
4AOEJ5F2
Return | FP:Get Image, FP:Get Image Scaled, Print:VI to HTML, Print:VI to RTF, and Print:VI to Printer methods do not properly generate off-screen cluster images
These methods generate an incorrect image of the front panel when it contains off-screen clusters and the contents of all off-screen clusters appear blank in the generated image. This issue only affects the FP:Get Image and FP:Get Image Scaled methods when the Visible Area Only parameter is set to False.
Workaround: N/A
Reported Version: 8.5 | | Resolved Version: 8.6 | | Added: 09/01/2007 |
|
66461
4CUGA5RK
Return | Programatically Increasing Stacked Plot Chart Legend at Run-Time Crashes LabVIEW
If you programmatically increase the size of the plot legend through the property LegNumRows when using the stacked plot option of a waveform chart, often times, LabVIEW will crash with a DWARN in alloc.cpp line 655 or a DABORT in ThEvent.cpp line 190.
Workaround: Two potential workarounds:
1. If you write to the plot before you change the number of plots visible, then LabVIEW crashes less often. It appears to crash most often when you try to increase the number of plots before LabVIEW has allocated memory for the additional plots. If you are changing the number of plots while LabVIEW is writing to the indicator in a loop, it appears that it still crashes pretty often. This is only a partially viable solution, and only works if you can stop updating the chart while it resizes.
2. Place the stacked plot in another VI and show it on the front panel via a sub-panel. Then use VI server to programmatically update the chart.
Another workaround from a customer:
Since it is ok to reduce the number of displayed plots on a chart (but not ok to increase it), initialize the program with maximum expected number of plots and then allow the user to reduce from there. If the user wants to increase the number of plots, they must restart the program.
Reported Version: 8.5 | | Resolved Version: 8.5.1 | | Added: 09/10/2007 |
|
66776
4CUDBIVB
Return | Cannot Save Variant Data Returned by the LabVIEW ActiveX Server as a Control/Indicator's Default Value.
Cannot save variant data returned by the LabVIEW ActiveX Server as a control or indicator's default data. Saving the VI returns error: "LabVIEW: Memory is full. Cannot save VI [name of VI]. LabVIEW Save error code 10: Default data space."
Workaround: Use the VI Server interface instead.
Reported Version: 8.5 | | Resolved Version: 8.5.1 | | Added: 09/10/2007 |
|
64101
4B1CC3V9
Return | Scrolling graph's cursor legend corrupts front panel redrawing.
Controls and Indicators on front panel have become either totally invisible, distorted, or corrupt. This can happen if your front panel has a waveform graph with the cursor legend visible. If your graph has multiple cursors and a scroll bar in the legend the front panel image can become corrupt if you have scrolled to the very bottom of the cursor legend's list of cursors.
Workaround: Because this problem is due to the cursor legend, to fix the problem, replace any waveform graphs with another waveform graph (right click graph and click replace), then minimize and restore the LabVIEW front panel window and repeat for any waveform graphs which had a visible cursor legend. After your controls are restored, expand the cursor legend such that there is enough room to display your cursors without a scroll-bar.
Reported Version: 8.2.1 | | Resolved Version: 8.5.1 | | Added: 09/11/2007 |
|
65534
4CFADPDX
Return | Replace Array Subset Broken for 3D (or Higher) Arrays
Replacing a subset of an array with more than 2 dimensions (i.e. a 3D array) causes a broken wire and the VI to break. 1D and 2D arrays do not have this problem.
Workaround: N/A
Reported Version: 8.5 | | Resolved Version: 8.5.1 | | Added: 09/11/2007 |
|
65723
4CKGJ6Q7
Return | UDP Write Hangs LabVIEW When Called in a Loop with a High Loop Rate
Writing data at high rates using the UDP Write function within a loop can cause LabVIEW to hang and display a Resetting VI dialog. The rate at which UDP Write can be called in a loop is dependent upon the size of the data being written during each call to the function.
Workaround: Use the Wait until next second multiple function to control the loop rate and therefore how fast UDP packets are written.
Reported Version: 8.5 | | Resolved Version: 8.5.1 | | Added: 09/11/2007 |
|
66538
4CU3C5QW
Return | Updating a Typedef that Contains a Refnum that Contains a Cluster can Make LabVIEW Crash
Updating a typedef that contains a refnum to a cluster can make LabVIEW crash.
Workaround: N/A
Reported Version: 8.5 | | Resolved Version: 8.5.1 | | Added: 09/11/2007 |
|