I have similar problems. My workaround at the moment is to add a comment at the start of the .ino.I use ESP8266, Uno, Etherten, Maple and others, so have started putting things like:/* * #! Board is generic ESP * DW, 20151031 */(the '#!' is based on Linux shell scripts using '#! /bin/bash')I posted to this Suggestions topic and have had no response either.Dave
I remember this topic from before:https://github.com/arduino/Arduino/issues/3228And here is another approach, a little different:https://github.com/arduino/Arduino/issues/1482
I suspect coding something like that would be difficult. If it is easy, somebody could take this one step further by actually coding the changes and submitting a pull request in github and that may get incorporated faster than a suggestion.
Even the com port is part of the project settings, so when I have two codes on two UNOs I can load to one, unplug it, and load to the other without having to remember to go change the com port.
it would be nice if the board, port and any other settings were loaded with each project
For the record: I disagree, and think that it is an important feature of Arduino that the same sketch can easily be run on different boards with different CPUs/etc. I *often* want a sketch to run on the board I currently have plugged in, and NOT the last board I compiled it for.
You can solve this problem by using a batchfile to open .ino files using the IDE commandline options you can store the preferences.txt in the sketch folder, so ALL settings are per-sketch.
Syntax?The problem with something simple...// BOARD = Arduino Uno...is that the developer may inadvertently create an action when they really meant to just document.
Would "extending" the Doxygen syntax be a good idea? Does anyone use Doxygen to document their projects?
If the ino includes any settings, should those settings track the actual IDE settings? If I change the board is the sketch automatically updated?
Should the syntax include a tracking option?