Hi Jules.
I’m developing a plugin (actually porting it from some old win32/vst code) from VST to JUCE because we want built OSX (AU, and RTAS if possible) versions.
This plugin has a bitmaps based GUI wich user could modify, and the old version just had the bitmaps (bmp) and data files along the dll, distributed like this:
Main library module (dll):
VstPluginsInstallPath/…/Company_Name/VASynth/VASynth.dll
Bitmap files:
VstPluginsInstallPath/…/Company_Name/VASynth/Skin/main.bmp
VstPluginsInstallPath/…/Company_Name/VASynth/Skin/knobs.bmp
Data files:
VstPluginsInstallPath/…/Company_Name/VASynth/Data/presets.dat
VstPluginsInstallPath/…/Company_Name/VASynth/Data/config.dat
The question is simple: looking at SystemStats members, it looks that I can get the main exe path, temp path, user directory path and application data path.
I know I should use the later (app data path) in order to store the data, but I would like to do the mostly unobstrubsive package for users, avoiding put data out of the folder where the main binary file is set.
Using Win32 is just a GetModulePath call iirc, but it could be possible to get the library pathin a “Juicy” way. and the most important question, there’s anythings in the AU version to be considered if I want to distribute the data in the same style.
If there’re problems I guess I’ll better have to use the app data path way.
What you recommend in any case?.
Thanks for your amazing library.
Regards,
Argu.