hooovahh

Thanks, added up through 2020. Even though it isn't actually released, lets just assume it does get released someday and that we won't need another reminder to update it until at least 2021 is out.

Permissions might prevent the reading of the file. If you do a Open File maybe even set to read only then read the file you might have better luck. Also calling a system exec and reading the standard output might work as well.

Neat idea editing the control itself. But that solution is only going to work if you don't mind having no control over the GIF and don't mind looping, and if you don't need to update the GIF at runtime based on an existing file. The demo I showed saved the GIF as a constant in the block diagram because it is faster, but I have some disabled diagram code that will instead read the GIF from a file. It then will play the first half of the GIF, then wait for the saving to finish (random number) then play the second half. Is there a site where simple animations like this can be used for free? Also back saved to 2016. 2016 Save Demo.zip

I get your point of the multi menu setting isn't very quick to change. That being said I sometimes mess around with conditional outputs, and with arrays I might be concatenating, or conditionally concatenating, or indexing, or last value, or conditionally last value. And I just think cycling through all 6 possible combinations would be more annoying than a couple right clicks.

You can call the non-NXG LabVIEW IDE what you'd like since NI just refers to it as "LabVIEW" but the designator I've seen most commonly used is Current Gen (CG). But maybe ODG would be better since, well some day it won't be current gen...unless NXG is always going to be coming next. Anyway I hate units too and have left them behind. I feel bad for those that do use them as it is an official real documented feature of LabVIEW, but just has too many places it doesn't work as expected. It's a feature I feel like the majority of NI and LabVIEW users have forgotten about.

Over the years I've been using a portable version of Gimp for ICO file editing. In Windows 10 I've found that having 256x256, 48x48, 32,32, and 16x16 work well. I mean you can have 128x128, 96x96, and any others but it becomes a support problem having to make all those for every application.

Over on reddit someone asked for suggestions on how to make a sliding UI like you might find on your phone. I thought it was a fun challenge so here is my very rough draft that could probably be turned into a QControl. And a video. At the moment you can only change the settings of booleans and of a selection like the days of the week I show. I planned on putting code for handling string and numeric value changes but probably spent too much time on this already. Android Sliding UI Demo.zip

I thought this was an interesting exercise so here is my attempt. OpenG has some image tools and one of them is the ability to open a GIF, but for some reason it crapped out and died with your GIF even after resaving it to something much smaller. I did find some other GIF API over on the dark side and instead used that. Attached is a zip, extract it and run Demo Saving Button. It will show the first image. Then when you click the image it cycles through the first half of the GIF and waits for the simulated save process to complete. Once it is complete it rotates through the second half of the images, and then after a few seconds returns back to the first. Parsing of the GIF takes time so I put in the GIF images as a constant, along with the code to parse the GIF. I also set the pane to be the color of the (0,0) pixel in the hopes it will blend in better. Honestly this could be turned into a QControl and be made very seemless. Demo Saving Button Gif.zip

Okay I edited the spec file to start with the following: [Package Name] Name=oglib_lvzip Version=4.2.0 Release=1 Display Name="OpenG LabVIEW ZIP Library" Then I zipped the source back up and renamed the zip to oglib_lvzip-4.2.0-1.ogp. I then installed the package and it didn't say "Upgrade" but instead said "Install". But after installing there was only one entry and the result was the upgrade was successful.

Thanks, good to know. I took your 4.1.0 release (maybe it was b2?) and edited it to make a package that was considered an upgrade. I thought the changes I made were to the displayed name and version. But now that I try to do the same with the 4.2 release in this thread I can't make it work. I keep copying more stuff from the existing spec to the new one and it isn't working...I'll keep playing around and let you know if I get anything conclusive.

As always, thank you very much for this continuation. Inflate/Deflate on Linux RT is important for a side project I have lately so this is awesome. I did notice that in VIPM if I open your package and already have the previous OpenG zip package installed, it doesn't do an upgrade but instead performs a new install. It appears that the internal name of the package, or versioning changed in a way that VIPM doesn't recognize it as a new version and will install it along side the last official release of OpenG which I think was 4.0. I was able to edit the OGP spec file and create a package that convinced VIPM that it was an upgrade. I was curious if this was intentional to distinguish it from the official releases. Oh it seems the old package name was "OpenG LabVIEW ZIP Library", while the new one is "OpenG ZIP Library", I think this combined with some version changing is what I needed to edit.

The VIM Array package is a dependency, and actually included in this VIPC release. It was just easier for me as a developer than trying to remove the dependency, and easier for you guys if everything is in one file.

I haven't tested everything in there on NI Linux RT but a few of them I have. The only thing that uses any thing questionable is the Circular buffer has a compression option where it zips the circular buffer before logging it to disk. I used the native LabVIEW zip API so I suspect it works on Linux RT...but I forgot to test it before posting it. Everything else is just pure G and I see no reason it wouldn't work.

