Sparkette Posted January 19, 2013 Report Share Posted January 19, 2013 Put that in a VI and click the Run arrow. The VI will keep running even though it looks like it's stopped. You can even use this to do VI scripting on a running VI! Since this is a private method, do not rely on this working, and don't complain to NI if it breaks something. Like with many other things I've posted, this is done at your own risk, and is posted only for the sake of sharing something cool I found. Quote Link to comment
Ton Plomp Posted January 19, 2013 Report Share Posted January 19, 2013 Hi flarn, could you add this (and possible other interesting events) to the LabVIEW wiki page dedicated to such events? http://labviewwiki.org/Private_methods Regards, Ton Quote Link to comment
Sparkette Posted January 19, 2013 Author Report Share Posted January 19, 2013 Hi flarn, could you add this (and possible other interesting events) to the LabVIEW wiki page dedicated to such events? http://labviewwiki.org/Private_methods Regards, Ton Sure I will, I wasn't aware that page existed. Quote Link to comment
Sparkette Posted January 20, 2013 Author Report Share Posted January 20, 2013 It's there now. http://labviewwiki.org/VI.Fake_Exec_State I also took the liberty of moving the page you linked above to "Private methods and properties"; when I get around to it, I'd like to add the Control.Genericity property, and I don't think we need a separate page for properties just yet. 1 Quote Link to comment
jcarmody Posted January 20, 2013 Report Share Posted January 20, 2013 I wonder why this method exists; it looks like an inside joke. Quote Link to comment
Sparkette Posted January 21, 2013 Author Report Share Posted January 21, 2013 I wonder why this method exists; it looks like an inside joke. I'm sure there's some internal process that requires something like that. Quote Link to comment
MikaelH Posted January 23, 2013 Report Share Posted January 23, 2013 My guess is to be able to build exe-files containing x-controls. Quote Link to comment
Sparkette Posted January 24, 2013 Author Report Share Posted January 24, 2013 My guess is to be able to build exe-files containing x-controls. Why do you say that? Quote Link to comment
lordexod Posted January 26, 2013 Report Share Posted January 26, 2013 There is one more much needed method. InternalCmdsHelp.vi Quote Link to comment
Sparkette Posted January 26, 2013 Author Report Share Posted January 26, 2013 (edited) There is one more much needed method. InternalCmdsHelp.vi I found that one too, but I'm pretty sure everything you can do with that command you can also do with the debug keys. What do you mean by "much needed" by the way? Edited January 26, 2013 by flarn2006 Quote Link to comment
MikaelH Posted January 29, 2013 Report Share Posted January 29, 2013 Why do you say that? When the Application builder renames VIs and X-Controls, the X-Control gets locked as soon as the VI using it gets loaded into memory. So my guess this feature or another hidden feature is used to be able to modified/rename locked items. Quote Link to comment
Sparkette Posted January 29, 2013 Author Report Share Posted January 29, 2013 When the Application builder renames VIs and X-Controls, the X-Control gets locked as soon as the VI using it gets loaded into memory. So my guess this feature or another hidden feature is used to be able to modified/rename locked items. It seems more likely that Fake Exec State would be able to do that. (not sure if it actually can) 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.