issue with subapplication and ini?

[Popcorn]

I remember a long time ago I read in the forums that someone mentioned to never use subapps and inis in the same frame because it doesn't work on iOS. This is probably more than a year ago and I had pretty much forgot about that. But now I am using subapplication and inis in the same frame, and the ini wouldn't work. The ini does work however in the frame that does not use subapplication. Is this really an issue? And if it has been an issue for one year, shouldn't it have been fixed allready? It sounds like a really messed up bug. It makes no logical sence that this shouldn't work.

I understand it might be just a coincidence and something else is making the ini not work for me on those frames, but that's what sounds most likely to me right now.

It is not the end of the world for me as I can just change the subapp with something else, but it would be nice to have this solved if it in fact is that which is the problem.

[AyreGuitar]

So the ini is being loaded by the frame that also has a sub-app (not in the sub-app itself)?
Perhaps if someone uploaded a simple example file to show the problem?
I've never used Ini, I use List files and arrays and haven't come across such a problem.

[Popcorn]

Yes, the ini is in the frame that is using a subapp. The subapp is using a frame from the same app, maybe that has something to do with it also.

[Anders]

It is somewhat a difficult tradeoff. We only save the INI file to disk when needed.
This causes problems if you expect the changes made in the INI object to have immediate effect because you need to read it somewhere else.

Reloading the entire INI file every time a value is read + re-saving the entire INI every time a single value is updated is just too battery consuming and slow to be useful on a mobile device.