My testing with FMPA 13. You have to make a change on the layout to force the file to be saved which will cause the Formatting bar setting to be changed and saved, if a change is not made on the layout then it will revert back. Just changing the setting of the formatting bar does not force a file resave.
There are a few things that are only written to a file when one forces FM to save some data to that file. Some of them need to be saved locally.
I usually add some text into a field, let FM save that (clicking out of that field), undo the changes - abd then close the file. As schamblee mentioned, altering something in the layout also forces the 'save'
doesn't "Flush cache to disk" script step have a similar effect ?
My good friend tried changing and saving ... it did not help. I am not really sure about the final answer to this question. How is the documented behaviour?
This is a file-based issue (not app). For settings to be saved, the file has to be local. Is the file being served?
I suspected that this could be the case, as with content in global fields. You can set the content in a local-non-hosted file to a value and then host on server. Now this value is default for everybody who log on the file.
The sames goes for "global guides". Drag a guide on to a layout and make it global/shared (right click and set the property). If the file is hosted this will be lost when you disconnect and connect again.
It could be argued that some of this behaviour is not only not very well documented (global fields are, and that is absolutely OK). But the guides, the settings for layout and other behaviour should be stored, either locally for "you" or for the solution as such.
I will ask my good friend to try it on a local file (I could of course do this my self, but I am pretty satisfied with the default setting and with changing it on a day to day basis when I want it to be different).