UIAlertView disrupting SPTouch events?

Sparrow Forum » Troubleshooting

UIAlertView disrupting SPTouch events?

(9 posts) (3 voices)

Started 1 year ago by cloistermaximus
Latest reply from Daniel

Tags:

cloistermaximus
Member

Hey, I've been banging my head against this one. Has anybody seen a UIAlertView event (incoming call, text message, low battery warning) happen during a sparrow app SPTouch event? I'm working on a game that uses 2 button controls—but if an alert dialog happens when the user is pressing one of the buttons it seems like the SPTouch phase gets lost and the buttons become inoperable.

I can go into more detail if needed—but I'm hoping somebody here has run into this and found a way to deal with it.

Posted 1 year ago #
Daniel
Primary Feather

Hi!

I haven't run into this issue yet -- but I can't remember testing it, either. I will have a look at it and inform you about the outcome!

Posted 1 year ago #
cloistermaximus
Member

Thanks a bunch for looking into this for me. Here is some example code that will cause the issue. Simply click and hold one of the buttons, wait for the alert, clear the alert, and the start clicking buttons again. You'll see that they get all wonky afterwords.

(Game H):
#import <Foundation/Foundation.h>

@interface Game : SPStage

SPTouch *buttonLeftPressed;
SPTouch *buttonRightPressed;
SPTouch *buttonLeftReleased;
SPTouch *buttonRightReleased;
int timerCountDown;
-(void)leftButtonPressed:(SPTouchEvent*)event;
-(void)rightButtonPressed:(SPTouchEvent*)event;

@end

(Game M)

#import "Game.h"

@implementation Game

- (id)initWithWidth:(float)width height:(float)height {
if (self = [super initWithWidth:width height:height]) {

SPQuad *gameButtonLeft = [SPQuad quadWithWidth:(150) height:(150)];
gameButtonLeft.color = 0xff0000;
gameButtonLeft.x = 0;
gameButtonLeft.y = 0;
[self addChild:gameButtonLeft];

SPQuad *gameButtonRight = [SPQuad quadWithWidth:(150) height:(150)];
gameButtonRight.color = 0xff0000;
gameButtonRight.x = 0;
gameButtonRight.y = 200;
[self addChild:gameButtonRight];

[gameButtonLeft addEventListener:@selector(leftButtonPressed:) atObject:self
forType:SP_EVENT_TYPE_TOUCH];
[gameButtonRight addEventListener:@selector(rightButtonPressed:) atObject:self
forType:SP_EVENT_TYPE_TOUCH];

timerCountDown = 0;
[self addEventListener:@selector(onEnterFrame:) atObject:self
forType:SP_EVENT_TYPE_ENTER_FRAME];
}

return self;
}
- (void)onEnterFrame:(SPEnterFrameEvent *)event
{
timerCountDown++;
if (timerCountDown == 50)
{
UIAlertView *alert = [[[UIAlertView alloc] initWithTitle:@"Test Scenero" message:@"This is a alertbox that interups controls." delegate:self cancelButtonTitle:@"OK" otherButtonTitles:nil] autorelease];
[alert show];
}
}

-(void)leftButtonPressed:(SPTouchEvent*)event
{

buttonLeftPressed = [[event touchesWithTarget:self
andPhase:SPTouchPhaseBegan] anyObject];
buttonLeftReleased = [[event touchesWithTarget:self
andPhase:SPTouchPhaseEnded] anyObject];

if (buttonLeftPressed)
{
NSLog(@"Left Button Pressed");
}
if (buttonLeftReleased)
{
NSLog(@"Left Button Released");
}
}

-(void)rightButtonPressed:(SPTouchEvent*)event
{
buttonRightPressed = [[event touchesWithTarget:self
andPhase:SPTouchPhaseBegan] anyObject];
buttonRightReleased = [[event touchesWithTarget:self
andPhase:SPTouchPhaseEnded] anyObject];
if (buttonRightPressed)
{
NSLog(@"Right Button Pressed");
}
if (buttonRightReleased)
{
NSLog(@"Right Button Released");
}
}

@end

Posted 1 year ago #
Daniel
Primary Feather

Thanks, that will help!

Posted 1 year ago #
alex_h
Moderator

I think this is the same problem I had with a UIWebView:

http://forum.sparrow-framework.org/topic/touches-on-a-uiwebview

One quick fix for this is to modify SPView as follows:

SPView only processes touches associated with itself:
for(UITouch *uiTouch in [event touchesForView:self]){
...
}
So the UIAlertView prevents any touches coming through into the body of that loop.

Changing that line to use [event allTouches] fixes the problem

Not ideal, but should work.

cheers,

Alex

Posted 1 year ago #
cloistermaximus
Member

@Alex: I just tried that out without any luck. I think this problem might be a bit different from the one you experienced since it seems that the touches from the other view will work fine, but if the user was holding down a touch state on a Sparrow view before the alert takes over Sparrow seems to lose the release state.

Posted 1 year ago #
aobama52
Member

Golf Clubs for Sale Are Coming

Your conscious mind gets involved and says that you need to hit the ball with [url=http://www.golfsale18.com]golf clubs for sale [/url] harder and change your swing a little to try and get the ball higher in the air so it does not land in the water. You are fighting with yourself a little because you want to hit down through the rough at your ball but on the other hand you feel the need to hang back and try to get it up out of the rough quickly. ishiner

Posted 1 year ago #
Daniel
Primary Feather
Hello again,

I just had a look at it. Thanks again for posting a simple to reproduce sample, this has saved me a lot of time =)

I found the problem. When an alert box is shown, UIKit calls SPViews "touchesCancelled:" callback, with a touch event. This event contains a "timestamp" when the the touch occurred, and Sparrow relies on this timestamp.

However, for whatever reason, UIKit sends the wrong timestamp when touches are canceled! Thus, Sparrow's code runs into problems.

I can give you an easy workaround for now. In SPView.m, line 250, add an additional line, like this:
```
- (void)touchesCancelled:(NSSet *)touches withEvent:(UIEvent *)event
{
    mLastTouchTimestamp -= 0.0001f;
    [self processTouchEvent:event];
}
```
That is not very elegant, but it works! I will see if I find a better solution for the problem; outerwise, I will add this to the official source code.

Thanks for pointing me to this problem!
Posted 1 year ago #
cloistermaximus
Member

Works perfectly! Thanks a million, I owe you one. You can thank my QA team for finding that little bug.

Posted 1 year ago #
Daniel
Primary Feather

Great to hear that it works! Greetings to you QA team, they did a great job =)

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.