Darin
-
Posts
282 -
Joined
-
Last visited
-
Days Won
37
Community Answers
-
Darin's post in How to correctly use the outputs of Gaussian Peak Fit? was marked as the answer
From squinting on my iPhone I can tell that your constant '2' should be sqrt(2). Looks good otherwise.
-
Darin's post in Matrix Multiply slower on RT than PC? was marked as the answer
I do not trust individual benchmarks of two operations in parallel. Especially when RT gets involved. Try serializing the two functions and see what the timing difference is then.
-
Darin's post in Scan from string into Timestamp was marked as the answer
Try with a four digit year instead '%Y'. Just a guess.
-
Darin's post in Calling GetValueByPointer.xnode in executable was marked as the answer
The XNode uses a CLFN with the library wired by path. I have used this CLFN inside an executable, see if it works for you.
-
Darin's post in Can you get a strict VI ref without statically linking to the VI? was marked as the answer
Simply create a constant from the reference terminals of Open VI reference or any of the ACBR or CBR nodes and you get a VI Type Specifier constant. You can drag a VI on top of the constant to set the type, or choose browse under Select VI Class on the right-click menu. Either way, the VI you choose is not statically linked, it simply sets the type.
-
Darin's post in Get datatype primary color was marked as the answer
Use the default value property (assuming you have a control reference) as input to the Application Method aptly named "Data Type Color".
This is where the class browser Ctrl-Shift-B comes in very handy.
Also works in conjunction with wires and control terminals.
-
Darin's post in what are the function icons mentioned in figure below in stopwatch block diagram was marked as the answer
Those are local variables. <Insert snide remark here>
-
Darin's post in NaN to U32 behaviour changed was marked as the answer
It happened in LV10, and I would probably follow the excellent advice given in the linked post above and do the conversion explicitly yourself.
Changing undocumented and ill-defined behavior is uncool, but not unreasonable. (By the time you compound the decisions to not document the original behavior, then not document the new behavior, and then not document the change in behavior it does seem especially lame).
Relying on these undocumented behaviors is unreasonable. Unless you document the undocumented behavior you were expecting then you are just as culpable as NI, hopefully it was easy to track down (but not too easy that it was not a lesson learned). I loathe text comments in a graphical language, and especially the ones that tell you what a chunk of code is doing. I can read your code, but I can not read your mind (and I often forget what I was thinking a few weeks/months/years ago). If I am using an undocumented behavior or working around a known bug I will add a comment and when I come back to the code I pay attention because I know I went out of my way to comment on something.
And for those keeping score, my C++ compiler gives a very useful warning message when I try a conversion like this.