Closed GoogleCodeExporter closed 8 years ago
The thought occurs (it previously hadn't) that I'd still need the "enter" key
in order to submit my command... but maybe when the keyboard is locked, we
could have a single horizontal row at the bottom with SPACE, RETURN and
BACKSPACE?
Original comment by ilprimoc...@gmail.com
on 27 Jan 2013 at 10:55
Since some games need the arrow keys (but often to the exception of the rest of
the keyboard), and others use the Function Keys (Beyond Zork, for one, and
Arthur has a function where you can switch between the displays of the graphic
window - or remove it entirely, which might be a welcome thing to do in a small
device), I've been thinking about this.
Let's say that there are two toggleable options, just underneath "Word
Completion On/Off": "Function Keys" and "Arrow Keys". The "Function Keys" could
be displayed on top of the screen, above the status bar.
Or maybe an option isn't necessary. I just noticed there's space, even in my
smaller device, for a button between "Frotz I" and the "Keyboard button". Let's
say that clicking that button toggles between the activation of a Function Keys
overlay that could cover the status bar ('cause it's temporary and easy to hide
again), the activation of "arrow keys" (another overlay that displays ABOVE the
virtual keyboard - more on that in a sec), activation of BOTH and DEactivation
of both. As an optional treat, holding the button could give us a menu with the
choice of which to use. Or maybe this is unnecessary and, since both are used
sparingly, the button could just toggle BOTH on and off at the same time.
As to the arrow keys, I was thinking that they could be ABOVE the virtual
keyboard. This would naturally take a lot of space - UNLESS the keyboard is
minimised, and most games that require the arrow keys don't use much of the
keyboard anyway. So the arrow keys on a minimised keyboard PLUS the ability to
lock the keyboard OFF, as in the first suggestion, with only the inclusion or a
RETURN and BACKSPACE key to the arrow keys overlay, would be a minimalist but
fully functioning way to play such a game, without sacrificing anything else,
and hopefully with a minimum of hassle.
Of course, talk is cheap, you're the one who actually has to implement all of
this, but what are your thoughts on it?
Original comment by ilprimoc...@gmail.com
on 5 May 2013 at 10:06
Going back to my original comment, I'd like to add: when I first suggested it,
I was mostly thinking aloud. But now I'm finding that landscape orientation
seems to be the best way to play IF on my iPod Touch. It's more pleasing to the
eye, and it's easier to write.
And if I hide the keyboard, I'm left with a perfect screen of text that is just
ideal. It's beautiful. It really makes me wish I could lock that keyboard in
place and use the typing shortcuts - INCLUDING the overlay you provide with
standard commands - so I wouldn't keep having to scroll up so many times...
because the keyboard takes up half the screen.
Really, until you try it, you have no idea how much more natural the landscape
view is on a small device. I'd say it's worth investing in.
Original comment by ilprimoc...@gmail.com
on 30 Mar 2014 at 11:17
I've got something whipped up for this allowing keyboard locking, and return /
delete word glyphs on the right of the command line (like the clear input glyph
that's there normally).
(Unfortunately, arrow keys and Fn keys will have to wait, because full keyboard
overlay APIs are too new and I want this version to still support old devices.
This will be the last version maintaining such support (and it fixed the issues
with gen 1 devices), so I can support only iOS 7 and newer going forward.)
Original comment by spath...@gmail.com
on 28 Jul 2014 at 7:31
Original comment by spath...@gmail.com
on 28 Jul 2014 at 7:31
Shame you'll eventually have to drop support for older devices, but I don't
suppose Apple's giving you much of a choice, software-wise. And of course I'm
glad to see you accepting this suggestion!
Original comment by ilprimoc...@gmail.com
on 28 Jul 2014 at 8:25
Actually, the reason I'm now able to drop support is that Apple now lets older
devices automatically download the most recent older version of software that
still support them. So users of ancient devices won't get new features, but
can still use Frotz, even if they get a hand-me-down device and have never had
Frotz installed before.
Original comment by spath...@gmail.com
on 28 Jul 2014 at 3:01
Oh. Well, that's another matter entirely. That's... quite awesome of them,
really.
Original comment by ilprimoc...@gmail.com
on 28 Jul 2014 at 9:07
Original comment by spath...@gmail.com
on 14 Aug 2014 at 7:48
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
Original issue reported on code.google.com by
ilprimoc...@gmail.com
on 27 Jan 2013 at 10:57