Fab
-
Posts
193 -
Joined
-
Last visited
-
Days Won
15
Content Type
Profiles
Forums
Downloads
Gallery
Everything posted by Fab
-
Arnoud bringing back the Design Kaleidoscope: balance skills, experience, tools as well as SMURF. #CLASummit Rome #LabVIEW @NIglobal
-
Can't wait for #CLASummit Rome next week. Safe travels to all Certified #LabVIEW Architects attending. @NIglobal @niukie @CLASummit
-
Next time you meet a new customer or a potential collaborator: Strangers & Coding - Can Rock Help? http://t.co/sR6ds6DC1X via @WiresmithTech
-
I rely on #JIRA & #techsilence @ night "10 Ways to Stop Lack of Sleep From Killing You..." by @jeff_haden @LinkedIn https://t.co/OlU0shh5jx
-
Cool new feature in #LabVIEW 2014 SP1 - Notice Anything New? http://t.co/YEuS8tDTPv via @WiresmithTech
-
Another great post: 4 Lessons Learnt Unit Testing LabVIEW FPGA Code http://t.co/4eajsJRGF5 via @WiresmithTech
-
Mark, I agree that posting to YouTube should be decided by each presenter. I have posted my videos to YouTube as well. Thanks again for doing this! Regards, Fab
-
My favorite part of the #clasummit is the breakout sessions: no slides, free format, feedback from great CLA minds & NI R&D #LabVIEW
-
AristosQ and Dmitry discussing how to integrate mediator into Actor Framework #LabVIEW these discussions make #clasummit extremely valuable
-
Casey Lamer's presentation, music to my ears: test driven development, modelling, defining done, continuous integration #LabVIEW #clasummit
-
AristosQ: "knowing 1 is worst than knowing none if you don't know all" Norm talking about hardware abstraction layers #clasummit #LabVIEW
-
Norm Kirchner kicks of his presentation with an impression from movie "Office Space" #clasummit "don't make HALs that stink"
-
All you wanted to know about #LabVIEW #BratVIs and feared to ask. @RoebuckChris check @swatzyssdc comment https://t.co/Mry9vcJPuE
-
#LAF #LabVIEW Architects Forum meeting starting now. Join us at Cafe B @ NI or remotely. Details https://t.co/dBE2BFB3uF
-
See the thing is that if I turn highlight execution both the Event handler loop on top and the Message Handler loop on the bottom finish executing, the queues get destroyed, the events unregistered and destroyed, the whole code executes, gets to the very last node (in the extreme case the VI Server Abort VI method I added), seems to execute and then the running arrow never turns off. I am just pushing this to the list of "we will never know". It is definitely not the code, because just changing the launching with start asynchronous call to using the old Run VI method just works. The VI stops right after it executes its last node. And I was able to remove the abort. I will the customer if I can share the VI. I was just curious if anyone else had seen that weird behavior. -
Nope, this is a VI that one of my customers has been using in a project that calls other similar VIs asynchronously. This is the only VI to have that strange behavior. I tried desperate measures like calling the Abort VI method at the end of the code, and it would still continue to run after executing that last node. The only way to stop it was to press the abort control on the tools bar. Once we replaced the call and forget code with the Run VI method, it did stop and I was able to remove the abort method.
-
Join us, #LabVIEW Architects Forum meeting. Next Tuesday, Feb 17 at 6:00 PM CST. Remote attndees welcome https://t.co/dBE2BFB3uF
-
I know this is an old thread. But does anyone know what can cause an Asynchronous launched VI to stay running even though the entire code is done? I ended up just switching back for that particular VI to using Run VI method and that worked. Thanks, Fab
-
"Users remember early experiences with your product..." Documentation is important for reusable #LabVIEW codehttps://t.co/Im1zSiBUN5
