Space-bar fails if screen hasn't fully scrolled down

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Load a game into iOS Frotz and start playing it. (I happened to choose Earth 
& Sky 1 from the IF Archive.)
2. At the text input prompt with the keyboard visible, scroll the screen up 
slightly. 
3. Type a word and then press space.  

What is the expected output or behavior?  What do you see instead?
- The space will fail to appear unless you manually scroll the screen back down 
again first.
- What should happen is that a space should be printed at the commandline 
whenever you press space!

What version of Frotz are you using?
1.5.3

What device model are you using (iPhone 3GS, iPad, iPod Touch 3rd gen, etc.)
iPhone 4

What version of iOS?  3.2, 4.0, 4.3, etc.)
5.0.1

Please provide any additional information below.
- Very annoying bug!

Original issue reported on code.google.com by cxde...@gmail.com on 5 Mar 2012 at 8:54

[GoogleCodeExporter]

This is actually an intentional feature intended to help users of Bluetooth 
keyboards, so you can scroll the screen by pressing space without having to 
lift your hands to touch the screen.

Pressing space when the command prompt is obscured will scroll the screen a 
page at a time until it is fully visible, and then pressing it again will 
operate normally.

You could argue that this should only happen when you are actually using a BT 
keyboard, and I would agree; however, Apple has made it impossible for apps to 
detect whether they are using a real or virtual keyboard by not exposing this 
in their APIs, so there's not much I can do there.

Why do you find this to be particularly annoying?  Does it happen all the time 
to you for some reason?  Normally commands don't begin with spaces, and so 
typing a command beginning with a letter will both scroll and echo and prevent 
the issue.   (I could perhaps make space do this as well if the prompt is 
partially but not fully visible, but I have to make it not echo when the prompt 
is completely offscreen in order to keep the BT keyboard support working well.  
But again, it doesn't seem like a big deal at all to me, so please make your 
case as to why it's annoying.)

Thanks

Original comment by spath...@gmail.com on 6 Mar 2012 at 12:24

[GoogleCodeExporter]

Thanks for the reply. 

I wasn't aware of the Bluetooth feature, but in any case what perhaps wasn't 
clear in my bug report was that when I'm using the onscreen virtual keyboard, 
typing a non-space character, such as "x", when the screen is not fully 
scrolled does NOT "both scroll and echo"; it echoes WITHOUT scrolling the 
screen back down -- so "x" appears at the prompt, but you then have to press 
space TWICE (once to get the screen to scroll down fully, and then once again 
to actually print a space).

CD

Original comment by cxde...@gmail.com on 6 Mar 2012 at 12:39

[GoogleCodeExporter]

Ah, interesting.  This appears to happen only on iPhone and not iPad, so it's 
probably just a geometry issue that needs to be tweaked.

Thanks for reporting it.

Original comment by spath...@gmail.com on 6 Mar 2012 at 12:46

[GoogleCodeExporter]

I've noticed the same problem on an iPhone 4 with ios 5.1
It is very annoying! I forget about it and it keeps catching me out. 
To clarify the effect: 
When the screen is not fully scrolled to the bottom:
Type t (for example)
The screen scrolls almost but not quite fully down.
>T is visible and so is take (offered as auto completion)
Press space to accept auto complete or type the rest of the word followed by 
space
Now the screen scrolls the rest of the way down just uncovering a tiny bit of 
white space
Continue typing (say gold)
Now we have either tgold or takegold depending on whether we used the auto 
complete

I hope this is useful to you. Great prog, thanks for all the hard work

Original comment by robertda...@gmail.com on 23 Mar 2012 at 8:53

[GoogleCodeExporter]

Fixed in svn -r262
Will be in next App Store update.

Original comment by spath...@gmail.com on 4 May 2012 at 5:29

• Changed state: Fixed-Pending

[GoogleCodeExporter]

Fixed in 1.6 on App Store.

Original comment by spath...@gmail.com on 23 Oct 2012 at 1:46

• Changed state: Fixed