We've discussed the disadvantages of making all of the files ino files before. The biggest loss is you give up incremental compiles. For me, compiling 210K of program code dozens of times each day, the time savings are substantial. At one time, you also lost type checking with multiple ino files, but I'm not sure that's still true with the latest release of the IDE. Finally, for someone who is not familiar with the code, making the file with setup() and loop() the only ino file makes it easy to locate the code's starting point.
Jack, W8TEE
On Wednesday, December 19, 2018, 6:32:19 PM EST, Jeff Davis via Groups.Io <ve3coj@...> wrote:
Hi Gary... well you hit the nail on the head. I put all the ino's one after the other and it compiled ok. However, the Bitx goes into cw mode and sends code?
I dropped each ino in the editor? one after the other as listed starting from the top of the list... Is there any particular order?
I'm going to try the newer code with the CAT and I read the cw is improved......
