hooovahh

I also heard information like this. No one at NI specifically said this, but I got the impression that the extensibility will one day (hopefully) be at the point that a completely different IDE could be made replacing the existing one. If this is true then maybe this is what NI plans to do for the other platforms. I too am a bit surprised more importance wasn't put on cross platform up front, especially if his reasoning was for native looking UIs when NXG doesn't have a single system control. And yes I already gave this feedback to NI in person, and at the expo floor where there was a board to make UI suggestions.

Oh boy lots to take in (my own fault for not checking LAVA enough) Timelines are not published. If I had to guess (and I do cause NI didn't tell me) I'd say the current LabVIEW as we know it will be around for several more years. I wouldn't be surprised if the current LabVIEW still sees releases with new features and bug fixes through 2022, but again just a guess and NI them selves may not even know. There is a pane tool (at least on 2.0 beta I don't have 1.0) and you need to hold spacebar. Yes auto tool is the only option. I'm not thrilled with this but I understand and think I can get used to it. I was told by NI the 2.0 beta stuff can be discussed since it is in a public beta which doesn't require SSP or NDA so with that...it does have the HTTP functions in VIs and more importantly webVIs, but yes it is missing several other communications. Yes NI has a package manager and it seems to work pretty well so far with driver information and other larger installers. I'd assume you can have local repositories meaning offline installs. There is apparently some kind of command line interface for the package manager which will be useful for automated builds. As far as I know this is Windows only. Not sure if that will change in the future but certainly leveraging Windows UI components is going to make going to other OSs difficult. I did notice sluggishness but was told that might be a sign of VISA not installing properly, or thinking it is installed when it isn't. Hopefully a good install, with a several thousand VI project doesn't break things. This version of NXG probably isn't for the target audience of LAVA. We can use it and probably should if we want to give NI feedback, but don't try to migrate a huge project to it, it just isn't ready for most things yet. Still the Data Grid control is awesome (still needs work), WebVIs are awesome (in 2.0 beta but generates working HTML), and a vector based UI is greatly appreciated. Reception from people seems good. I think most get the message that current LabVIEW isn't dead, and that this is new but will be getting better.

You should be using an event structure. If you use an event structure you can register for mouse down, mouse up, etc, or on value change. Then the event will be triggered on that event instead of polling a property node which forces a thread swap to the UI. Post your code if you can.

Yeah for me the conditional disable says that OS is not a defined symbol and so it defaults to the default case which here is Linux. NI has lots of multiplatform code so you might want to look into how they do OS detection.

Works fine for me. I tried the set Top & Active in Windows 7 x64, LabVIEW 2016 32-bit. I had a wait which allowed me enough time to put other windows (non-LabVIEW ones) on top then waited and it was brought to the front most of all windows.

Yes it is out unofficially. And there are even a few blog posts talking about its new features. But there always is that ever so slight chance that NI will find a major issue before the release, have to release an update. In these cases people like you and I are risking getting a broken version of LabVIEW that was never intended to be in the hands of the public. NI would just delete it from their FTP and assume no one got the buggy version. Of course I'm not aware of that ever happening, and besides is will be officially released next week anyway so I say have at it. One thing that isn't quite clear to me is when we can start talking about these new features. I was part of the beta and have an NDA so I can't talk about it, but now it is out...but not officially. Anyway as far as I know there are only two features that get me excited. One is a major thing for reuse and will help make reuse code what we have wanted for years. The other isn't as big of a deal but might be useful for those that use DVRs often.

Well it's the 16th most kudo'ed idea on the RT section. (again highlighting the small amount of attention it gets)

I didn't see it linked here but I found your Idea Exchange, and luckily I already kudo'ed it. Too bad the RT Idea Exchange, along with several others, get very little attention from NI. A little while ago I was looking for a feature in RT and noticed an idea was posted for it so I kudo'ed it and talked to NI. Turns out NI already had implemented it internally and just had never released it. The feature could be documented and released 8 years ago but NI didn't know there was that much of a need for it. I pointed them to the Idea Exchange where at least one employee (close to RT support) seemed unaware that the idea was even posted, let alone that it was gaining traction.

