Hi there,
A suggestion:
I broke down my code in many libraries, wonderful.
Then I created dozen more, for each library, since it is required to, I create a project file on its own folder. Fine, that is a good way to atomic test each library.
But when compiling to library it ask me the name of the library to be created. If this is eventual it is not a problem, but when you switch over many library I can make a mistake with the library name.
I would suggest to create in project attributes a key #libraryfilename or something like that, when assigned it does not ask for the library file name and compile using this name generating the file on the additional libraries folder as it is the default.
regards,
Eduardo Elias
A suggestion:
I broke down my code in many libraries, wonderful.
Then I created dozen more, for each library, since it is required to, I create a project file on its own folder. Fine, that is a good way to atomic test each library.
But when compiling to library it ask me the name of the library to be created. If this is eventual it is not a problem, but when you switch over many library I can make a mistake with the library name.
I would suggest to create in project attributes a key #libraryfilename or something like that, when assigned it does not ask for the library file name and compile using this name generating the file on the additional libraries folder as it is the default.
regards,
Eduardo Elias