Ya, I guess it doesn't matter. It's just nice for the c++ library to "own" an entire directory.  Then you should be able to just delete the dir and all the persistent state of the app is gone.  On iOS if no other things go in the docs dir, then we can simply use that. If iOS uses it for something else, then I think we should and a subdir.Sent from Mailbox

On Wed, May 21, 2014 at 9:33 AM, Piet Brauer <notifications@github.com>
wrote:

>> @@ -8,8 +8,10 @@ + (MX3Api *)sharedAPI {
>>      static dispatch_once_t once;
>>      dispatch_once(&once, ^{
>>          NSString *documentsFolder = [NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES) lastObject];
>> -        NSString *file = [documentsFolder stringByAppendingPathComponent:@"test_ldb"];
>> -        _sharedAPI = [[MX3Api alloc] initWithPath:file];
>> +        // give mx3 a root folder to work in
>> +        // todo, make sure that the path exists before passing it to mx3 c++
> Oh I'm not too familiar with Mac development. We probably use the applications library folder because of sandboxing.
> I will research it.
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/skabbes/mx3/pull/7/files#r12906437