.uir and .h file naming conventions

[ablade]

I have a project workspace where I have moved the .uir and associated .h files into other directories from their creation directory and also changed the case of their names.
Now, of course, when I make changes to the .uir by adding panels, menus and the like these changes are not reflected in the corresponding .h file.
Is there a way I can link the .h include file to a .uir so that the changes are reflected ? Does CVI force the naming convention of XXXX.prj, XXXX.cws, XXXX.uir and XXXX.h all in the same project directory to enable the automatic updating of the .h file ?

[Dany27]

Hello,

CVI only force the naming convention between the XXXX.uir and the XXXX.h associated.

Concerning, the .h file, I think the best way to deal with is just to do nothing.
Just move or modify the name of your .uir file and CVI will create automaticaly the .h associated with the same name. You don't even have to include it in your project.

I hope I answer your question.

Yop!
DanY

[Comadreja]

Hi,
I'm having kind of the same problem.

I'm re-arranging my working directory to have \SRC, \H, and \BIN directories, so I can just copy away my \BIN directory and have a full working app. I had to create a new project after re-arranging all, and then added all the files again. My problem comes when sepparating my file.uir from its associated file.h

I need to put the file.uir inside the \BIN directory so that the file.exe can execute outside my project, but I don't want to have the file.h in that \BIN drectory (I want it to stay in \H directory). I haven't found a way to associate one file.uir with a file.h in another directory, just adding them both to the proyect doesn't seem to work, as when I save the project it creates a new file.h in the \BIN directory.

Any help on the matter would be much appreciated.

Thanks,
Daniel

[jr_2005]

If you choose the target build option of embedding the uir file into the exe one, you don't need to treat the uir as needing to be in the BIN directory any more - just regard it as just another source file and leave it with the h and c files in SRC.

JR