Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/13/2015 in all areas

  1. LabVIEW 2015 leaked screenshots via Hollywood movie? Probably not.
    1 point
  2. Nice work. Don't over-reach for a first release. Named pipes for progress bars are a stateful digression from just showing a dialogue. Maybe take stock and put a stake in the ground of where you are - package and clean. Then look at that for version 2. Productionise. Then you can incrementally add features under version control. Just a thought
    1 point
  3. Wow, quite some traffic in this thread ... As I mentioned, I can now use API-Calls to find "my" parent window. Just curios, which call will be, Dll-Calls to get Process list and than look for the window handle of the LabVIEW application or use the "Get HWND and PID" and obtain there the "MaiWindowHandle". BTW, I also added a progress bar example of the TaskDialogIndirect. I also tried to implement a few "NamedPIpe" functions. Perhaps you guys can have a look? Especially the Named Pipes (I only found some old code, using a wrapper dll, which I did not want) will not work ... Even I thought I just translated the examples of msdn (https://msdn.microsoft.com/de-de/library/windows/desktop/aa365588%28v=vs.85%29.aspx https://msdn.microsoft.com/de-de/library/windows/desktop/aa365592%28v=vs.85%29.aspx) to LabVIEW code... WinAPI.zip
    1 point
  4. Can't wait for one of the most entertaining events of NIWeek. The LabVIEW Tools Network team will again be donating a brand-new myRIO for the Door Prize again this year. <Trippy, plasma app tornado not included>
    1 point
×
×
  • Create New...

Important Information

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