hooovahh

I'm contacting Michael. Is this possibly an IT issue? Proxy issue? Corporate firewall? Just trying to gather information.

Okay what is the error message you get?

Dang and I thought I read every post clearly. Anyway I can't talk about the beta, and if a thing appears fixed in the beta or not, but I think I can say that I made NI aware of this in the beta forum. If a CAR is assigned I'll post it here.

There isn't a release date for SP1, but I'd suspect (with no inside information) I'd guess November-ish due to that being 6 months after 2017 release. I must not drag from one BD to the other very often because I didn't know this was an issue. With two relatively simple VIs dragging around works fine and is pretty responsive. But as soon as I try with a project that has actual code in it I see the 1Hz refresh you are talking about. I did however find an INI key you might be interested in which reverts some of the 2016 live drag functionality. If you add LiveDrag=False to you LabVIEW.ini you lose the live drag functionality, but I also found that dragging from one BD to another seems to be improved as a result. EDIT: Or pressing 'x' mid drag to disable it for that drag seems to help.

Yeah this is somewhat known. Some times I have a page up for a while then go to reply, I type in a bunch of text and hit Submit Reply only for nothing to happen, but at least my text I entered is still there. I will copy the text, refresh the page, paste it in, and reply will work due to a page timeout. It is possible your page was just timing out and not allowing for uploads. I'd suggest refreshing the page (copying what you entered first) then paste it, and then try to attach. If you are still having issues I'll contact Michael, since this admin level issue isn't something I can really do anything about.

So I'm missing a VI in that snippet for the decoding part which looks like some kind of NI get icon library. But attached is the VI that was that snippet, and another way of getting the icon if you don't mind opening references. I think Jim was interested in getting the icon without VI Server for its usage in VIPM. Get XNode Icon.vi

Oh only a known bug for 11 years on value change not working properly? Kinda seems like something someone might run into all the time. Oh so true, new quote for a signature? Possibly.

You got me wondering so I went and looked at the service requests I've opened and...it only lists 8 in 5 years. I think it is missing some maybe due to account weirdness, but on top of that I realize I gravitate to the forums a whole lot more for support, which does make it harder to track. Many times I'll have some issue like a crash in LabVIEW when I run a project. Then I'll start minimizing the project to isolate the problem, then I'll post the test VI on the forums so others can try it out and convince me that it isn't just my setup causing the crash. Then eventually someone from NI will chime in and say yes this is a bug I've assigned CAR XXX. If it is a major issue with no work around then yes I'll contact NI directly but if the issue can be isolated it can usually be worked around. Anyway of the 3 service request I've opened in the last year, one couldn't be reproduced, and is still a point of concern but hasn't been an issue in months, one I opened yesterday but is looking good, and one I opened a month ago because of a licensing issue that NI hasn't been able to resolve. That being said I've always been impressed with NI's ability to help out. I also thought Microsoft did a pretty good job with support too. One major downside of the forums for CARs is while it might get more attention at first, it is easy to just lose track or ignore requests.

Oh lovely. Yeah I noticed this was removed for NXG and complained, but didn't realize this extended to current LabVIEW.

Glad you got it working (partially at least) my suggestion would just be to repair stuff. Yeah it takes a while to reinstall MAX, LabVIEW and all the other stuff but it has worked for me most times LabVIEW refuses to start.

Oh the mysteries of .Net. It seems Windows 10 comes with at least 4.6. The code I developed is based on the link you provided, which is why I'm also confused why that works and mine doesn't.

What are some of your environment versions? I've tested this on Windows 7 x64 LabVIEW 2015, 2016, 2017 32-bit, and with some success on Server 2012 x64 LabVIEW 2015. I say some because it runs and works, but the preview images aren't shown in the selection UI. Really that is just a terrible hacky solution and I regret doing it. If I get some time I may try to revert back to the picture control solution. You're issue definitely has to do with the .net stuff.

Search your feelings, you know it to be true. The dark side is the only path forward. (unless someone from NI comes here which does happen but I think this is specific enough of a problem to ask that group) This really does sound like a software limitation, potentially in the kernel. The fact that the 15th device is pluged directly into the cRIO not through a hub is the key piece of information.

