Glulx games which access supplemental files do not correctly autosave/restore the glk filerefs

[GoogleCodeExporter]

Glulx games which access supplemental files do not correctly autosave/restore 
the glk filerefs, causing spurious errors when those files are access after an 
autorestore.
For example, Alabaster has 'alabastersettings' and 'alabasterconc' files.  
These aren't crucial and the game is still playable, but it's supposed to 
remember what endings you've seen between restarts, and it doesn't.

What version of Frotz are you using?
1.6

What device model are you using (e.g., iPhone 5, iPhone 3GS, iPad 4, iPod
Touch 4th gen.)
All

What version of iOS?  6.1, 7.0, etc.)
7.0

Please provide any additional information below.

Original issue reported on code.google.com by spath...@gmail.com on 11 Aug 2014 at 3:00

[GoogleCodeExporter]

That's funny, I absolutely can't replicate that, and I've tried pretty hard 
just now. Well done on catching it.

Original comment by ilprimoc...@gmail.com on 11 Aug 2014 at 3:00

[GoogleCodeExporter]

Try this:

- Start a new game of Alabaster, get to first real prompt.
- Type 'look' or any other command.  Press home button to cause autosave.
-  Kill iFrotz with double tap home button and swipe up, so that when it 
relaunches it uses the autosave instead of just resuming the app via OS support.
- Relaunch Frotz
- Type "burn her"
- Type "again"

This will end the game, and should print a couple error messages in brackets 
about being unable to open a file, although the other game end text prints 
normally.
The 'endings' option at the restart/restore prompt will only print the ending 
you just encountered, when it's supposed to keep track of all endings you've 
played through, even in other sessions.

Original comment by spath...@gmail.com on 11 Aug 2014 at 3:13

[GoogleCodeExporter]

I get the error messages, but I still see all the endings I had previously plus 
this new one. Ah well, well spotted nonetheless.

Original comment by ilprimoc...@gmail.com on 12 Aug 2014 at 12:35

[GoogleCodeExporter]

Original comment by spath...@gmail.com on 14 Aug 2014 at 7:48

• Changed state: Fixed-Pending

[GoogleCodeExporter]

Fixed in release 1.7, now available (as soon as App Store servers update).

Original comment by spath...@gmail.com on 22 Aug 2014 at 4:21

• Changed state: Fixed