So sorry if you've been monitoring this thread. The official one was posted here but Jeremy just forgot to update this one.

Native support? Even better. I knew those Variant functions were on the palette but for some reason didn't realize that was one of them.

Or even better there is an OpenG function that given an enum will return all the unique values of an enum, and it works just the same on a tab (since a tab uses an enum for its value). This function is under the LabVIEW Data package named Get Strings from Enum. Then there is no need for reference or property nodes.

Oh yeah lots of fun for sure, glad you got something working. I'd say you can thank me with a drink in Austin, but it sounds like you won't be making it.

I don't think that is related to the pre build, or setting build information. It likely has to do with the somewhat finicky application builder. I used to get build errors all the time when building on top of EXEs that were already built. I'm guessing you can build it locally or to a new empty directory. I've been using that pre build on some very large projects without any issue.

Sure we can talk at NI Week be sure and flag me down if this doesn't answer your questions. Over on the dark side I posted some overly complicated code that gets the job done for the most part. It is a Pre build VI that prompts the user for what you want the EXE build version to be. If you change it, then the build has to be aborted and restarted (NI limitation). http://forums.ni.com/t5/LabVIEW/Pre-Build-EXE-and-Installer-Set-Version/td-p/3149028 As for reading this from SVN, I have a VI that calls the C:\Program Files\TortoiseSVN\bin\SubWCRev.exe file. All you need to do is pass in a command line switch to the fill file path you want the rev of. Then what is returned from the command line is "Last committed at revision" which I pull out and put in the build. So my unpublished modification to the code posted is when it is ran it shows the last Major, Minor, and Fix version, and then fills in the Build with what is from SVN. Then the developer is prompted to change anything they want, but if they do change anything the build is aborted and has to be restarted (again NI limitation).

I think the more difficult part isn't debugging a Linux RT system, but instead debugging a Linux RT system and Veristand. For me debugging a Linux RT system is pretty easy, just plugin a monitor and look at the front panel of a VI that I push debug data to through a functional global or other methods. But with Veristand taking over a bit I imagine you don't have that level of control. I'd almost just suggest you log to a file the status and debug information, and then view that file via FTP other means on a remote computer. It does suck that the console isn't available, I didn't realize it wasn't an option since in MAX it still looks like it can be enabled there.

Yeah that's what I do. I read the build version from the file and display it in the about screen. I've also thought about pulling in the file creation date which if you are using an installer to install your software, should be the date the EXE was built, and not just the day you copied the file to the computer. I also set the build number with a pre-build which is the commit number in SVN. So then you have the major, minor, fix number, along with the commit for source code control, and the file creation date all in the about screen, and reports that are generated so you can look up what source code went with what software.

No I meant integrate, which is the area under the curve. So comparing the area under the curve for some set amount of X time on the first waveform to the same amount of time on the second waveform, and perform the integration then subtract the two and you'll get the difference between the two waveforms for that period of time. When that number is the minimum for a range of values that that is where the two should line up. I think the amount of X time can just steadily increase. So look at the first 0.01 of waveform 2 and the last 0.01 of waveform 1. Perform integration and see the difference, now the first 0.02 of waveform 2 and the last 0.02 of waveform 1 and do the same. Of course you can do smaller slices of time. Attached is the code that I think does this operation. It looks at the length of time the second waveform has, and performs the integration on the two waveforms 100 times, with ever increasing X length. Then it finds when the two waveforms had most similar integral on that period of X. This 100 is again arbitrary but can be easily increased if you want more precision, it will just take longer the more slices you are using. Detect Waveform Alignment 2.zip

