cocos2d for iPhone

A fast, easy to use, free, and community supported 2D game engine

1. 

   astropaul
   Member

   I'm using 0.8.1.
   Menu's work fine for me, except when placed near the screen edges.
   Then they become very difficult to trigger. A direct touch does not
   work. You have to like touch the edges, and it's very difficult to
   get it to trigger. I create the menu button like this:

   MenuItem *btnNext = [MenuItemFont itemFromString:@"Play Next..." target:self selector:@selector(playNext:)];
   Menu *btnNextScene = [Menu menuWithItems:btnNext, nil];
   btnNextScene.position = ccp( 200, 30);
   btnNextScene.visible = NO;
   [self addChild:btnNextScene z:5 tag:NEXT_BUTTON];

   If I position it at 160,240 it works perfectly.
   But if I position it near the bottom of the screen, it does not work.
   Help!

   Posted 2 years ago #
2. 

   eshirt
   Member

   I've also noticed that in the simulator. I've got simple NSLog statements to register touch coordinates and mouse clicks anywhere within ~45px from any edge don't register all the time.

   Are you testing on a device, or in the simulator?

   Posted 2 years ago #
3. 

   astropaul
   Member

   Always on the device. Never the simulator.
   This is using 0.8.1 on iPhoneOS 3.1

   Posted 2 years ago #
4. 

   Blue Ether
   Member

   I would say that this probably has more than anything else to do with the angle of your finger and the size of your button. What size if the button? Small buttons can be difficult to touch, and especially so near the sides of the screen where the finger angle changes. It may "feel" like you're touching it, but you aren't. This has something to do with the hardware limitations and also something to do with psychology. General guideline I've heard for iPhone is to try to keep buttons at around 64 pixels or larger. You can get by with smaller. Once the button goes below 32 pixels or so in size it can get VERY difficult to press, especially if its at a location where the finger angle is very oblique.

   Posted 2 years ago #
5. 

   astropaul
   Member

   Thanks for the feedback Blue. But it's clearly not that. I have increased my button to 64 pixels tall, and 80 wide. If I place it at 200,200 it works perfectly with a single touch.
   If I place it at 200,30 it does not respond to touches at all. I have tried numerous ways of touching it, and nothing happens, but if I place it in the middle of the scene it works first time.

   Posted 2 years ago #
6. 

   jd
   Member

   The iphone surface is conductive so you may lose accuracy near the edges since less of your finger is on the screen, but I've noticed menu touches don't register as I would like them. It seems to be better at detecting touches at the lower region of the MenuItem than the rest. Did you try not using Menus and just detecting touches on images directly?

   Posted 2 years ago #
7. 

   eshirt
   Member

   FWIW - in the simulator, I've been able to consistently demonstrate that mouse clicks in the areas ~25px around each edge are ignored. The area itself can register touches - on a touchesMoved method into the area. But clicking on the very corner registers nothing.

   Of course, you really shouldn't be putting crucial targets in this area to begin with - but does anyone know if this is a bug in cocos2d or in the simulator itself?

   Posted 2 years ago #
8. 

   Steve Oldmeadow
   Administrator

   Are you sure about that eshirt? What simulator version? I just tested on the 3.1 simulator and I can click on the edges and bottom corners with no problem.

   There is a well known issue with the simulator where clicks don't register in the top most rectangle where the status bar would display. It is definitely not a cocos2d issue.

   Posted 2 years ago #
9. 

   eshirt
   Member

   Looks like that might be it... in landscape mode, the bottom left corner would actually be the top of the phone. I've always noticed it around the (0,0) point which wouldn't register until (28,28) or so. That would explain a lot.

   astropaul - could that be part of your issue as well? Although, you said it happens on the device...

   Posted 2 years ago #
10. 

    astropaul
    Member

    Yeah, this is on the device: iPhone 3GS with OS 3.1

    I hardly ever use the simulator, after I spent ages debugging an issue, which turned out only existed on the simulator.

    I have found, I can get the button to respond by moving it to 200,80 but that is 80
    pixels from the bottom of the screen, which is madness. The iphone screen is
    clearly touchable at 0-40 since that is where UIToolBar items work. Also if I log touches received by the layer, I can see it is being touched, but the menu button is just not triggering. Maybe I will try 0.8.2 release.

    Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.