How to structure the main LabWindows/CVI routine to break into logical files

[Sandia_Mike]

When developing a LabWindows/CVI application with lots of options on the UIR, I get really long main routine files.  But if I try to break up the main file into additional files, maybe with their associated subroutine calls, I get errors linking the CVICALLBACK panel handle.

What's the trick to breaking up the main file as I've described?  Or are there better ways to group routines for clarity and maintenance ease?

Thanks!

[RobertoBozzolo]

There is normally no problem in splitting functions into several fies in CVI, provided all source files are ancluded in the project and the appropriate include files are added to all of them.

One practical approach is to generate a small project (a panel with one or two buttons) and see which files are automatically included by the IDE: those are the core files that are to be added to all source files in the project.

While adding new functions to the code, the IDE will prompt you to add the nencessary include files when needed (at least for functions in built-in CVI libraries).