You're beginning to sound like a customer. 10 Points is arbitrary, 0.5 tolerance as well I figured those could be adjusted as needed. I was just trying to come up with a slightly more robust solution while making some assumptions until more information came in. The non-even X would complicate things for sure. Having to perform more of an integration between times, and then look for when the subtracted integration between two lines at moving X is the minimum. But again I'd need more information about the types of overlap we are expecting. Can we always assume the second half of the first waveform is intended on overlap the second waveform? That would help simplify things a bit. Honestly most of my assumptions were based on the idea that these were two sets of data read from some analog device with hardware timing. Like an AI DAQ device, which is why I did it the way I did. The integration solution is probably a better way to go since it sounds like that is not true

I wasn't sure what version of LabVIEW you were using. The snippet says 2009, but it forced me to open it in 2016 for some reason. Anyway attached is my quick attempt. It will take the last N points (in my case 10) from the first plot, and then try to find a match with a tolerance (in my case 0.5) in the second waveform. If no match is found maybe you could look into adjusting the tolerance. I also wasn't sure if the second waveform would always continue the first, so maybe grabbing the middle points from the first waveform would be better if you know there is that much overlap. Detect Waveform Alignment.vi

Oh sure there are tons of ways to do this with 3rd party tools. My favorite happens to be one I helped develop posted here. With it I have been able to run a VI on a remote system which generates an HTML5 webpage, which I can view using chrome on another desktop, or my phone, or firefox running on an embedded Linux RT target. It has several limitations, like all clients connected will see the same UI but it is all open source and could be updated to your needs. Here are a list of other options, most of which I can't speak to the feature set of. As far as I know all of the official ways to do this (other than the new hottness teased at the last NI Week) all require some part of the run time engine to be installed.

Interesting program, but is everything hard coded in terms of the word used? Eventually I'd suggest allowing to just update a single string with a new value and have the program just work. Your question isn't quite clear but keeping track of the number of wrong answers seems like something you are going to have to keep track of with a shift register or feedback node, incrementing with each wrong answer. Then you can build your path with a format into string so that you will select 2.jpg for two wrong answers. You could also embed the N images into a single Picture Ring control, then pick the image based on the number of incorrect answers.

I've heard of people getting that kind of speed but I've never used it on any device. I found a couple of articles you probably already found talking about high speed serial stuff. http://www.ni.com/white-paper/52915/en/ http://digital.ni.com/public.nsf/allkb/D37754FFA24F7C3F86256706005B9BE7 I'm not aware of any special work that needs to be done to achieve a fast baud rate.

Bummer. Well still most of the icons look alright when small but is definitely noticeable.

FYI I made a separate post over here talking about my process of taking SVGs and making nice looking scaling icons using them, and I demonstrate it using your Dark and Light controls as templates.

There is still no way through scripting to replace the decals on buttons to use a different image. But using some known LabVIEW calls we can extract the image and replace it, then save it with a new file name. This has been done several times replacing the PNG image data in the CTL file. The problem I have with this is PNG images don't scale well. If I have a PNG that is 16x16 pixels on a small button, and I happen to want to make this button for a larger touch screen UI, I can but the image will look poor. LabVIEW does support some vector images mainly the EMF and WMF file formats. So using an external program Inkscape, I wrote some code that will take an SVG file (which is vector based) convert it to an EMF, and replace the decals of buttons, as well as give the CTL a PNG icon, label, and boolean text. I recently re-discovered a website that has all kinds of useful flat icons, and makes them available as SVGs. So all that is needed is to download Inkscape, download an SVG, and run a VI that I've attached. In the zip is some Example Controls I've generated using the SVGs from the Essential Collection which make controls based on 6 different templates. The JKI Flat Dark/Light, the Flatline Dark/Light, and the System Vertical and Horizontal controls. The main VI is in Replace Button Decals\Create Control from SVG.vi. I could see this being used on a repository of SVGs at some central location like a network drive, and then call something like Tools>>Generate Controls which shows a database of icons, and control types, and then generates them, rather than generating tons of controls that might never be used. Oh and I did find this pretty handy program that allows for viewing SVG images in Windows Explorer. It really helps to be able to see the icons and organize them before generating controls. Vector SVG Controls.zip