Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/19/2014 in all areas

  1. It flattens / unflattens the variant, replacing its type by the one of the other variant (so it's like a raw type cast):
    1 point
  2. Seeing everyone at the BBQ is one of the highlights of my year. Anybody got any limerick topic requests?
    1 point
  3. I don't know anything about the internals of LabVIEW window management, so I can't speak to whether or not what you're seeing is intended behavior when the windows are reparented via winapi calls. Here's a VI that may help, though. This password-protected VI (saved in LabVIEW 2013) calls a private VI Server property to suppress LabVIEW editor dialogs. Call this VI before you do your scripting, with a TRUE input. Then when your scripting is done, call it again with a FALSE input to reenable LabVIEW editor dialogs. <standard disclaimer here about using private LabVIEW functionality in production code> Suppress Dialogs.vi
    1 point
  4. You can set the INI variable and restart LabVIEW using two Invoke Nodes. You will have to confirm "Quit will abort all running VIs" and it should start back up with the correct setting. (LV 2012)
    1 point
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.