Hi Tim,

Sorry to post 3 messages in such quick succession

Quick suggestion that, in my humble opinion, would make the whole programming experience much more bearable..

Would it be possible to stop Visual Micro re-writing the projects "Additional Include Directories" property. I spent a long time working out the interesting behavior between include files being automatically added to the .vsarduino.h (as well as function decelerations) and the "Additional Include Directories" continually being re-written.

I love the Arduino, but I really dislike how things are done behind the scenes to "make it easier" it seems.

I've been 'fighting' the problems with the include paths with the new 1.5.x arduino release and the new VisualMicro beta and these sort of problems could be easily avoided/worked around if we were actually allowed to make decisions about what Additional Include Directories we want.

Kind regards,
Dan

Hi Tim,

I'm a long time Visual Studio user (since Visual Studio 6) and a few weeks old Arduino user Its quite possible the added complication I'm experiencing is simply down to me not doing things the "Arduino" way.

There may be a simple solution but it seems some of my issues may be caused by personal libraries that themselves include additional libraries. It seems unless I explicitly include the additional dependent libraries in my ino they are never found.

For example, say I have a class 'B', and the header file for B includes class 'A'. I then want to use class 'B' in my ino. So I include B's header file and create an instance of B in setup(). This fails to compile because it cant find the header for file A. If I then explicitly include A in the ino as well, it compiles without issue.

Note: The above is from memory after a frustrating night, I will double check this after work tonight and note down the specifics - I may have just been having one of those moments and doing something ludicrous.

Quote:


I finally got my mind around exactly what was happening with the "Additional Include Directory" being re-written and the automatic includes in .vsarduino.h. I then manually copied some libraries into the ide\libraries directory and still had issues with file paths. At this stage I called it a night. I'm afraid I cant give you any specific information. As above Ill give it another whirl tonight and get specifics

Quote:


I did see this folder yes however I am not actually storing my project in my documents\arduino. I have a different file structure that fits in better with my other projects over the years.

Quote:


I'm not going to lie, I had seen this menu option but completely forgotten about it until I read these forums further this morning. I haven't been including libs in this manner.

Quote:
Sounds like a good addition

Regards,
Dan

Hi Dan,

These problems are because you do not understand how Arduino works.

You have too much experience of other development systems

In the Arduino world there is a very rigid set of rules that define where libraries can be located, sub folders are not supported.

A library folder must exists directly below ide\libraries\ or sketchBook\libraries. The library folder must have the same name as a .h that it contains and must not have sub folders other than an optional folder called "utility"

You must abide by these rules otherwise things will not work.

There is never a need to change the C++ project settings, the plugin handles everything and ensure that your project remains compatible with the Arduino IDE.

So your lib structure looks okay but int he sketch you must only include "Controller.h", do not specify the path. Arduino and Visual Micro will automatically discover the path and set everything up for you. Adding the path will break the compile and other stuff.

Use the "Project>Add Arduino Library" menu to add your #includes. This will allow you to see how things work. It will #include "Controller.h"

Hi Dan,

Many people want to maintain compatibility with the arduino ide allowing their open source code to be shared within the community.

New users need little knowledge to use an Arduino library, for example the i2c Wire library requires some knowledge to know which files to include.

Generally project development becomes much slower if one has to mess with library paths. 

Keeping things simple is at the heart of everything Arduino so I think the default behavior it correct and should be understood before the rules are broken. 

The main reason being that it is impossible to support the free product once the rules are broken and difficult for you to obtain support support elsewhere.

Having said all of that you are not the first person to want to do something less-arduino with an arduino so we will add this to the list as an optional feature for a future release.

Thanks for your support. Thanks very much for the support.