INI problem

[Czentnar]

I've got a problem with the INI object (it works in Java quite well, anyway):
Once an ini file is loaded, it won't be refreshed in the next time.

For example:
- Start of frame:
Set INI file -> apppath$+"file.ini" //this file contains an item
- Always:
Set global value A to -> get INI item value

Now, if you change the item of the INI file during runtime, the global value will also be changed in the MMF2 editor. But it won't be changed in Java. You have to restart the frame or the application to have the effect.

[RickyRombo]

Hm... I don't know if I'm right about this, but it seems to me that you would have to reload the INI because the INI is loaded in the cache at start of frame (I think)

Something like that.

I'm probably wrong but try reloading the file after changing it at runtime :S

[James]

It's probably better behaviour if the INI values are cached - parsing the INI file again and again every time you read a value is pretty nasty.

[Czentnar]

Thanks RickyRombo and Jamie for your reply!
I will try to make an example because it isn't as simple as I explained.

There's one INI file and a frame with a Sub-Application in it.
The frame contains a String that is always changed to the item of the INI file.
The Sub-Application modifies the INI file - for example on key pressing.
(So there's an INI object in the parent frame and in the Sub-Application's frame as well).

When the Sub-Application changes the INI file, the parent frame should pass the changed value to the String. This will work in MMF2 but not in Java.

Thanks,

[Francois]

Yes, the INI is cached in Java. I cannot save a load the ini file each time you change something, this would waste a lot of processing time. The INI is saved after 10 seconds of inactivity after the last change. But it is never reloaded if you change it externally.
Putting a new action just for Java would not be really good.

[Czentnar]

That's good to know. I think I can solve the problem somehow, it isn't a big problem.
Thanks!

[RickyRombo]

:shocked:

For once I was right!! First time for everything...

[Czentnar]

Yes, the INI is cached in Java. I cannot save a load the ini file each time you change something, this would waste a lot of processing time. The INI is saved after 10 seconds of inactivity after the last change. But it is never reloaded if you change it externally.
Putting a new action just for Java would not be really good.

Back to this topic for a question:
Does the "Named Variable Object" behave in the same way? Or is it more flexible?
I haven't experienced with it yet, but if it caches the data during runtime and it can write and read external files as frequently as the user wants, then I will use it.
Thanks!

[Francois]

I would guess so. But I cant look at the source code today.

[Simon]

Francois is there any potential problem with writing to the INI file just before ending the application on a java mobile platform? Will this result in data not being saved due to the 10 second inactivity counter not being triggered as the application may have already closed?