King of Shreds and Patches Errors

[GoogleCodeExporter]

I started playing the if game, King of Shreds and Patches by Jimmy Maher a 
couple of days ago.
  Some commands that are common in other games do not work correctly. These include hint, help, about, and so on.  When one of these is typed, it brings up that screen, but if you click on an option in that menu, the whole Frotz app crashes.  This also happens between chapters of the game. Also, typing 'inventory' does show what you are carrying, but it takes about a minute to do so, where other commands work almost instantaneously.

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.)
iPod Touch 4th gen

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

Original issue reported on code.google.com by CampJack...@gmail.com on 30 Jul 2014 at 12:50

[GoogleCodeExporter]

The other issues are dups for which I already have fixes in the upcoming 
version, but the delay showing inventory  seems to still occur.  Odd.

Original comment by spath...@gmail.com on 30 Jul 2014 at 2:35

[GoogleCodeExporter]

The inventory slowness appears to occur in other interpreters as well (tried 
Zoom and Spatterlight), so it looks like the bug is specific to this game and 
not an issue in Frotz.
The delay is about 2 seconds in an iPad Air; I don't know if it gets slower the 
longer you play, or if an iPod Touch 4th gen is that much slower.  The delay on 
a Mac Book Pro (2012) running Zoom is about half a second.
Interestingly, typing "i.i.i.i.i" delays about 5 times longer before displaying 
ANY output, then displays the 5 inventory lists at once (on all interpreters).
I'll profile it and see if I spot anything, but it's unlikely I'll be able to 
'fix' this in Frotz since it's something the game is explicitly doing.

Original comment by spath...@gmail.com on 30 Jul 2014 at 6:40

[GoogleCodeExporter]

Profiling shows entire time during running inventory command spent in the git 
interpreter, which is already a highly optimized state machine.  I doubt I 
could shave more than a couple percent off run-time.

Closing this issue as dup since the rest of it is already fixed/in-work.

Original comment by spath...@gmail.com on 5 Aug 2014 at 7:36

• Changed state: Duplicate