If it fits your use case, I would encourage you to embed the image in your project. Doing it this way allows you not to worry about file paths, as well as guarantees the image will be available at run time. Add the image to the Projucer project, and then within your code access it like this:
const auto gearImage = ImageCache::getFromMemory (BinaryData::settings_gear_black_png, BinaryData::settings_gear_black_pngSize);
This works. I tried it earlier but got no results because I used save_png_size instead of save_pngSize so thanks a lot! Images came out funny looking but I m sure I can work that out now they are appearing in the first place. How did you get that syntax? There aren’t any examples I could find of that.
I’ve been writing JUCE, and C++, code for so long, I couldn’t tell you exactly how I derive an exact usage. Docs, experimentation, other peoples code, this forum… all of these things help me gain a better understanding of finding best usage.