Leaderboard

This window can be called by a CIN code, by using the function DbgPrintf("Value to debug : %d", value); Is is very useful to debug CIN functions. It is defined in the /LabVIEW folder/cintools/extcode.h

Could you use Lab Python? I wrote a small example here. [edit - fixed link to original discussion in the NI Forum]

It's a security issue. See this thread for more information:

If you are using FTP, transfer progress is buried inside the Internet Toolkit. If you want to be able to monitor progress, please consider voting for this Idea Exchange suggestion - Add progress functionality to Internet Toolkit FTP library.

Commonly this would require you breaking your transfer down into chunks. You can then easily time each chunk as you would benchmark any VI (check the example finder) and knowing the size get to the bytes/second This chunking is going to happen in the tpc stack anyway so don't think it would add much overhead. Not aware of a way to time it whilst in the TCP write function. Cheers, James (null)

Don't use any type definitions inside your class data. I'm not sure I'm following what your final implementation looks like. You're letting LabVIEW load the object with the binary read function and then fixing your index if it's bad? Is the index a scalar value that requires some logic to determine its value? I would probably use the class version number to determine what code to execute on the data to fix the index. At the end of the day, you still need to do some "fixing". When I've had to do this. I use a multi-stage sequential conversion routine. based on what version I'm reading. So if you have 3 versions of your file then you would do 1->2->3. Needing 2 conversion routines. I've stayed away from using the class versioning system for saving object data because I tend to use typedef clusters in my objects. Ya, I know, bad - bad Michael. I'm slowly trying to ween myself from this habit.