hooovahh

Correct me if I'm wrong but Genericity (is that a word now) makes the VIs on the fly and saves them to temporary file locations on disk. One for each instance needed to support the VI. Essentially making a new polymorphic instance every time one is needed. I have no clue how that would work in a built EXE because scripting isn't in the run-time engine. But now that I think about it when building an EXE it would probably just replace the generic subVI with the instance it created that was being used. If that is the case then again a built EXE using a VI that uses a Generic terminal, should be identical to a EXE built with just a normal subVI. But really I have no idea what the compiler would do, which is probably why NI just advises against using them at all.

Don't get your hopes but, I'm quite certain this functionality does not exist in this toolkit, but I too would love something like that. Our testers don't generally have lots of graphics horse power but if they do, off loading some of that to a GPU seems like a great idea.

Which is quite ironic since generics are most certainly not "Go" and NI has said multiple times that the development of Generics are a dead end for them. I can't remember who I heard this from but I thought I remember even hearing that NI plans on removing Generics from some future version of LabVIEW because they don't think it is a stable technology.

They are a secret that's why you can't use them...but seriously they help with custom control development. They are very incomplete but give some functionality that has been desired by the developers. The interface for getting these much desired features is quite lacking, which is probably why this isn't public yet. It can allow things like defining the behavior of a decal on a button, as the button changes size. By this I mean the decal can move as the button grows, or the decal can stretch. You can also define if the decal (or text) can be resized or moved independent of the control. Very neat stuff but yeah it can behave strangely if you enable some features at the same time which the interface doesn't restrict you from doing.

I went through Ctrl+Shift+D Ctrl+Shift+<another key> for all keys on the keyboard to see what other things come up. I never found the _ debug because I was expecting some kind of popup like the W and H return. EDIT: It looks like the wireframe drawing work on 2011 not sure about older.

Not quite. When the EXE is made there is no XNode, and there is no private method being used. The private method is only being used during edit time. If you interact with the XNode described it will call the private method, but once it has ran, that private method won't be found in your source. So it is a grey area for sure. The production code doesn't contain any private methods, but a tool used to generate a portion of the production code does.

I still couldn't get that to work, but I understand what you were trying to do. This ladies and gentlemen is another reason why code review does not replace unit test.

What limitations are you referring to? And how did you get around them? I have only used these devices (and the Arduino SPI) on very simple slow devices for getting voltage readings, so maybe my application didn't see the limit you did.

That is fascinating. So that explains this thread on glyphs in multiple columns. http://lavag.org/topic/7002-multiple-glyphs-columns/ I haven't played with it yet but some of these settings sound very useful. If you don't mind me asking how did you find this INI key? EDIT: BTW has anyone just tried SuperSecret<insert function or control>Stuff=True for every function imaginable? Or EnableSecret<insert function or control>=True Double Edit: Looks like this works on 2013 and newer.

Notice I didn't say to use regular expressions, I just said that it could be used.

Maybe you should it sounds like it would meet your needs. If you are unsure what the function can do open the context help.

So you want to print the source code to your application correct? Did you try File >> Print? Or File >> Print Window? If so what was wrong with doing that? You can also do it programatically using the Report Generation >> Easy Print VI Panel or Documentation

Yup that's what I said.

Many ways. How about getting the string subset on the first four characters and seeing if they equal SDFS or ASXP then getting the string subset of there for the appropriate length and offset for each. I'm sure regular expression could do it too. Post your VI you have tried and show what you couldn't get to work.

Wow I always wondered if I could use a series of DIO lines to make a SPI device. You haven't confirmed the fact that you can or can't yet but it is interesting. What is wrong with using a cheap USB to SPI device? NI does sell their USB-8451 which is a SPI device and works quite well. Of course a much cheaper option would be an Arduino Uno and the LIFA Toolkit which has a palette for doing SPI or I2C. I've used both of these for SPI communication and never had a problem.

Support, documentation, and examples are a few things I know you get without ever having used it. If I were experienced with CUDA (which is sounds like you are) you might not see enough value in it. Download a trial and try it out, and if you do please report back your honest opinion of the toolkit for others to see, I get the feeling few have ever used it.

FYI Crosspost

Yeah I actually took that and modified it to make this QD. https://decibel.ni.com/content/docs/DOC-31302 When using mine, adding the Shift modifier should do just like that function where it shows the file in explorer. Without the shift it does something completely different where it shows the currently opened VIs. I just thought it was a waste to not have some secondary function, especially when QD shortcuts are in high demand.

I have seen that issue many times all on 2012, or 2012 SP1. I believe they fixed that in 2013 not just 2014. I still have some programs made in 2012 and I dread making changes just because I know it will take several restarts of LabVIEW to get my EXE built again. Usually I say not to upgrade to a new version of LabVIEW mid project due to the unknown risk, but for me I think the risk is worth being able to make EXEs easier again.

Another neat trick is you can open an explorer window, and have a specific file in that folder selected using the /select switch when calling explorer from a command line. I tried this, this morning and it worked but for some reason the new windows were minimized. Probably another switch I'm missing.

If you asking how to read a file, it doesn't really matter what the file is, you can use the Read Binary File with an array of bytes. But the usefulness of this is very small. It still isn't clear why you need to load a hex file with LabVIEW.

Yeah it should be possible. But rather than trying to read the file into LabVIEW, can you just use the hex file in a commandline program to load your device? AVRDUDE has command line support so you can provide the file and interface and it uploads it. You can make this a batch file if you wanted which is probably easier than LabVIEW.

I don't want to go off topic...but you have 7 posts...been registered since 2005...and you are a premium member. Congratulations to you sir, and thank you for supporting this forum.

The typical disclaimer to be said is that using this INI key enables private functions of LabVIEW which NI does not officially support. Using any of these private functions means you are more or less on your own. Support for these functions is non-existent, documentation is non-existent, and these functions may change from version to version without mention in a change log.

Revive a 5 year old thread? Why not. Turns out there is a easier way to concatenate a 2D array of numerics horizontally using the matrix math build matrix function. There is a right click option for append columns, or append rows. http://forums.ni.com/t5/LabVIEW/Concatenate-2d-arrays/m-p/2959175#M853118