09-01-2022 11:24 AM
This answer to a serious question makes me believe there are more examples of comments that you wrote/found that could brighten someone else's day.
I put this into a brute-force OCR VI I wrote before NI released a property node to get the event selectors in an Event structure:
I'm often tempted to write "If it was hard to write it should be hard to read.", but the minions here might take it seriously.
Please share your humorous code comments.
09-01-2022 12:08 PM
"This comment is for future Brian. Screw you."
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
09-02-2022 03:20 AM
Turns out most of my comments (actually feedback for improvements) isn't funny.
Sadly, this is the funniest.
09-06-2022 03:48 PM
If you didn't know... LabVIEW supports pasting images onto block diagrams. So you are not limited to text comments.
I can't post the actual thing here because of company confidentiality, but my favorite useful one so far is where a fellow developer just straight up took a cell phone picture of a whiteboard that had a complicated diagram on it showing the process and the calculations involved, and just pasted that in with an arrow pointing to it as a way of explaining the calculations that the VI it was in was doing.
To be silly I would occasionally put "reaction meme" images in code that I was reviewing from another developer to show to them later. That never gets committed to source control...
09-12-2022 11:59 AM - edited 09-12-2022 12:10 PM
@Kyle97330 wrote:
If you didn't know... LabVIEW supports pasting images onto block diagrams. So you are not limited to text comments.
I can't post the actual thing here because of company confidentiality, but my favorite useful one so far is where a fellow developer just straight up took a cell phone picture of a whiteboard that had a complicated diagram on it showing the process and the calculations involved, and just pasted that in with an arrow pointing to it as a way of explaining the calculations that the VI it was in was doing.
( #Busted)
In my defense, there had been a multi-hour meeting of the engineering team to explain, and agree on the algorithms and no one captured it on paper. I had the whiteboard signed and dated by each responsible engineer and manager.
09-13-2022 03:46 AM - edited 09-13-2022 03:48 AM
@Kyle97330 wrote:
If you didn't know... LabVIEW supports pasting images onto block diagrams. So you are not limited to text comments.
Just don't paste images of LabVIEW code into the diagram 😊.
That gets really confusing. Although you can resize the image, if you really insist on having LabVIEW code pasted as an image.
09-13-2022 06:18 AM - edited 09-13-2022 06:23 AM
wiebe@CARYA wrote:
@Kyle97330 wrote:
If you didn't know... LabVIEW supports pasting images onto block diagrams. So you are not limited to text comments.
Just don't paste images of LabVIEW code into the diagram 😊.
That gets really confusing. Although you can resize the image, if you really insist on having LabVIEW code pasted as an image.
It's getting to feel like a "Pick on Jay's code thread"!
Should I even admit that I have stuck documentation on a Global VI Block Diagram?
12-01-2022 07:31 AM