hooovahh

Last I knew the forums had a minimum search length of 4 characters. At some point there was a warning if you searched for something with less 4 characters. I'm guessing the period is somehow ignored or reserved for some kind of special formatting.

Don't worry Brian will pick up the tab.

The first time you mentioned this I thought it was a nice gesture, now I think you are just desperate for friends...or an alcoholic. I'm down.

Yeah deploying to a target that I don't have the option to run source on the same OS sounds like a nightmare. Where I'm from that "throwing it over the fence" which usually results in dozens of builds trying to figure troubleshoot the issue. I'll agree this is a bad situation. But I think it would be worst if NI made the same decision in 2 years. LabVIEW is dead, long live LabVIEW. (hopefully)

In 2014 I had the privilege of being in on one of the early discussions around what would be NXG, before I was a Champion, and I think I was just a CLAD. They were interviewing each person one at a time with a set of questions and the last one was "What is your biggest concern with this decision by NI?" and my answer was some thing like "What are NI's plans if this fails?" Saying that this is my career they are potentially messing with, along with the negative effects internally at NI. They sorta laughed it off and said how unlikely it was but that they would do their best to go back to supporting the more classic LabVIEW. It probably is the right decision for them to make, but also a very difficult one. If it were me I'm not sure I would be able to see past the sunk cost fallacy.

Cloneable VI: Should work just fine. NI did a pretty decent job with VIMs, and has seemed to fix a few edge cases and bugs with them in recent versions. Should work just fine. Examples: Yeah I was lazy. A few of the older examples were intended to show special features of XNodes. But VIMs don't have all those special features. So instead of re-writing examples for VIMs and putting it in the package, I just didn't include any. I should have but wanted to get it out there and I was losing motivation.

Glad it helped. Is there a repository somewhere of these types of gifs? I'd love to have a library of controls or something. Like I mentioned a QControl can probably handle this well.

I've recently released the Variant Repository code as a package on VIPM.IO as VIMs. Some of the magic is lost going from a series of XNodes to VIMs, and even more wind is taken out of my sail by the fact that Sets and Maps can do what VRs did in a more native way. However I have some code I'd like to share that relies on Variant Repositories, so I cleaned it up for a release. And replacing those functions with Sets and Maps would mean my code could only be used by 2019 and newer. In the future when 2019 doesn't seem so new I'll probably remove the VR dependency. Or maybe I'm being lazy I can't tell.

To be clear I don't know that this is what JKI did, and no one told me they did this. I just know I didn't upload my stuff to VIPM.IO, and saw it was there which lead me to believe that this is what they did. The rehosting of BSD stuff is probably fine. The using LAVAG.org in ways that might go against terms of use might not be.

So I'll admit I was dragging my feet a bit when it came to VIPM.io. I sorta saw this as another standard leading to this XKCD. But the process is pretty slick, and pretty easy. And the fact that it seems to have already crawled LAVAs Code Repository means a few of my tools are already there and looking nice. One issue I saw is with the screen shot resolution limitation. 800 x 500 is a decent size, but I found some of my palettes didn't fit and needed to be shrunk to fit. Is this size limitation just to ensure it fits on the page well? Here is my array package and I needed to scale that image before uploading. I'd prefer just upload any size (within reason) and have the page scale it to fit the container, then clicking it can show the full size. Pretty minor and it works fine as it is.

I did use something a while ago that sounds similar to what you are describing. First I'd like to know if the OS it self is supposed to be on the USB drive too or not. If not I'd look into Thinstall or Thinapp which is virtualization software. Years ago I tried it and it worked for running LabVIEW IDE portable. It scans your system, you install software, it scans again, and then sets up a sandbox with the difference in files that can run on a similar OS without needing to install anything. It mostly worked but had issues. If the OS is supposed to be there too, then maybe run some kind of Windows PE environment? Or use a VM maybe inside Windows PE or even inside of Linux? Lots of options, all are probably terrible.

Pretty hard to tell. I mean the game came out in 2001, so development was probably 1999 or 2000. The UI could be Window 98, or Windows 2000, and it could be LabVIEW 5 or 6. But honestly it could be anything.

