Jump to content

Michael Aivaliotis

Administrators
  • Posts

    6,214
  • Joined

  • Last visited

  • Days Won

    117

Everything posted by Michael Aivaliotis

  1. Sorry about not getting back to you all. The upload issue is fixed. So Ton, feel free to upload your new add-on tool .
  2. So am i suppose to be hanging out on google+ ? Nobody is on there. Only @Fabiola31416 and Mercer. No really.

  3. Thanks Darin for the response. Ya, figures I'd run into a corner case. All is good now.
  4. Awesome thanks. I think I figured out why Application Instance Close? wasn't working for me. So the WM_CLOSE message requires a handle to a window name. My executable had a custom window name. I was using this as the window name. So the window was closing fine but the event was not firing and the app remained in memory. In your example, if you set the VI title name to CloseMe, instead of the default CloseMe.vi, then it won't work. So the message gets sent to the window instead of the app, which is also called CloseMe.exe. Now I just have to make sure that my window title doesn't match my exe name.
  5. The Application Instance Close? event doesn't work. If you can attach an example that works, that would be nice, but my tests show it not working. You're correct in catching my bug. Nice to have a second set of eyes . That was the problem. After I fixed that it worked as expected. So the updated diagram for anyone else needing this:
  6. How can my LabVIEW EXE application handle the windows WM_Close message correctly? I have tried the Windows Messaging Queue library without any resolution to this problem. The behavior I'm seeing is that my application window closes but the app remains running as can be seen by looking at the process list in Windows Task Manager. The images below don't show it but I've added the Quit LabVIEW function to exit the app. So far I've tried: Creating a loop that monitors the windows message queue: Application Instance Closed? Event: Panel Close? Event: I've read this thread but it didn't seem to address the issue head-on. Or I didn't see what the resolution was. Any help is appreciated. Thanks.
  7. I'm going to learn LabVIEW. So I can come to NIWeek with you.
  8. How to make a boring robot car into an internet sensation: http://t.co/iJw6mTdg

  9. Next time you pull out your smartphone to take a video, think how far we've come: http://t.co/U6DSal5E

  10. This is why LAVA exists. Love it!
  11. Ok, just got notified of this post. I'll fix it as soon as I can. Sorry about that. I have no idea what the problem is but no worries. I'll fix it. Thanks for you continued support of the LAVA Forums.
  12. So one time we had the LAVA BBQ, I noticed that the establishment had posted the following sign on the door to guide guests to the right place: I wonder where the heck they got that idea from. Now I know: http://www.l-a-v-a.net/
  13. Ya, thanks. Was on my list to fix and now it's fixed.
  14. The certification team should also keep tabs on this board.
  15. Some videos for those without internet in 2012. Sit back and catch up: http://t.co/w1AjSFdw

  16. Child Actor Henry Thomas's Audition For E.T. (Nails It) http://t.co/U5feHJKh

  17. Town Hall Debate Songified - this is awesome! http://t.co/vOaIGxiE

×
×
  • Create New...

Important Information

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