Issue with landscape browsing

[Kahciroz]

I'm not sure if anyone else is having this issue, but when I am in a set filter, browsing cards in landscape view, and adding selected ones to needed, trade, etc. The landscape full card view sometimes reverts to the list view while still remaining in the landscape layout. So I rotate my iPhone to portrate and back to landscape and then it brings me to the first card in my filter. Then if I turn it back to portrate, scroll down to where I left off and turn it to landscape it causes the same prob. So the only work around is to keep it in landscape and swipe my way back to where I left off. Then I add a few more and repeat. Just a tad annoying, I can live with it tho, just thought I'd point it out. Still 5/5 in my book 

[BlackJester]

I have had similar problems.  I think part of the issue is if the iPod is flat, like on a table.

[Mentonin]

I have this issue and it isnt even close to flat

[Piotr]

The coverflow will disappear when iMtG will receive - (void) didReceiveMemoryWarning from iOS. Here's what happens then:

    // Releases the view if it doesn't have a superview.
    [super didReceiveMemoryWarning];
   
    //DEV either here or in viewDidUnload it clears the advanced filters
   
//    if ( UIDeviceOrientationIsPortrait( [[UIDevice currentDevice] orientation] ) ) {
        if ( self.carousel ) {
            self.carousel.dataSource = nil;
            self.carousel.delegate = nil;
            [self.carousel removeFromSuperview];
            [self.carousel release];
            self.carousel = nil;
        }
//    }

    NSLog( @"CardListView memory warning" );

[MacUser001]

Yeah I've been noticing this rather annoying problem too. That's all it is though, annoying. Not a deal breaker. Would be nice to see it fixed though. Some of us don't understand that mumbo-jumbo you posted there, Piotr.

[Mentonin]

I understood 70%, though i cant tell whats the reference to other files without actually knowing the files

[Piotr]

Coverflow will disappear in low memory conditions. If it wouldn't, iMtG would probably crash. Now, why are we getting into these low memory conditions is a different matter.