Closed GoogleCodeExporter closed 9 years ago
I should note that I tested this in Anchorhead and also in an unreleased game
that I'm testing. I've played Anchorhead in this version of iFrotz on this
iPad but on previous versions of iOS before without any problems.
Original comment by phoesha@gmail.com
on 16 Mar 2011 at 1:16
This bug is caused by a change in iOS 4.3. I'll try to get a fix in Frotz out
soon.
In the meantime, you can avoid crashing by turning off Autocompletion in the
prefs.
Original comment by spath...@gmail.com
on 16 Mar 2011 at 1:23
[deleted comment]
Having a huge problem with Anchorhead in Frotz on Ipad/Iphone. I can't read
the news clippings or the library book. When it asks to hit the SPACE button,
I hit SPACE and it goes back to the main menu. Please help. Am I doing
something stupid or is there a bug? thanks
Original comment by chadgibb...@gmail.com
on 30 Jan 2012 at 2:27
One issue with some text adventures, including Anchorhead, is that they were
written with the idea that people were playing them on full computers with full
keyboards, including arrow keys, and iPad/iPhones don't have arrow keys. I
think what's probably confusing you is how to navigate the menus which come up
when you 'read clippings' or 'read book'. (On a full computer, people would
just try arrow keys intuitively and it would work, so the author of Anchorhead
didn't think it was necessary to describe the alternate key bindings.) The
trick is that you can use the N and P (for Next and Previous) keys to navigate
the menu items, RETURN to select, and Q or backspace to return to the game.
This works on almost all in-game menus. Most games tell you about N and P in
the status line, but Anchorhead unfortunately doesn't. This is actually
mentioned in the last paragraph of the "Getting Started" help page in Frotz as
well.
Hopefully this helps. If you still think you've hit a bug, please respond in
greater detail about what's going wrong. Also, you've commented on an
unrelated problem which is already fixed, so if you are still having problems,
please open a new issue report. Thanks.
Original comment by spath...@gmail.com
on 30 Jan 2012 at 4:14
Original issue reported on code.google.com by
phoesha@gmail.com
on 16 Mar 2011 at 1:15