PDFKnown Issues by Date
The following items are known issues in LabVIEW 2009 Statechart Module sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 100185 4BTB979A Return |
Replacing a block diagram constant when configuring a statechart state node or transition node may not delete the original block diagram constant Replacing a block diagram constant with the "Select a VI..." option in the statechart state node or transition node configuration dialog may not delete original block diagram constant Workaround: Delete the original block diagram constant manually.
|
|||||
| 100729 Return |
Unexpected searching may occur when saving Statechart Communication nodes to a previous LabVIEW version Unexpected searching may occur when saving Statechart Communication nodes to a previous LabVIEW version Workaround: N/A
|
|||||
| 101248 Return |
Building a build specification may fail if it uses statecharts or their callers last saved in LabVIEW 8.5 Building a build specification may fail if it uses statecharts or their callers last saved in LabVIEW 8.5 Workaround: Save your statecharts and their callers in the current version of LabVIEW before attempting to build.
|
|||||
| 110487 Return |
Deleting cluster constant in statechart configuration guard/action diagram can crash LabVIEW In the Guard or Action diagram of the Configure State dialog box, if you try to delete the contents of a block diagram cluster that is typedef'ed, and then delete the cluster constant itself, LabVIEW might crash. Workaround: When deleting a cluster constant in the Configure State dialog box, delete the entire constant at once instead of deleting the contents first.
|
|||||
| 118558 Return |
Issue with copying/pasting states/transitions between different statecharts of the same name in different application instances Copying and pasting a statechart diagram from a statechart state or transition in one application instance to a different statechart of the same name in another application instance generates an error. Workaround: Ensure the statecharts between which you want to copy and paste states/transitions have different names.
|
|||||
| 159675 Return |
Cannot rename statechart groups If you try to change the name of a statechart group of triggers, you will not be able to. Similarly, if you create a new group of triggers, you will be unable to change the name from the default name initially assigned. Workaround: N/A
|
|||||
| 184024 Return |
Existing guard/action VIs may be locked in config dialog when debugging is off You may be unable to edit Guard or Action code in your statechart if you generated code with debugging turned off. Workaround: Enable Debugging and regenerate code for your statechart.
|
Document last updated on 11/5/2009
