LabWindows/CVI
Is there a list of deprecated library functions?
Solved!
Well, Luis, what you say is true almost all the times but not always. I can remember when (I suppose passing from CVI5 to 6 or from 6 to 7, I don't remember exactly) InStandaloneExecutable () function was obsoleted and BeingDebuggedByCVI () was introduced: in this case the old function lost all functionality, always returning 1 ("running the executable"), with the additional problems that the new function reversed return value significance (1 meaning "running in the IDE") 
It's true that only a few of such changes have been introduced during years, but I second the opinion that a little list of obsoleted functions would improve the quality of new releases documentation.
Just my 2c 
Hi, Roberto.
Let me start by saying that what you're saying, in general, is true. There are (rare) instances in which a function does cease to work. A good example is the CVI automation function GenWinHelpFileFromFPFile. However, I'd quibble with your example. I wouldn't say that IsStandaloneExecutable lost all functionality. It's just that with CVI 5.5 and later, every program started running as a standalone executable, so the function always returns 1. But I realize that this is somewhat a matter of interpretation so I'm sort of splitting hairs.
You raise a good point. When something really is deprecated we do add something in the readme to that effect, but that doesn't always stand out very much. And when people skip versions they might not see all the transitions in each readme. We'll look into creating such a list.
Thanks,
Luis
@LuisG wrote:
(...) It's just that with CVI 5.5 and later, every program started running as a standalone executable, so the function always returns 1. But I realize that this is somewhat a matter of interpretation so I'm sort of splitting hairs.
Hi Luis,
I'm a little puzzled about the quoted sentence: every version of CVI I had been using permitted me to run the program in the IDE while debugging and compile them later to deploy to the customer, obtaining an executable with exactly the same functionality and little differences with its debug version. This is a powerful feature of CVI, that permits me to reduce the debug of compiled execution to very little tests.
This being the situation, I formerly used InStandaloneExecutable () and later BeingDebuggedByCVI () functions to discriminate wether the application was running in the IDE or not, mainly to make some controls / indicators visible to permit me to examine the values of some internal parameter without need to break the application and look into the variables.
This is my goal while using these functions and in this respect changing the function used and reversing the meaning of the return value forced me to a complete revision of the source code in order to port old applications to the new CVI versions. Not a complicated task, I know, just a little puzzling.
Maybe I'm splitting hairs too and probably we are now running out of this topic: I just wanted to know what do you mean when you say"every program started running as a standalone executable".
