Snippets are broken?

[JÞB]

---

@LiliMcDonald wrote:

We have escalated the issue with VI Snippets to our community provider for further investigation. We will post updates when available.

---

Lili,

I would ask that you float an announcement on the LabVIEW board with some information like:

"We are currently experiencing technical problems with vi Snippets.  Please attach the actual VIs, back-saved as needed, while we resolve the issue."

We've become quite dependant on sharing snippets inline to aid the community and my guess is that a lot of threads may be effected from many users.  Attaching VI's is the obvious work-around until the new uploader gets fixed.

Thanks

[LiliMcDonald]

Thanks for the suggestion, Jeff. I have posted an announcement and floated it to the top of the LabVIEW board.

[aputman]

---

@RavensFan wrote:

I'm seeing that same problem also.

With this post.  http://forums.ni.com/t5/LabVIEW/The-distribute-object-tools-often-crashes-LabVIEW-2017/m-p/3659157#M...

Interestingly, that looks more like a Code Capture Tool snippet rather than LV built-in VI snippet.

And that brings up the question, how have people been installing the CCT in LV 2017?  Recent versions of LV, I've used JKI VIPM to install the CCT.  But VIPM doesn't seem to be updated yet to work with LV 2017.

---

When I tried to copy a snippet, the "drag to desktop" method didn't work but if you click the download button on the new image viewer, the snippet does work properly. 

[RavensFan]

aputman,

You definitely found a workaround there.  Using the download link does make it save as a working snippet image.

However, this should not be consider an adequate workaround.  Why?  At least in Firefox, when you do the save, it will save it to the download directory of the browser.  Then you have to drag that off of there and onto the desktop.  Only then can you drag it into a VI.  So it seems to add at least 2, or 3, or 4 more steps to the whole process.

[aputman]

Oh I definitely agree that it is not an ideal workaround but that is usually how workarounds "work", otherwise they wouldn't be a workaround.  

[RavensFan]

Let me poke and ask if there any headway has been made in improving the way snippets are handled by the forums.

I've avoided working with snippets posted in messages because it is such a pain under the new image format.  I just did one and found it is actually a 7 step process to get an image snippet into a block diagram where in the past it was only a 2 step process.

[LiliMcDonald]

Unfortunately, we do not have any news to share at this time.

[Hooovahh]

Still anything on snippets?  Some boards like the Idea Exchange don't allow attaching files, so the only way to express G based code is through uploading a snippet.

[wiebe@CARYA]

This hurts once or twice every day... I feel crippled.

[LiliMcDonald]

Unfortunately, we do not have any new updates on this.