I'm not sure it's the same problem, cause swapping app doesn't help at all.
Also...there's no actual delay on touch. It only causes fps drop.

This is down to an Adobe Air bug:

http://forum.starling-framework.org/topic/input-needed-touch-issues

but apparently it has been fixed in AIR3.8

Hello everyone,
I have following problem: Everytime I use touch input in my game on Android device (haven't tried on iPhone yet and on PC no problems), it causes game to lag. This doesn't show on Starling stats (top left corner FPS/mem info), but it clearly lowers fps. When I'm not touching anything, everything runs smoothly. I've tried to set touchable to false on as many display objects as possible, but with no success.
Any help would be greatly appreciated.

The touch lag issue is apparently fixed in AIR 3.8 beta

see this thread:

http://forum.starling-framework.org/topic/air-38-beta-available

My experience: windows=no lag, ipad=no lag, galaxy tab 7 p1000: massive lag, i tried Stuv's solution and it worked like a miracle BUT it causes the game to crash some time after game is started. anyone has same problem? i tried to let the app run without touching the screen and it didnt crash. it only crashed if i touch the screen. any word of advise?

My issue had to do with the project setup. I created a new project in flash builder, and dropped in all the same code, and it worked fine. Still a mystery, but more or less resolved.

Hm thats strange indeed. I thought you had a moving sprite aswell. Seems like we might have different problems <img src="http://forum.starling-framework.org/my-plugins/bb-smilies/default/icon_smile.gif" title=":)" class="bb_smilies" />

Interesting. The sprite I'm having a problem with isn't moving at all.

I thought it had something to do with the framerate, but no matter what framerate i run on (between 25 and 60), the issue is always there.
The faster the touchable sprites move, the further the distance between the touch and the actual image. i.e.:

a image is moving across the screen with 20px/frame:
Touching the image triggers nothing, touching 20 before it triggers a touch on the image.

when image is not moving, this doesn't happen. It seems that the image is already moved internally, but not yet drawn to the screen, but thats just a wild guess.

I'm not certain. The showStats box doesn't seem to be working, either.

What is the framerate of your app?

No, sorry - this is happening for me in the Flash Builder simulator (ie Flash Player).

I just made a post with the same issue (http://forum.starling-framework.org/topic/moving-spriteimage-with-touchevent). The problem seems to be mainly on android. iOS and desktop seem to handle this better.

Can you confirm if it's mainly Android?

But I still don't understand why though

I think I see where you are getting tripped up.

With Starling touches, the event.target will always be the deepest Starling DisplayObject in the display list hierarchy that is touchable in the scene at that touch location, (based on calling hitTest() recursively on DisplayObjectContainer)

You are assuming with the Starling Button, that the Button sprite itself is the e.target. However, a Starling Button is a more complicated sprite container that contains children, a contents Sprite that might also contain a background and a text child.

So when you are actually getting a touch that is hitting over a Button, it is one of the Button's children that is actually e.target and not just the Button instance itself.

When you write a generic touch handler like you are doing, and doing e.getTouch(game), that works fine, but you are asking for all active touches at the top-most game scene space (e.getTouch(someObject) supports bubbling so any touch on the object you pass in or any of its children will return active touches)
So you have lost a bit of granularity when you want to ask the question, 'which specific object is now being touched?'

Many times one doesn't have to think about 'which object was touched' if instead you were adding specific touch handlers directly to only one button or any specific parent and didn't care whether it was this sprite or any of its children that were actually e.target.

So now you see why switching the pause button to a plain 'Image' made it work because an Image has no children, so there is no where else deeper to go with the touch than the Image itself.

So there are a couple ways you could still have the original button, maybe a hack but knowing your button is a parent you might be able to pull off a check like
if(e.target && e.target.parent && e.target.parent == pauseButton)
(assuming there is only one parent level up from what was touched to the button,
for button you might even need e.target.parent.parent <img src="http://forum.starling-framework.org/my-plugins/bb-smilies/default/icon_sad.gif" title=":(" class="bb_smilies" /> )

or a little less code and generic, you could do another repeated filter check of touches using the pauseButton as a target
inside your objectPressed handler, like
if (e.getTouch(pauseButton, TouchPhase.BEGAN))

Finally, (more of an advanced exercise) some users find it convenient to override the default hitTest() function of DisplayObjectContainer if they are writing a deeply nested sprite with children, but still want 'this' to be the e.target for touches all the time and not any of its children. (one might have thought Starling's Button should maybe always return 'this' for its hitTest for touches but I don't think any Starling display objects do this by default).
http://forum.starling-framework.org/topic/something-is-not-right#post-29208

I had the same issue. here's how I fixed it:

if(touch)
   {
      //smallObjects is an array containing all relevant game objects on screen
      if( (e.target as DisplayObject) == smallObjects[currentObject])
      {
         //in here I handle all game/touch logic and that all works well
      }

Hope that helps

Wow this is so stupid. I slaved over this issue for 5 hours yesterday to no avail and now, right after posting the question I seem to have found a work-around. Changing the pauseButton to an image made everything better. That was I could use:

if(e.target == pauseButton)
   //pause logic

But I still don't understand why though. I'm guessing it has something to do with event propagation?

I am having trouble correctly targeting objects on the screen. This is probable very, very simple but let me explain. The basic setup is like this:

addEventListener(TouchEvent.TOUCH, objectPressed);
 
private function objectPressed(e:TouchEvent):void
{
   var touch:Touch = e.getTouch(game, TouchPhase.BEGAN);
   if(touch)
   {
      //smallObjects is an array containing all relevant game objects on screen
      if(e.target == smallObjects[currentObject])
      {
         //in here I handle all game/touch logic and that all works well
      }
      else
      {
         //wrong object pressed
         wrongAnswerSoundFX.play();
      }
   }
}
 
//then at another place I have this pause button and wanted to use the TRIGGERED event
//the pauseButton is also positioned away from the game objects, in the upper right corner
 
pauseButton.addEventListener(TouchEvent.TRIGGERED, pauseGame);
 
private function pauseGame(e:TouchEvent):void
{
   //pause game logic, not a problem
}

The problem is that I can't exclude the pause button from the objectPressed function. I tried doing something like:

//inside the objectPressed function, at the top, before anything else
if(e.target == pauseButton) //shouldn't this work?
   return; //to exit the function

But that didn't work either. It doesn't even know if e.target is pauseButton.

This is probably an easy one but I can't seem to wrap my head around it.

Yeah - I actually set the viewport based on the stage width and height. Also, the contentScaleFactor is set to 1.

Does your values for Starling stageWidth/stageHeight and the Starling viewPort have the same aspect ratio? If one is stretched in one direction compared to the other, I think I remember that it will break things.

Please help. I'm just a wretched gutter rat in need of aid...

I'm having a problem with a subclass of starling.display.Sprite. I'd like for a child to grow when the parent is touched. Unfortunately, the touch event is getting triggered by an area below the actual sprite (in the y+ direction), and sometimes the Touch passed in through the TouchEvent is null.

there's my code:

package code
{
	import com.greensock.TweenLite;
	import com.greensock.loading.*;
	import flash.display.Bitmap;
	import flash.events.MouseEvent;
	import starling.display.Image;
	import starling.display.Sprite;
	import starling.events.*;
	import starling.textures.Texture;
	public class NumberSymbol extends Sprite
	{
		private var number_img:Image;
		private var wheel:Sprite;
		private var dot_txt:Texture;
		private var dots:Vector.<Image>;
		private var variable:String;
		private var value:uint;
		private var adjusting:Boolean;
		private var touch_id:int;
		public function NumberSymbol(value:uint=0, variable:String=null)
		{
			super();
			this.variable = variable;
			this.value = value;
			addEventListener(Event.ADDED_TO_STAGE, onAdded);
		}
		private function onAdded(e:Event):void{
			var wheel_bmp:Bitmap = (LoaderMax.getLoader("wheel") as ImageLoader).rawContent;
			var wheel_txt:Texture = Texture.fromBitmap(wheel_bmp);
			var wheel_img:Image = new Image(wheel_txt);
			wheel_img.x = -wheel_img.width>>1;
			wheel_img.y = -wheel_img.height>>1;
			wheel = new Sprite();
			wheel.addChild(wheel_img);
			wheel.scaleX = 0.3;
			wheel.scaleY = 0.3;
			addChild(wheel);
			adjusting = false;
			var number_bmp:Bitmap = (LoaderMax.getLoader("number") as ImageLoader).rawContent;
			var number_txt:Texture = Texture.fromBitmap(number_bmp);
			number_img = new Image(number_txt);
			number_img.x = -number_img.width>>1;
			number_img.y = -number_img.height>>1;
			addChild(number_img);
			addEventListener(TouchEvent.TOUCH, onTouch);
			var dot_bmp:Bitmap = (LoaderMax.getLoader("dot") as ImageLoader).rawContent;
			dot_txt = Texture.fromBitmap(dot_bmp);
			dots = new Vector.<Image>();
			setValue(5);
		}
		private function setValue(val:uint):void{
			val = val%6;
			if(value<val){
				for(var i:uint=value; i<val; i++){
					var dot_img:Image = new Image(dot_txt);
					var angle:Number = (i*72-90);
					dot_img.x = 46*Math.cos(angle*Math.PI/180)-dot_img.width>>1;
					dot_img.y = 46*Math.sin(angle*Math.PI/180)-dot_img.height>>1;
					dots.push(dot_img);
					addChild(dot_img);
				}
			}
			else if(value>val){
				for(var i:uint=val; i<value; i++){
					removeChild(dots.pop());
				}
			}
			value = val;
		}
		private function getValue():uint{
			return value;
		}
		private function onTouch(e:TouchEvent):void{
			var touch:Touch = e.getTouch(this);
			//trace(touch);
			if(touch.phase == TouchPhase.BEGAN){
				if(adjusting == false){
					trace(this.getBounds(this)+", "+this.pivotY);
					touch_id = touch.id;
					adjusting = true;
					TweenLite.to(wheel, 0.5, {scaleX:1, scaleY:1});
				}
			}
			else if(touch.phase == TouchPhase.MOVED){
				if(touch_id == touch.id){
				}
			}
			else if(touch.phase == TouchPhase.ENDED){
				if(touch.id == touch_id){
					TweenLite.to(wheel, 0.5, {scaleX:0.3, scaleY:0.3});
					adjusting = false;
				}
			}
		}
	}
}

and before you ask, I am in TOP_LEFT and NO_SCALE mode. Does anyone know what coudl be going wrong here?

I've got this same offset problem, even though I am in TOP_LEFT and NO_SCALE mode. Touch events seem to fire below (y+) the sprite in question.

cool, thanks.

Not sure how many native controls you will end up having in your scene, but you can always add some 'did hit native control' checking in your Starling touch code right before you do anything in the Starling layer. See if the global touch location hitTests a native button, and if so, ignore the touch.

Hi,

I have a game scene created with Starling and some buttons made in regular flash display list on top of the game scene (like in Angry Birds Facebook).

The Starling stage listen for touch events. But when I click on the flash display list objects, the touch event is triggered by the Starling stage. Is there a way to avoid this behaviour?

I tried to attach the listener on a Quad placed on top of the game scene instead of the Starling stage but the touch event is not triggered at all.

here is my code for the gamescene :

stage.addEventListener(TouchEvent.TOUCH, onStageTouch);
 
private function onStageTouch(event : TouchEvent) : void
{
    var touch : Touch = event.getTouch(stage);
 
    if (touch && touch.phase == TouchPhase.ENDED)
    {
        doSomething();
        return;
    }
 
    if (touch && touch.phase == TouchPhase.HOVER)
    {
        doSomethingElse(touch.globalX, touch.globalY);
    }
}

the code for the flash display list button :

var closeButton : CloseButton = new CloseButton();
closeButton.buttonMode = true;
closeButton.addEventListener(MouseEvent.CLICK, onButtonClick);
 
private function onButtonClick(event : MouseEvent) : void
{
     quitGameScene();
}

@Markel

btw have you tried linking Gestouch against source code or compiled swc? (with that ASC 2.0 and inline stuff)
Because maybe the new compiler will work just fine with swc, affecting only YOUR code.

@clozertou

was there something unclear with the examples?

Hey, how can i apply multiple guestures to a single flex button? single tap (do different), double tap (do different task), and tap and hold?
A code example vl b highly appreciated.

@Pavel, I've updated the post. I guess it matters which of the objects listens to the zoom event.

@skol

that looks totally random... you'd better analyse what's wrong with the point. Put a simple project somewhere maybe?