On a forum intended to discuss and provide help for LabVIEW, is it not obvious that you are able to attach LabVIEW code? I've seen requests for help with screenshots posted into every document type imaginable
Admittidly the 'create snippet' function is a little hidden in the Edit menu, but why would you think you can't upload a .vi?
There are some forums where you can't post a .vi (not talking about NI.com)
What i find more disturbing is the fact that some people keep posting images instead of VIs even if told to NOT do so (please post the VI instead!).
Sometimes i wonder if those people really want to get help or if they are just afraid to get a place in the Rube Goldberg thread......
I think it's great to get picked up on rubes, sure you get a red face but you learn something
It's great that that has become a little meme on the site for the past 6 years
My preference is for the images and not hte VIs unless digging is required.
Images can be viewed and commented on without having LV installed.
No one has ever started a thread requesting that an image from LV 6i by saved as an image fro LV 2012 or vise versa.
Yes, images! But not just any image - a VI Snippet is IMO the best way of attaching a VI. [Edit: Many times I include the snippet and attach the VI in the earliest version of LabVIEW possible]
Although it can be done directly from LabVIEW I prefer Ton Plomp's Code Capture Tool. It correctly handles references and is much easier to use. All you do is select some code, activate the Code Capture Tool, then click on the camera icon. It will save the snippet into a temporary file and put the location of the temp file into your clipboard.
This means that when replying to a post all you do is capture the snippet in LabVIEW, go to the insert image icon in the forum reply, click browse then do a paste from the clipboard. No need to save the snippet to some "Delete Me" folder on your desktop first. This is my favorite third party addon.
Now if only Ton could make the snippet include subVIs and be navagable (or is it navagatable?) so you could directly dig into structures using your web browser. That only leaves making the code snippet editable and then just throw in a run arrow
Steve Chandler wrote:
Now if only Ton could make the snippet include subVIs and be navagable (or is it navagatable?) so you could directly dig into structures using your web browser.
VIpreVIEW can do that, but it was never finalized into a usable tool - http://lavag.org/topic/7132-vipreview-interactive-vi-preview/page__view__findpost__p__41512