Buttons/Touch mistery? « Sparrow Forum

Sparrow Forum » Troubleshooting

Buttons/Touch mistery?

(23 posts) (5 voices)

Started 1 year ago by Durrza
Latest reply from kevinmeziere

Tags:

Durrza
Member

Hi,
i've been using sparrow for a small while and whilist finding it great (amazing job guys!!!)
i've a problem i can't really understand, my touch events and my button presses are not being dispatched to my window i know the xib settings are correct beacouse setting breakpoints i can see the code flowing thru sparrow events chain, the target is my Game class and then the message never ever reaches my function, nor touches nor buttons.

[self addEventListener:@selector(onTouchEvent:) atObject:self forType:SP_EVENT_TYPE_TOUCH];
inside my scene class (everything else in that scene class works fine, including juggler, pre-frame events etc...).

and bit lower in the code
- (void)onTouchEvent:(SPTouchEvent*)event
{
int test
test=1;
}

i'm kinda clueless why is this happening, any ideas?

Debugging deeper i figured out that it doesn't work due to this
NSMutableArray *listeners = [mEventListeners objectForKey:event.type];
in SPEventDispatcher.m which is obiously null, so it returns the function right away, however i added the listener! The most strange thing is that mEventListeners is null itself, after i personally debugged and made sure the event was added properly. Yes i've cleaned and rebuilt already, any ideas?
Thanks.

Posted 1 year ago #
Daniel
Primary Feather
Hi Durrza!

Hm ... that's weird. One thing that might cause this is a wrong 'init'-method. Make sure that your scene class' init-method looks like this:
```
- (id)init
{
  if (self = [super init])
  {
    // init custom stuff
  }
  return self;
}
```
The important part is the "[super init]" part, as that calls the init-method of the superclass -- and that's where e.g. the "mEventListeners"-Array is created. You have to do that manually in Objective C, which makes it easy to miss if you have experience with other languages.

Could this be the problem?
Posted 1 year ago #
Durrza
Member

Nope the init is correct. i tried to add a listener for touches to the Game class and obiously works ok
i've debugged aswell into - (void)onEnterFrame:(SPEnterFrameEvent *)event of my scene mEventListener is correctly sized, valued. still receiving no touches

Posted 1 year ago #
baike
Moderator

This may be off base, as I don't fully understand your situation, but be sure to add the event listener to the class that will fire the event. Your mEventListeners will be null if you haven't added any events. So if you had a sprite that you wanted to fire touch events to your game class, you'd say:

[sprite addEventListener:@selector(onTouch:) atObject:game forType:SP_EVENT_TYPE_TOUCH];

Maybe you already had this sorted, but it would explain a null mEventListeners if you were looking for it in the wrong object.

Posted 1 year ago #
Durrza
Member

HI Baike,
no i don't have it sorted yet. Maybe i'll try to explain better what i am trying to achieve. I would like to tap the screen on a button to select the object, and then tap the screen anywhere else to "drop" that object. To achieve this into my Scene class (called World)
i've the button and the code as follows:
[self addEventListener:@selector(onTouchEvent:) atObject:self forType:SP_EVENT_TYPE_TOUCH];
self is an instance of World class (a class with loads of sprite childs used as game logic container basically), the mEventListener for World is not null, and contains the correct values my onTouchEvent function does not get called EVER.

