Invisible black-on-black text

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Before upgrading to 1.4, set iphonefrotz to display 
green text on a black background. 
2. Start playing a game.  
3. Update to v1.4 from App Store. 
4. Return to previously started game.
5. The "double-tap a word to input it on the 
commandline" feature results in invisible black text 
being entered onto the commandline until you hit 
enter, at which point the text becomes visible.  

What is the expected output or behavior?  What do 
you see instead?
Text on commandline should always be visible. 

What version of Frotz are you using?
I believe it was the version immediately prior to 1.4. 

What version of iPhone/iPod Touch OS? (2.0, 2.1, 
2.2.1, 3.0, etc.)
iPhone 3G OS 3.1.2

Please provide any additional information below.
Resetting the text color and background color makes 
the problem go away. 
Apart from this minor bug, v1.4 is awesome. 

Original issue reported on code.google.com by ahope...@gmail.com on 20 Mar 2010 at 10:38

[GoogleCodeExporter]

Unfortunately, this problem slipped in at the last minute and I didn't notice 
it before releasing the new version.

I've got a fix for it, please expect a 1.4.1 to appear on the App Store early 
next week.  (Already submitted, 
waiting for Apple, but they've improved their approval rate lately so I'm 
optimistic.)

Original comment by spath...@gmail.com on 20 Mar 2010 at 2:51

• Changed state: Fixed-Pending

[GoogleCodeExporter]

I came here to report this exact issue, so am glad to hear this is already 
reported 
and fix is pending :-) I too was trying to get classic green screen mode and 
the 
black on black was killing that hope.

While I'm here, many thanks for the http file transfer option, as I could never 
get 
the adventures from my Activision Infocom classics CD to transfer over FTP for 
some 
reason (probably my router, I imagine), so with v1.4 I am really pleased to be 
able 
to get back into them.

Original comment by smithers...@gmail.com on 21 Mar 2010 at 10:17

[GoogleCodeExporter]

Fixed in 1.4.1

Original comment by spath...@gmail.com on 6 Apr 2010 at 3:58

• Changed state: Fixed