I'm curious what USB hardware you are using. It sounds like you have 16 individual devices and might fair better with a single 16 port device. I've used these successfully on Windows, but never had access to one and an RT controller. I know of no reason why this limitation would be there, but NI might and you should probably crosspost here. EDIT: You may also want to update this post with USB devices you were successful with. I haven't found an FTDI, or Prolific chipset that hasn't worked yet.

One work around I've yet to try is I've heard you can set the window to be transparent in the VI properties. And then make it not transparent when the VI starts running. Not sure if this actually works but I've seen it on several of my programs and just haven't looked into fixing it since it is a pretty minor issue that no one has complained about except me.

I've always added new items to the end. It does make organization look a little out of order but functionally I've never had a problem. The 2014 approval dialog does come up once in a while when I'm removing items, and seems to work well. Maybe you are removing, moving, and adding too many items at once and the attempt at preserving values fails. If you do one edit at a time I wonder if you'll see the problem.

eah I know you were specifically asking about picture rings, sorry I can't help on that topic. But I thought showing you an alternate solution that can accomplish a similar UI would help. Having the other functionality that a pict ring gives might be a pain to implement for sure. Having a small window pop up on top when the user clicks a picture box might be difficult since the picture box will be rendered as a separate object and often times is forced to be always on top of all other UI elements, but I think that is limited to a single handle, and a separate VI could be used. I do wish more attention went into the features of the picture ring. Replicating all of the functionality of a picture ring in an XControl seems like alot of work for just a little added functionality.

I've posted this several times now but figured I'd give it a try to see if it works with vector images and the first EMF I tried it on appeared to work. Attached is the .Net image manipulation stuff that demonstrates loading an image into a picture box which supports alpha layer transparencies, ICO and TIF image selection, and zooming with the control which in this demo changes size with the window resize. Here was the last update I made on the dark side. This attached example just has an EMF that is included to test with. Image Manipulation With Ico and Tif Fix emf.zip

Okay well no sense in derailing the conversation more but had success dragging it from explorer, to the BD when it was saved to the desktop, and the downloads folder, maybe I have some other INI keys doing something else.

Oops, so there is apparently an INI key I had that I didn't realize made this work which might be another reason to not use it. You need this: ExternalNodesEnabled=True With that you can wire an array of strings to the VIM I attached earlier in 2015.

Nope you can just drag and drop the VIM I attached to a BD and it works as expected.

That's not true. In 2015 (and several versions back) you could rename a .VI to .VIM and the inputs and outputs would have type propagation throughout the subVI just like it does in 2017. The difference is that in 2016 and older it was implemented as an XNode and had issues with class (something XNodes have a problem with) and as a result working with the XNode and forcing an update also wasn't as easy. Oh and the wires wouldn't break if there was a type problem, it would just not work and tell you the subVI was broken, but wouldn't allow you to see the VI or know which wire types it didn't accept. VIMs worked back then, but not nearly as well as 2017 and I wouldn't really recommend using it. I presented on XNodes and VIMs at NI Week 2016. EDIT: Apparently you also need this in your LabVIEW.ini: ExternalNodesEnabled=True Remove Duplicates 2015.vim

http://digital.ni.com/public.nsf/allkb/F0FC362A73C794BA86257C6700692B0B And an idea exchange item to make this easier. https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Add-right-click-option-to-delete-class-mutation-history/idi-p/2594921

In my typical development cycle I keep looking forward to the next release (2017 SP1) imagining it will fix all of my stability issues. Not that my system is unstable, just that long delays in editing, and saving, make for a painful development process. Oh right positive. Rapid prototype and performance testing with small VIs is fun. For performing some kind of custom filtering, I'll sometimes write it 2 or 3 ways to get the same result, and then throw random data at it and see which performs the best. Then implement that into the main application.

Thanks rolfk for saying what I was thinking. That being said if we are talking about a cRIO with an embedded UI thing in theory things work the way you described, but I simply haven't heard enough from other developers, and haven't had enough experience with it to say one way or another if it behaves differently. YMMV indeed. If you are seeing some reproducible issue I'd ping NI on it. It is possible there is a bug in some UI behavior, or optimization that could be made.