Hi Daniel,
i'm having this problem aswell with Demo multitouch if i convert it to IPad project! Hence i suppose there is a problem with sparrow and ipad (i've tried running the demo in iphone compatibility mode and works great!) or a problem with the simulator (i dont' have access to a code sign facility to try it live on my ipad). After spending few hours debugging i think (i'm not 100% sure yet) that the problem resides into SPTouchProcessor.m on line 92
currentTouch.target = [mRoot hitTestPoint:touchPosition forTouch:YES];
returns my Game class, which obiusly has mEventListeners nullified since there are no events to listen on for the Game class (whilist there are for the childrens of the Game class. I assume that the touch object is sized correctly since it's visible and rendered with a decent size on the screen. I Will go further down the line with this problem since it's a necessity for me, but before i do, was ever a problem before (or better, was this a known problem and fixed into the svn distribution)? I'm using the stable release freshly downloaded.

Posted 1 year ago #
Durrza
Member

Gotcha!
It's the landscape mode container, wich i modified in the demo too as test

mContent = [[SPSprite alloc] init];
mContent.rotation = SP_D2R(90);
mContent.y = -768;

makes it all wrong, if i make the world child of the game itself, everything works great :0
i still don't know how to fix this tho

with mContent.y = 768; my screen is totally black, but the touch is received, i reckon there is something broken into the transformation "path" of the touches.

Posted 1 year ago #
Durrza
Member

FIXED. Daniel there is a bug into the transformation matrix for sure, i can't identify it tho, you should have enough element from this thread to reproduce i reckon, elsewise just ask and i'll make an example for you.

To other people that might eventually come across this problem here is a fix for you

_pivot = [SPSprite sprite]; [self addChild:_pivot]; _pivot.width = 768; _pivot.height = 1024; _pivot.x = 768; _pivot.y = 0; [UIApplication sharedApplication].statusBarOrientation = UIInterfaceOrientationLandscapeRight; _world = [[World alloc] init]; _world.rotation = PI_HALF; [_pivot addChild:_world];

Posted 1 year ago #
Daniel
Primary Feather

Hi Durrza!

It would be great if you could really create a small demo project that I can use to reproduce the problem! I just converted the Demo App to an iPad project, and I could not find any issues. Perhaps I misunderstood something, though.

Thanks a lot in advance! And thanks for all your efforts to get to the root of this problem.

Posted 1 year ago #
Durrza
Member

As soon as this project is finished i'll do Daniel, might take a week or so
Basically to reproduce the problem convert to iPad
into the Game class use the following
mContent = [[SPSprite alloc] init];
mContent.rotation = SP_D2R(90);
mContent.y = -768;
mScene = [[Scene alloc] init];
[mContent addChild: mScene];
[self addChild: mContent];

into the scene map a touchevent and you will never receive it due to a transformation problem (i think due to negative y?). Scene never gets picked as target, hence returns Game class all the time, which is obiously the wrong target, i haven't tested the code i just wrote to be reproducing the error, but i'm fairly confident it does since it's exactly what i was doing.
Cheers

Posted 1 year ago #
Daniel
Primary Feather

Hm ... sorry if I'm a little confused, but wouldn't the scene be invisible in that container? It lies outside of the screen! (Or did you want to move 'x' to '+768'?)

Posted 1 year ago #
Durrza
Member

on my simulator it was either -768 or wasn't working at all, with a 1024x768 subchild of the Scene, like that for me was 100% visible (i developed 99% of the AI like that )

Posted 1 year ago #
Daniel
Primary Feather

OK ... I guess I will wait until you have time to set up the demo project. In the meanwhile, if anyone else has a similar problem, please add the reports to this thread. Thanks!!

Posted 1 year ago #
Durrza
Member

Hi Daniel,
since reading from the forums you are so kind to every user, i decided to take sime time off to do the example for you, you can download it at http://www.qfpost.com/download.do?get=6d905db0cb50c6b7aa2bd7e4203d52cd it is 1.1MB beacouse of a stupid .png made in Preview that does not let you set the compression ratio sorry.
As you can see with the given code the image is visible, correctly orientated aswell, however receives no touch (they all go to Game class), i'm fairly sure it could be to bad coding practice (it's my first big ObjectiveC project) from me, however i would have expected Sparrow to react to the oddity of the coordinating, i hope it bugs for you aswell so you can recreate the problem as i did (no it's not a curse ). Please do let me know, i've already done a workaround for it and posted it in here, but after debugging 3 hours i wasn't really in the mood to go deeper into Sparrow .

Posted 1 year ago #
Durrza
Member

Daniel have you confirmed the problem by any chance?

Posted 1 year ago #
Daniel
Primary Feather

Hi Durrza!

Sorry, I have not yet found the time to try it! I will write about my findings as soon as I have the time to have a look at it.
Thanks for taking the time and creating the demo project! I'm sure I will get to the root of this =)

Daniel

Posted 1 year ago #
Daniel
Primary Feather

Just a short question: do you see anything when you start the project? When I do, it's only a black screen. I have to change the line with the pivot coordinate from

_pivot.y = -768;

to

_pivot.x = 768;

to see the image.

Posted 1 year ago #
Daniel
Primary Feather

Just a short question: do you see anything when you start the project? When I do, it's only a black screen. I have to change the line with the pivot coordinate from

_pivot.y = -768;

to

_pivot.x = 768;

to see the image.

Posted 1 year ago #
Daniel
Primary Feather

Now I've found the time to look at it.

First a short question: do you see anything when you start the project? When I do, it's only a black screen. I have to change the line with the pivot coordinate from

_pivot.y = -768;

to

_pivot.x = 768;

to see the image. And with these settings, I receive touch events in the "World"-class. Could it be that you unintentionally changed something in the source code of Sparrow?

Posted 1 year ago #
Durrza
Member

yes i do see the image with the example i linked,i do not without the -.
Nope i have not changed anything in the sparrow code, i done a diff between a fresh download and the one i use, no differences odd. Oh well it's solved for me anyway, you say you tested against your distribution and it's fine, let's close it as "not a bug" i don't know what to say really.

Posted 1 year ago #
Daniel
Primary Feather

Hm, that's really strange ... perhaps it is a bug in the current distribution, that I have fixed without knowing it was there *g* (because I made by tests with the latest development version).

Let's just ignore it for now, if the problem pops up again in the future we'll have another look at it =)

Posted 1 year ago #
repetitio
Member
I use Xcode 3.2.4. I have got a similar problem with dead buttons. I have used 'scaffold' and I use it on my iPad apps. I have changed:
```
//Game *game = [[Game alloc] initWithWidth:320 height:480];
    Game *game = [[Game alloc] initWithWidth:768 height:1024];
```
and then I have changed 'MainWindow.xib' in IB. I've changed 'View' resolution from 320x480 ---> 760x1024. But 'Window' resolution is fixed and greyed at 320x480. On screen I,ve got some sprites and full screen pictures, and everything work OK, but...
But buttons that are placed outside 320x480 region do not generate events.
I wonder how to change 'View' dimensions in IB from present 320x480 to 760x1024?
Posted 1 year ago #
Daniel
Primary Feather

Hi repetitio,

the next Sparrow version contains a new Scaffold project that makes it easier to switch to the iPad. I sent it to you via mail!

Posted 1 year ago #
kevinmeziere
Member

Daniel,
Can I get you to please send me the new Scaffold project?

Thanks!

Posted 1 year ago #
Daniel
Primary Feather

Hi Kevin,

that's the scaffold project that's part of the Sparrow 1.0 package!

It's configured for iPhone/iPod, but you can switch to iPad with one single setting in the build settings of the project. Find the setting with the name "Targeted Device Family" and set it to "iPad". That's all you have to do!

I hope that helps!

Posted 1 year ago #
kevinmeziere
Member

Daniel,
That worked wonderfully!! Thanks so much.

Posted 1 year ago #
Anonymous
Unregistered

yes iagree

Posted 1 year ago #
Anonymous
Unregistered

:lol:soft!!!!

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.