Closed GoogleCodeExporter closed 9 years ago
I'm afraid I still can't reproduce this. Are you sure this is a 'fresh'
install?
The attached image shows a font size of 12, while the default is 18.
Did you change any other settings?
My version of Nord and Bert appears to be the same version you are using
according to the header, but just to make sure the file isn't corrupted, mine
has a file size of 170285 bytes and a md5 checksum of
cc5a8334a4fbb51166c625e52738c668. Could you verify this? It's possible that
the file could have minor corruptions but still be playable if, say, it was
ever transferred vis FTP in ASCII mode by accident, for example.
I'm just grasping at straws trying to figure out what could be different for
you that could cause this.
Are there any other games which have missing status line for you, or is it only
N&B?
Original comment by spath...@gmail.com
on 9 Apr 2012 at 3:48
I just got the iPad on Friday, so I'm pretty sure it's a fresh install. :-)
I changed the font only. I tried changing it after I couldn't get the status
bar to show up, in a hope that it would.
Last night, while trying to play, the iPad went spinning through several 360
turns (not intentionally). When I picked it up, the status bar was visible.
Curiouser and curiouser.
Original comment by kno...@gmail.com
on 9 Apr 2012 at 1:50
OK. I was mislead by the term 'fresh install' into thinking that you had
deleted Frotz and reinstalled it a second time as part of trying to make the
problem go away, but you did not.
In fact, it looks like just killing Frotz (by double tapping home and doing a
long press on the Frotz icon) and restarting it, or rebooting your iPad would
have made the problem go away.
It looks like the problem is probably a timing issue in updating the bounds of
the status line window during rotation animation. I have seen this happen
before, but it's reasonably rare and will fix itself by rotating again a few
times or restarting. It looks like this is what is happening to you. I'm
updating the summary to reflect that.
Original comment by spath...@gmail.com
on 9 Apr 2012 at 9:02
Original comment by spath...@gmail.com
on 27 Sep 2012 at 6:48
Original issue reported on code.google.com by
kno...@gmail.com
on 8 Apr 2012 at 4:19Attachments: