LabVIEW
Why would VI's with my XControl want to be saved when opened?
A color map is part of the Sound and Vibration Toolkit.
What is interesting about it is that when it was "upgraded" to the Sound and Vibration Measurement Suite 5.0 it seemed to lose functionality, as I can't really edit any part of the graph like you can on most other types of graphs. This is perhaps why in 8.5 it's having some sort of "change"... but I don't know for sure.
But a quick explanation from the LabVIEW help:
What is interesting about it is that when it was "upgraded" to the Sound and Vibration Measurement Suite 5.0 it seemed to lose functionality, as I can't really edit any part of the graph like you can on most other types of graphs. This is perhaps why in 8.5 it's having some sort of "change"... but I don't know for sure.But a quick explanation from the LabVIEW help:
Colormap
Displays the results of transient analysis or order analysis on a customized intensity graph with a rainbow color scale. You can display these 3D results using colors to represent the third dimension. You also can add frequency or order lines to indicate locations of specific frequencies or order components on the colormap.
This was reported to R&D (# 4HFAQJRK) for further investigation.
Ben's VI is prompting to be saved when opened because the "State Changed?" Boolean was being set to TRUE during the Panel Resize event of the Facade VI.
The Panel Resize event should not be fired when the VI hosting the XControl is opened, but to workaround this situation, you can compare the NewBnds and OldBnds parameters returned during that event. If the two clusters are different, indicating a resize did occur, then set the State Changed? to TRUE, otherwise, do not set the Boolean. This will avoid setting the modification flag with the hosting VI, so you can close the VI without the prompt to save it again.
before ===>
fixed ====>
The Colormap XControl that Bob mentioned is modifying the State Changed Boolean (similar to Ben's VI) when you open the hosting VI, but is it doing it in multiple places. That is mentioned in the report to R&D as well.
Cheers,
Message Edited by Spex on 01-16-2008 05:44 PM
Ben's VI is prompting to be saved when opened because the "State Changed?" Boolean was being set to TRUE during the Panel Resize event of the Facade VI.
The Panel Resize event should not be fired when the VI hosting the XControl is opened, but to workaround this situation, you can compare the NewBnds and OldBnds parameters returned during that event. If the two clusters are different, indicating a resize did occur, then set the State Changed? to TRUE, otherwise, do not set the Boolean. This will avoid setting the modification flag with the hosting VI, so you can close the VI without the prompt to save it again.
before ===>
fixed ====>The Colormap XControl that Bob mentioned is modifying the State Changed Boolean (similar to Ben's VI) when you open the hosting VI, but is it doing it in multiple places. That is mentioned in the report to R&D as well.
Cheers,
Message Edited by Spex on 01-16-2008 05:44 PM
