Hello!

I have some code to check if there's a config file and if there isn't, it will create one, simple stuff. I can then read from the file just fine, but when I try to set values and then save, the save fails.

Here's some of my code.
I first load the config file in the beginning of my code

// Outside of main()
ALLEGRO_CONFIG* config;
// Inside of main()
config = al_load_config_file("config.ini");
// This works just fine
value = al_get_config_value(config, "blah" "blah");
// But this doesn't :c
al_set_config_value(config, "blah", "blah", "blah");
// This returns false and the file isn't changed
al_save_config_file("config.ini", config);

Not sure what I'm doing wrong.
Thanks!

1.
No, it can create the file just fine.

2.
Tried compiling in debug mode. Where can I find allegro.log?

3.
Yes, and that also fails.

4.
Sorry that I was unclear. Meant that al_save_config_file failed. If I try to check the value before and after, the value changes.

5.
Running Allegro 5.2.1.1

I tried recompiling Allegro with WANT_RELEASE_LOGGING, but no log is being created.
I'll see what I can figure out...

Just to be clear, I'm trying to update an already created config file. A workaround could be to remove the file and create it again if it's needed...

EDIT: Tried removing the file and write it again like this and it removes the file, but doesn't write it again

ifstream fileCheck("config.ini");
if (fileCheck.good())
{
  fileCheck.close();
  remove("engine.ini");

  ALLEGRO_CONFIG* config = al_create_config();
  al_set_config_value(config, "Blah", "Bloh", "Bleh");
  al_set_config_value(config, "Blah", "Bleh", "Bloh");

  al_save_config_file("engine.ini", config);
}

Yes, I can create it just fine, just not modify it afterwards.
I'm using various other Allegro stuff for graphics etc. so I know it's working.
Dunno if PhysFS is messing stuff up though.

EDIT: Yup, after initializing PhysFS, you can't save config files, since PhysFS doesn't support writing to zip files. Not sure if bug or not though.

As an aside, I think 7-zip has an API that lets you write to archive files. If we wrote a file system driver for 7-zip, what you're trying to do could be done. And 7-zip supports MANY different formats.

That's why it's always best to try and provide a minimum, complete, verifiable example (MCVE like Stack Overflow likes to call it), so others can try to reproduce it and so we can see everything that's going on. I would never have guessed you were using PhysFS from what you showed us.

I wonder if we should provide a function al_set_physfs_file_interface_read_only. But then when you try and read your config file it still would try to read from the .zip - I guess it has to be the user's responsibility to set the file interface they want to use.