viSci Posted August 16, 2011 Report Share Posted August 16, 2011 Ok I give up. Apparently this can be done but I have looked under every scripting rock and cannot find it. Any hints? Quote Link to comment
Yair Posted August 16, 2011 Report Share Posted August 16, 2011 Basically, you need to create a new VI (with its type being control) and call the Save Instrument method on that VI. There's an example of this in this RCF plugin (although, if memory serves, that one doesn't save the VI) and a more complicated one here (which does save it). 1 Quote Link to comment
viSci Posted August 16, 2011 Author Report Share Posted August 16, 2011 Unfortunately the Save Instrument method is not available in the LV run time and I would not want to place that restriction on this application. I am trying to create a way to save all of the properties of a graph control. There used to be a property saver vi that was alluded to in some posts from a few years ago but the link is now broken. (I imagine it would be pretty hard to keep that kind of vi working for each release of LV) Quote Link to comment
Yair Posted August 16, 2011 Report Share Posted August 16, 2011 You can find the property saver here - http://www.kshif.com/lv/index.html There are methods called Get Property and Set Property which I believe should allow generic setting of properties. However, if memory serves, the require a 1D array of integers to identify the property (which you have no way of finding out) and I believe I remember someone from NI saying that they're not actually used anywhere, so they might be unsafe. 1 Quote Link to comment
viSci Posted August 16, 2011 Author Report Share Posted August 16, 2011 Wow! Konstantin Shifershteyn is a monster LabVIEW programmer. Amazingly it still works perfectly for Graph Controls even though it was last compiled in LV 8.5. Unfortunately it uses many deprecated properties and thus is not really safe to use I really wonder why NI could not give us a hand with this kind of thing. Quote Link to comment
Aristos Queue Posted August 16, 2011 Report Share Posted August 16, 2011 Deprecated properties are still safe to use insofar as they still work as documented. They just won't be safe to use in future versions when we stop supporting them. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.