View File Hooovahh's Tremendous TDMS Toolkit This toolkit combines a variety of TDMS functions and tools into a single package. The initial release has a variety of features: - Classes for Circular, Periodic, Size, and Time of Day TDMS generation with examples of using each - Reading and Writing Clusters into TDMS Channels - XLSX Conversion example - File operations for combining files, renaming, moving, and saving in memory to zip - Basic function for splitting TDMS file into segments (useful for corrupt files) - Reorder TDMS Channel with Demo There is plenty of room for improvements but I wanted to get this out there and gauge interests. The variety of classes for doing things, along with VIMs, and class adaptation makes for using them easier. If I get time I plan on making some blog posts explaining some of the benefits of TDMS, along with best practices. Here is a youtube video demonstration of some of the features of this toolkit. Submitter hooovahh Submitted 12/12/2019 Category *Uncertified* LabVIEW Version 2018 License Type BSD (Most common)

I also can redownload it, you likely need an account.

Now we are digressing a bit but I also have an old piece of marketing I like to show off inconspicuously. At NI Week the last few years NI has various buttons that say phrases for that years' theme. Usually people grab a handful of buttons and put them on the lanyard you wear with your badge on it. I won't go too over board but I'll grab a few and put them on, but mixed in with them is a LabVIEW 7 Express pin I was given years ago by someone that was at NI Week the year LabVIEW 7.0 Express was released. It is old enough that it is starting to rust on the back a bit but LabVIEW 7 (and 7.1) were my favorite versions for a long time so I wear them. Last year someone was looking at my various buttons and saw that and asked where they could get the retro NI Week pins and I had to explain where it came from.

I don't have anything to add other than I've seen this but not in any recent projects I've worked on. It always frustrated me when I'd drill into some VI that was taking forever and it would be some property node or Read/Write/Open that was supposed to have a small timeout.

One quick comment on the can opener thing. I might well be using the can opener incorrectly, and I'll try the horizontal way next time, but I think my habits came from an old wall mounted can opener I used at my grandparents for years which was vertical in design. Also I included an ad for it because the thought of giving a can opener as a perfect gift to the "queen of the kitchen" would probably not go over well.

In the Facade, set the background pane color to the transparent color value. This doesn't make the facade transparent when developing it, because...well it can't really. I believe when editing the VI the pane will appear black. But when the XControl is running in a new front panel, it will have a transparent pane color, meaning it will be the color of the front panel on that VI. The transparent color value is 0d16777216. https://forums.ni.com/t5/LabVIEW/Can-a-Color-Box-display-the-transparent-color-16777216/td-p/172288 Also is this documented somewhere or just tribal knowledge?

So when I was playing around with this I would map my build folder, to the www folder of my webserver, with a symbolic link. This way I would build and it would already be in my web server folder ready to be used. Here is a very loose set of steps I did to map a folder from a build to a place that the webserver uses. I don't know of what NI uses on the hosting side and I've always just used XAMP which is Apache. Windows has a built in server too that works well enough for basic stuff.

The "Check your internet" is a catch all error basically saying it couldn't install, and it must be because the internet is down right?...right? For me I got that error when I had a bad stick of ram in a computer, and it would uncompress a package, and then the CRC would fail. I'd restart the installer over and over until it worked but the computer had all kinds of other problems. The Offline installer including drivers and several other things is a bit crazy. I mean will the community edition also be 25+GB in size? I'd usually download the whole developer suite in the past anyway so it is on the order of the same size as that was. The Web install however was perfect. It would prompt you on what you wanted to download and then install offline using those things worked great, but no more. Sorry I'm not from the 2.x era LabVIEW and the idea of installing it in anything other than the default install location of "LabVIEW 20xx" seems crazy to me. I suggest embracing the change...from 2003. Package manager does decide where it goes and I saw several people complain that they couldn't even install LabVIEW to any place other than C:\ drive without editing the registry. When I go to a new version of LabVIEW I just leave the one that's already there. I mean I usually don't upgrade all projects at once and some maybe in the older version so I just install them side by side. I think the most I've had installed was probably 7 or 8. I guess what I'm saying is I've never uninstalled a version of LabVIEW, and I would expect problems if I did. I mean honestly it should work just fine, but I wouldn't expect it to.

It really depends on what you are trying to do so I get that. For me even just setting the VI file to read-only would be enough, but I ran into a few times when a mass compile would want to overwrite the VI despite it having separate compile code, but that was years ago. For me the purpose was that a developer would be drilling into the code and not realize they were in a reuse function and would start messing around with it and changing things that will now make the program behave differently on one developers machine, than the others. A gentle reminder to not mess with something was all we needed. But I get your points.

Not trying to derail the thread even more, but every time I hear that argument I say that is why you can lock a VI without passwording it. Which is what my Pre-Build action on building a package does. Need to edit it and do a test? Sure just unlock it. Drilling down into a VI and not realize it is part of the reuse library? You will when you see it is locked. But whatever. I still tell the quote from NI R&D saying off the record that the protection you get from password protecting a VI, is about the level of protection you get from tissue paper.