labwindows recompiles files when I switch from the development environment to another application

[Anna_K.]

Hello,

Thanks for your response. Let's try setting the path for the log file to your Documents folder instead in case there are permission restrictions in the C drive. 

After that, reopen CVI. 

I would also be curious to see what happens if the file is moved to your local drive. If you get a chance to try that afterwards, let us know the behavior. 

Have a great day!

[Test_Engxx]

I changed the file path, and restarted.  I do have a log file created now.  The previous post was my attempt to paste the log file to my reply.  (Maybe it was too long?  IE displayed an error about a script running slowly.)  Anyway, I will try again by attaching the log file.  I closed labwindows and deleted the log file to start from a 'clean' point.  Timestamp 11:09:46.531 is after labwindows reopened and I loaded the project.  The rest of the file was created when I switched applications and returned to CVI.  My .c file recompiled.

I have not tried copying the .c files to my local drive yet.  I am trying to avoid this because of how our projects are structured.  We use a global sandbox on a network drive for most of our test software.  (I am willing to try, if the log file doesn't help!!)

[Anna_K.]

Thanks so much, we are looking into it now.

Also, is it possible that other engineers are accessing the file while you are? Or are items in the shared drive refreshed and resaved periodically? I recall that you mentioned that the windows timestamp does not change, so that may not be the case. 

Thanks, 

Anna K.

[Test_Engxx]

I am the only one who would be accessing the files in this particular project.  I would not expect anything to be 'touching' these files on the network.  I am starting to wonder if this is some sort of interaction with 'mcaffee?' or some other network service.  

I don't know if this is related, but I will mention it anyway.  I have another project, which has several instruments loaded in the project.  When you open the project, labwindows shows a status box that seems to indicate that .obj files are being loaded for all of the instruments.  If I delete the cvibuild directory, and then reopen that project, I see a status box that resembles the 'compile' popup that I am trying to figure out.  After the cvibuild directory is recreated, the project will only show the 'loading .obj' box when reopened.  In this particular project, and this is from memory so don't quote me, I believe that one or two of the instruments show the same behaviour as the driver I am working on.  I.E. Intermittent, seemingly random, popups suggest that labwindows is recompiling their .c file.  One of these files, if I recall, has a compiler warning message issued.  

I believe that the only files I see this 'recompile' issue with are instrument drivers.  It also appears that labwindows handles files that are loaded as 'instruments' differently. (They exhibit build or load popups when the project is opened.)  Is there something that would trigger labwindows to 'reload' instruments? 

[Anna_K.]

Hello Thank you for your response, our R&D department has taken a look at the log file and we have some follow up questions for you that can better diagnose the situation:

1. Have you noticed that you have to have Interactive Execution window open for the problem to occur?

2. Is the file that recompiles always the source code of the Function Panel in your project?

3. Could you post a screen shot of the Instrument Driver Information window: Right click your instrument, select Edit Instrument, then click the Show Info button.

4. Have you noticed that the file that recompiles is always open for edit in CVI?

5. Have you seen the "Update Window from disk" dialog?

6. If you get a chance to move to the file/project to your local machine, that may give us more useful information. 

One last question, a member of our R&D department would like to work with your directly on this issue, may I ask your permission to retreive your contact information from the Forums administrator in order to email you? 

Again, we really appreciate your help and patience, some issues only become evident post-release and with your assistance we can work towards continually improving our product!

Cheers, 

Anna K.

[Test_Engxx]

1)  No, I do not have to have the interactive window open.

2)  Yes, the file that recompiles is the .c for the instrument driver.

3)  I don't quite understand the steps to view the instrument driver information window.  I tried right clicking on the .fp in the project window and selecting edit.  This simply opened the .fp file.  I tried right clicking on the .fp panel and it gives me the option to find, expand, etc.  Right clicking on the .c file showed a number of items, but none that appear to bring up an information window.  Could you clarify this?

4)  I believe that the file in question is always open for editing when this occurs. 

5)  'update window from disk'  I see this window if I edit a file I have open at my desk out at a test station and return.  I do not see this window during the issue being discussed here.

6)  I did move this project to my c drive, and the issue appears to go away. (This issue is somewhat hard to quantify.  My method to duplicate the issue is simply to toggle back and forth between CVI and IE.  It varies how many times I have to do this before I see the 'compile' popup message.  It also appears to change in frequency from day to day.  (Network latency playing a role????)  My original complaint was that when cvi recompiled the .c file my interactive declarations would no longer be defined.  I saw instances yesterday where the 'compile' box popped up but my interactive session was not affected.  That seems to be just as puzzling as to why cvi wanted to recompile the file.)

Yes, you may retrieve my contact information.

I will be out of the office Thursday and Friday, so I may not reply to any new posts until next week. 

Thanks for looking into this.  I'm still afraid it will come back to something to do with our network/mcaffee, but maybe you will be able to pinpoint it.  It still seems to be odd that it only appears to be instrument drivers that are affected.

[Anna_K.]

Hello Again,

Here is a screen shot of where to get that info. You'll have to right click the instrument from the Instruments tree rather than inside the project. I will let R&D know that they can contact you. Thanks

[Test_Engxx]

Here is the screen capture requested.