Glitch/artifact when the device changes orientation

[pallzoltan]

I'm quite surprised that I can't find this issue in the tracker. The best way to explain is by a video:

http://www.youtube.com/watch?v=3oB5iE8JjS8

You see, the grayscale glitch on the left side of the folds is ruining the whole effect and awesomeness :) I'm testing on iOS Simulator 6.1 and also tried on a real device with iOS 6.1. Same effect.
If anyone had similar experience and found some sort of workaround, please let me know, it's quite crucial in our project.

Thank you,
Z.

[rootd]

I use this code to simply close the fold before orientation changes. I know this is suboptimal, however it works.

• (void)willRotateToInterfaceOrientation:(UIInterfaceOrientation)toInterfaceOrientation duration:(NSTimeInterval)duration {
  [self.paperFoldView setPaperFoldState:PaperFoldStateDefault animated:NO;
  }

[honcheng]

I've not been able to figure out how this can support orientation change yet. So it works for you after closing it automatically? I think there's problem with height not changed after the orientation change?

[pallzoltan]

Thanks rootd, I ended up using a similar (practically identical) solution.
@honcheng, the same glitch appears in Nav-Demo.

[pallzoltan]

Actually, there still is a problem even if you close on rotation, and that is that when you open it in the other orientation, the folds are white. Would be great to be able to force a redraw of the content somehow. I'll look deeper in the code later on and hopefully post a solution :)

[dstuecken]

Having the same issues here, did you find out how to redrew the whole thing @pallzoltan ?
I did not take a closer look in the code to find out the reason for this problem, maybe some else did and already fixed it?

[pallzoltan]

I think I've mentioned this before: instead of redrawing I use the less
userfriendly way of closing paperfold on rotation.
Don't have better news, sorry :)

Z.

On Mon, May 19, 2014 at 9:05 AM, Dennis [email protected] wrote:

Having the same issues here, did you find out how to redrew the whole
thing @pallzoltan https://github.com/pallzoltan ?
I did not take a closer look in the code to find out the reason for this
problem, maybe some else did and already fixed it?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/50#issuecomment-43471488
.