Being able to combine your data processing, and GUI processing into a single loop is sometimes useful to reduce complexity. However, plenty of LabVIEW developers intentionally keep those two things separate. I've of the opinion that as long as you are very confident that the work being done is short, and won't keep the UI from locking up, then this approach is fine. Of course rarely can I predict how large an application might grow and how much of an impact this will have on the UX.

Awesome and congrats. I look forward to any kind of revelation or perspective changes you have as a result.

I do something close to Neil. My messaging structure uses the user events, and so in my event structure I have a long timeout of say 5000ms. In that timeout case I check to see if the user event is valid (not a number/reference). If it isn't valid then go clean up, I probably forgot to send a quit message or something shutdown improperly. I made an idea on the idea exchange to generate an event, when a reference gets destroyed over here which would make this a bit more graceful.

Oh man that looks like a painful thing to debug and isolate. And an even bigger pain to convince NI that there is an issue when someone in the support call will just have a goal of getting your code working. I haven't seen anything in 2020 like this yet. I have seen code that application builder says is broken, I go and run the VI it isn't broken, and then the build can continue. It is related in that it seems to be a compiler issue.

At what point in the video does a tab get removed? I just watched it and no tab is removed. I just downloaded the code and you are right that the Remove Tab doesn't work. Not sure why, but I probably just forgot to implement that.

Since this thread I've been using separate projects for each target. Debugging things aren't that difficult until it is some interaction between the two systems. I'll build my RTEXE, deploy it, then run my Windows VIs from the Host Only project. I might then realize the issue is on the RT side, so I then build the Windows EXE, close the Host Only project, open the RT Only project, open and run my main RT VI, then run my Windows EXE. Lots of building, and deploying when debugging. But since most issues I encounter are clearly one targets bug or the other it isn't too bad. I'll just open that project and run the source and debug the issue, while the other target runs its binary. It really seems like multiple targets in a project is one of those features that works in practice, and in the real world, falls short of expectations.

For personal use at home I use Acronis. I've only ever used it for whole OS backing up. It supports incremental backups, and has a pretty decent scheduler. So my home computers all backup to a network location once a month doing an incremental backup. This is much smaller but only tracks the differences from one backup to another. After 5 incremental backups it performs a full backup. After so many backups it deletes the old ones. There was a 3 pack of software that went on sale years ago which came with a mail in rebate basically making it free. It has a CD image that you can boot to restore the image from outside of the OS, or in most cases can select from within Windows the image to restore, then it reboots and restores it. Again this is more useful for OS back up, and probably not what you want but it likely does work with just a set of folders.

Not that I know of. You can email certification@ni.com for questions. They are pretty responsive.

Thanks for the video, definitely never seen that. I'd suspect it is an interaction with Parallels, like LabVIEW losing track of what you are under as you transition to other systems. No idea.

I don't follow you and may need a video to understand. Are you saying you can't drag an item from the palette onto the block diagram? I've never seen what it sounds like you are describing.

Just anecdotally I'd say my 2020 RT is more stable than 2017 and 2018. I do use a couple RT utility VIs, but I have separate projects for the Windows Only and the RT Only portion. In the past I had issues with opening things in the other context causing problems and long recompile times. With two separate projects there is no code under the other target.

Sorry about the snippet thing, LAVA sometimes strips out the meta data for it. In any case Crossrulz is right there is a function for this already.

Your Fig 1 still has a couple issues. First the memory issue. You build the array, then put it into a shift register that continues to build. You need to perform the array subset, and then put that into the shift register. Because adding elements at the start of an array were less efficient than at the end (not sure if LabVIEW improved) I often put elements at the end, then perform an Array Size, and if it is greater than some value, I use the Delete From Array, providing the index to delete as 0. Just a pointer that probably doesn't matter. The other issue with Figure 1 is you start with 1000 elements, then add elements one at a time. I suspect you either want to start with an empty array, or use the replace array subset but then things like pointers and shifting might be an issue. If you are just trying to keep it simple, I'd suggest this. Also if you are preallocating the array with a bunch of data, doing an Array Min/Max is going to use that preallocated data too which probably isn't what you want. If you go with a preallocated method you can still use array min max, but you will have to keep track of how full it is with real data, and then do array subset before Min/Max. This seems easier and honestly isn't that bad. Also you should be posting VI Snippets, these allow for posting pictures of your code as PNGs, that can then be dragged into the block diagram. Then others can get your code more easily.