Orientation change causes play by play to grow (iPad)

[Tjor]

I accidentally had my iPad tip forward which caused then orientation to flip (upside down). When I put it back vertical iScore changed back but the play by play view grew and covered the bottom right part of the screen. The only way I could fix it was to close the app and reopen.

Cheers, // tim

[FTMSupport]

We have hadbthis reported before. The problem is there are no clear steps to reproduce tin it seems to happen somewhat randomly when rotating the device. If anyone can give us consistent steps to reproduce we can probably fix it but without steps, it appears to be an issue with the OS.

[Bill]

I had this happen to me on my iPad this weekend. I don't remember what I did prior to it happening, but I'll see if I can recreate a similar event, given the info about tipping the iPad forward. I just wish I had seen the tip about restarting the app, as I went the rest of the game without being able to track pitch location.

[Bill]

Hmmm....that was an easy bug to reproduce.

I started a game, hit FOUL about 5 times to get more play by play info than would fit in the window, tipped the top of the iPad down, screen orientation changed to upside-down, tipped it back....play by play spilled out of the window and over the pitch location window.

I repeated this several times with the same results. I also noted that when I had it "upsidedown", the play by play is completely empty. I also noted that closing the app and going back to the game corrects the problem (i.e., a workaround until this is fixed).

I am running v2.70.89 on the iPad (16GB, no 3G).

[FTMSupport]

We will try these steps and see if it consistently reproduces the issue. We have done similar steps many times, and it sometimes has the issue and other times it does not. But maybe there is something with using FOUL that makes these steps consistent - we did not hit FOUL over and over to try and reproduce the issue.

[Bill]

I see what you mean. After having repeated it a few time, I just encountered a game where I *COULDN'T* repeat the bug using what I believe were the exact same steps.

Would it help if I e-mailed you the stats of a hosed game?

[Bill]

Dang, now I can't figure out what I did differently the ONE time the bug didn't appear.

Here's a few things I noticed:

1) I can flip the screen at ANY time after hitting PLAY! to trigger the bug. I did it immediately after starting the game and then hit FOUL, FOUL, etc. and the play by play was spilling down. I did it after hitting FOUL, FOUL, etc. and the play by play was redrawn spilling down.

2) Once you tip the screen and create the bug, any other games you visit or start will also have the bug until you exit the app.

I think I will try different points in time for flipping the screen PRIOR to hitting PLAY! and see if I can isolate to that specific screen.

[FTMSupport]

We don't believe it has anything to do with the actual data in the game. As you have now seen, the exact same set of steps do not cause the issue to repeat consistently which makes us believe it is either an issue in the Operating System itself, or something that is just not obvious that has not been identified yet.

Thank you for your diligence in trying to reproduce in a consistent way because as soon as somebody IS able to do it consistently (i.e. same steps produce the same result every time), we will likely be able to fix it (or come up with a workaround if it is an issue in the Operating System).

[Bill]

Yeah, it's nothing to do with the data in the game itself.

I believe it has something to do with how the size (height) variable the sub-window gets initialized. Once the variable is set (either correctly or incorrectly) it will stay that way until you restart the app. So if you get it in a state where it is correct, it will stay correct; conversely if it is incorrect, it will stay incorrect until you restart the app. So the question is "what event initializes that variable?" That might help you guys reproduce it. I can't do much more unless I got to look at your source code.

Another observation is that the touch screen only recognizes touches within the original (i.e, smaller) play by play window. So the "touch window" is correct but the "display window" is not.

[OhioTex]

(sorry to interupt... but an envious iTouch user.. getting a chuckle...)