MikaelH

Excellent work, you're the best.

Something like this

Hi Mike, One question, The CellClicked Event gives me the Row and Column index, but after sorting the data, how do I get the Data of the cell? The DataGridView:Get DataArray.vi, gets me the unsorted order, so Unless I track the sorting my self I'm not sure how to get an sorted grid's cell value based on the CellClicked event. I'm sure there must be a way to do this.

Simple solution LED_Characters.vi

Do you open references to Reentrant VIs and not closing the reference?

I always start by changing the GDI Object limit to 65535, but that just solves your issue for few more days. https://msdn.microsoft.com/en-us/library/windows/desktop/ms724291(v=vs.85).aspx Does this happen in exe file version as well?

I've had these issues. This is not a License Issue, it's a windows permission problem. LV was installed by user X (so the LV files is owned by that use). Now when user Y logs in he/she won't be able to open any files belonging to user X. I've had this issue on some PCs, you can try right clicking on the e.g. LV20XX folders and re-set the user permissions on it and all it's sub folders. Properties->Security->>Add Everyone Full Control. When I get issues like this I normally asks IT to fix it.

You are right the NI-motion driver is not working in 64 bit, which is a really bad thing. But we use the NI motion drivers very successfully on from LV 64 bit....so how do we do that? We create a LV32 bit server application, that our LC64 bit application starts (if it's not already running). We then connect and send instructions over localhost-TCIP/IP, to the 32 bit written LV server application. We use this architecture for several driver components where e.g. the vendor only supplies a 32 bit dll version. Since we're using a GOOP based HAL inheritance structure the driver layer solves all our problems. I hope you don't give up yet on the 64 bit solution, since it will solve a lot of your problems.

I hope you are running LV 64bit to start with, we only run 64 bit here, so we hardly get any out of memory issues. The easiest way it to stop disposing/destroying the image and see if that helps. If you create a "new" image with the same name, you'll just get the same reference. A pool is one way to go as well, but you need a acquire and release images out and into the pool, so if the pool is empty the next user have to wait for his turn.

I would use for loops in your examples. And if you do, it's kind of impressive that you can run the loop with Parallelism activated, but them suddenly it takes 3 times longer time.

The only time I inherit a concrete class, is when I have a Class Called e.g. Instrument123, that has many methods and been verified and work perfectly. Then a new model comes out "Instrument123+", that just needs tweaking in one method or so, to get the same behavior as the old instrument. I guess I do this because I'm lazy, but that's when I do it.

The INI token "ModernBD=True", only changes the wire color for (what I can see) the Blue Numeric into: Instead of the old Blue:

Thanks for the info

I've just started to use LV2016, and one thing I noticed is that the built-in function Icon's inner color isn't black any more when placed on the BD. It's black in the palette, but when placed it becomes gray. Some functions is still black, is this a new feature?

Just a tip, start off with a base class called: Instrument Then children for the different abstract types, and children to those for the specific ones. Add a FactoryCreateAllInstruments method in the Instrument Base class

I Agree that all those things are very easy to learn, but if the person knows about them, it tells me that they are curious enough to looks at our peoples solutions. So even if you have >10 years LV experiences but never heard about OpenG VIs, Custom Probes, VIPM or QD, that tells me that the person have probable not worked in a team, and been doing the same style of coding since the they started. They probably still thinks global variables are the best way of sending data between processes.

When I interview someone I check: If they are familiar with the OpenG libraries. How much they know about version control If they know what VIPM is If they know and have used: Queues, Dynamic Events, DVRs, libraries(*.lvlib) and classes (*.lvclass) types. Which (if any) LV-forums they visit regularly (it's important that the person is looking around to see how other people solves problems) Then of course I ask them about Quick Drop and QD Short Cuts I ask them about: Custom probes. If you know all these things I would hire you :-)

I would use a Picture control together with a plot, something like this. ExtraX-Scales.vi

What they should have done, is to convert the U32 to U64 inside the node, so it handles the date correctly, but maybe it's not that easy

Does anybody know why in some Point By Point functions there is a Type Cast from I32 to I32 in the code. E.g. Sort 1D Array PtByPt.vi Array Max & Min PtByPt.vi

I had to use QD "fts" (Format To String) and the format %<%Y-%m-%d>T to get it working.

Is it commonly knows that the Get date/Time String can't handle Time Stamps greater than 5PM the 6th of February 2040?!?!

Now I've installed the needed VIs: and I've tested it, it looks nice :-)

It looks I have to install: <userlib>:\_LAVACR\Scripting Tools\XNode Support\...

It probably won't work on Linux. :-(