[iOS] IMPORTANT FOR PAUL!!! - GameCreators Forum

Author

Message

xGEKKOx

AGK Master

15

Years of Service

User Offline

Joined: 7th Dec 2008

Location: Italy

Posted: 10th Jul 2015 19:35

Link

Hi Paul, i discovered why the MKMapView doesn't refresh on iOS.

It depend on this:

+ Code Snippet

//if (displayLinkSupported){
        // CADisplayLink is API new to iPhone SDK 3.1. Compiling against earlier versions will result in a warning, but can be dismissed
        // if the system version runtime check for CADisplayLink exists in -initWithCoder:. The runtime check ensures this code will
        // not be called in system versions earlier than 3.1.
        
        displayLink = [NSClassFromString(@"CADisplayLink") displayLinkWithTarget:self selector:@selector(drawView)];
        [displayLink setFrameInterval:frameInterval];
        //[displayLink addToRunLoop:[NSRunLoop currentRunLoop] forMode:NSDefaultRunLoopMode];
        //} else {
        syncTimer = [NSTimer scheduledTimerWithTimeInterval:(NSTimeInterval)((1.0 / 60.0) * frameInterval) target:appDelegate.viewController selector:@selector(drawView) userInfo:nil repeats:TRUE];
        //}
        active = TRUE;

As you see to get the gesture back to work on some View, i must use the NSTimer.
What do you think about this?

Is safe or you must update it to work with the better NSDefaultRunLoopMode ?

I will do some other test and i will inform you if i found something interesting.

Youtube Channel WebSite FB Page

Back to top

Profile PM Website

xGEKKOx

AGK Master

15

Years of Service

User Offline

Joined: 7th Dec 2008

Location: Italy

Posted: 10th Jul 2015 19:55

Link

Ok i found a workaround, but you need to investigate for the Threads and the RunLoop too.

This is the code i changed to get ScrollViews and MKMapView work again...

Old Code
[displayLink addToRunLoop

NSRunLoop currentRunLoop] forMode:NSDefaultRunLoopMode];

New Code Fix
[displayLink addToRunLoop

NSRunLoop currentRunLoop] forMode:NSRunLoopCommonModes];

Hope this will send you in the right direction.

I also found some help on StackOverflow : HERE

Let me know if is ok my code in this way:

+ Code Snippet

- (void)setActive
{
    if ( g_bDisplayLinkReady == FALSE )
        return;
    
    if (!active){
        if(displayLinkSupported){
            displayLink = [CADisplayLink displayLinkWithTarget:appDelegate.viewController selector:@selector(drawView)];
            [displayLink setFrameInterval:frameInterval];
            [displayLink addToRunLoop:[NSRunLoop currentRunLoop] forMode:NSRunLoopCommonModes];
            
        } else {
            syncTimer = [NSTimer scheduledTimerWithTimeInterval:(NSTimeInterval)((1.0 / 60.0) * frameInterval) target:appDelegate.viewController selector:@selector(drawView) userInfo:nil repeats:TRUE];
        }
        active = TRUE;
    }
}

Youtube Channel WebSite FB Page

Back to top

Profile PM Website

xGEKKOx

AGK Master

15

Years of Service

User Offline

Joined: 7th Dec 2008

Location: Italy

Posted: 10th Jul 2015 21:38

Link

Ok i found that the common mode check about all run loop, so in this case is the best to get continuous animations of uiview and tables while the loop do something.

Paul confirm me is ok to use the common mode loop.
Thx in advance!

Youtube Channel WebSite FB Page

Back to top

Profile PM Website

Paul Johnston

TGC Developer

22

Years of Service

User Offline

Joined: 16th Nov 2002

Location: United Kingdom

Posted: 13th Jul 2015 19:40

Link

I'm not familiar with what the different loop modes do, I used NSDefaultRunLoopMode because it was in an example application, so I don't know the effects of using the common mode loop. Most AppGameKit applications aren't going to be using iOS UI widgets anyway so I probably won't be exploring this.

Back to top

Profile PM Email

xGEKKOx

AGK Master

15

Years of Service

User Offline

Joined: 7th Dec 2008

Location: Italy

Posted: 14th Jul 2015 17:41

Link

Thx Paul, anyway, all is working good with the new CommonModes.
So i think is safe.

Maybe you could add it in the official Template as a choice for a possible lost of touches on some Views.