I am having a problem where a function in a file added to the project as a new INO file will not resolve when linked, even though I have identified it in the project (see attached file).  When I looked at the CPP file, the declaration is not included, nor the source.  Yet it's in the build list as _aThermistor.ino.

I have seen other posts which mention some issues on prioritization of including source files before compilation, which is why I used _ as a file prefix.  I can drop the function in an existing file and it resolves just fine.  I've also tried to rename the INO but no luck.

Any ideas?  I can add the function to existing files but they are getting pretty big and cumbersome.   

Thanks,
Rich

Actually I solved it another way (restart didn't help).  Turns out when you use the "Add new INO file" to the project, it does add it but sets the "exclude from build" flag to undefined "no entry"  Therefore, as far as VM is concerned, there is nothing to add into the CPP file before compilation - it doesn't exist.

This also explains why adding the function definition manually in the main INO file didn't matter - there was no code which resolved to the declaration.

This is a bug/feature that i think should be changed.    I only stumbled on this after much work, to overcome something i think is intuitive.  If I add an INO to a project, it seems natural it would be included in the build?????

Rich