smithd

WPF is 14 years old, maybe not so 'whiz-bang'

ah, so thats how you are supposed to actually use ppls. is there any way to do this outside of vi.lib (ie a project directory)? the way I've done this so far is to have a separate project for each target -- the ppl seems to load first before any callers, so it kinda-sorta relinks itself (doesn't ever seem happy about doing so, but it works as long as the ppl-calling-code isn't loaded in two contexts simultaneously)

i find gitextensions to be my favorite. it asks you a lot of questions and is fairly 'low level'...which is to say it doesnt do much fancy past displaying command line output. it also exposes all of the little options like force pushing (to override history on a server) or amending commits, both as pretty clear options on the appropriate dialog. https://gitextensions.github.io/

oh trust me i've done that on machines which might be offline or I just dont feel like installing VIPM for this one package. Its generally just two locations (vilib and maybe a palette file) so its pretty easy.

the run on launch thing was just an awful idea. it makes me want to install packages with 7zip. On my machine 2020 hasn't fixed the file association issue -- any computer i use which has had 2019 and now 2020 loses its .vip file association for some reason. thanks to michael for giving us all an out on this.

could be valuable on rt if enforced. have to do this yourself with byte arrays and replace subset.

For those of you not using any of their remote systems (rt pxi, crio, or slsc): silverlight is still alive and well technically extant in the WIF. you have to use internet explorer because no other browser supports the silverlight plugin, but thats still better in many cases than trying to find a remote system in MAX.

A better way of looking at it might be that a variant is a specific data type. so if we assume c++ has some map<keyType, valueType> under the hood, the new labview map type exposes this directly and lets keyType and valueType be any labview type. the variant attribute system was specifically map<string, variant>. The api added some sugar on top so that if you specified a type, it performed variantToData(map.read(myStringKey), myDataType)...but it was still a map<string, variant>. If the content of your variant is a big array, this could potentially cause performance issues because of that variantToData. Vs 2019 where your map type might be map<string, lvArrayHandle> which doesnt need any of the weird memory allocation that happens if you call variantToData(myArrayInsideOfAVariant, dblArrayType). I dont know if this is precisely accurate, but thats what my general understanding was.

Stopped using it from labview, mostly do my database interactions in python currently. Actually, I use python to generate a data structure which I then json over to labview using your jsontext

I totally forgot about that, but I remember feeling the same way about...version 2? I figured since it used microsoft's ui stuff it would have some of the same features like automatic layouts at the minimum, and was disappointed. I know they've since worked on dynamic control instantiation, which is good, but if we're still stuck with finding window bounds and putting the top left corner of a control in right spot, whats even the point? Has anything like that crept into the more recent versions?

I think you're thinking of MAX Sliding scale the project tree is not the worst thing.

VSCode+gitlens has really nice git integration for text, if you don't have access (or dont want) full visual studio. I've been trying and trying to get away from sourcetree -- I've tried gitahead and git extensions. I like Git extensions best so far -- is not friendly, but it does a good job of exposing all the little random git things whereas a lot of tools (rightfully) try to make git look like its easy. I do want to try kraken now. Edit: do you know what gitkraken's license rules are? I thought the old rules were that its only free for open source, but I can't actually find any license terms. It says you can only access "public" repos, but when I just installed it I could use it just fine with a local-to-my-computer repo. So I'm confused.

But just think about how fast you can get to your first measurement!!

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019ZhbSAE&l=en-US https://sine.ni.com/nips/cds/view/p/lang/en/nid/209022 All these do is call lvcompare, which you rightly described as not enough. I've not heard any rumor of the current version of labview ever supporting better tooling.

yeah i mean i still can't get nxg to open on my machine without crashing, so I think we have a ways to go before it reaches the current 2019 standard of crashing only randomly in the middle of your work (real answer for me is that I use real-time, so 'next release' it might provide what I need but we shall see)