cocos2d for iPhone

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

1. 

   pabloruiz55
   Member

   Hi!

   I have a layer with a menu, when touching an option i am adding another layer which overlays the previous one and displays some options.
   Now even though i am setting the first layer's isTouchEnabled to NO i can still select the options. Is this an expected behaviour? How can i disable the menu without having to set every option to disabled and then enable them when dismissing the overlaying layer?

   I think that istouchenabled should disable every element from the layer, why wouldn't it?

   Thanks!

   Posted 2 years ago #
2. 

   crmagicxxx
   Member

   Didn't quite understood what you refer to first layer? Is that layer on the bottom that you created first, or is that layer on the top?

   if it's layer on the top, you have two options:

   1) if you're using old touches system, then you actually need to set isTouchEnabled to YES, because if you set it to NO, all the touches are disposed to other receivers, in your case layer below. And you also need to handle ccTouchesBegan, ccTouchesMoved, and ccTouchesEnded in such way that you return kEventHandled even you don't need those events. For every touch event you didn't handle in that layer, it will be also disposed to children...

   2) you can use new touch dispatcher which has an option to swallow the touches.

   Posted 2 years ago #
3. 

   pabloruiz55
   Member

   Mhh i have a layer, with the menu, then i create another layer ON TOP of the menu layer. I want to stop the menu layer from receiving the touches, thus setting its istouchenabled to NO should suffice... So the only layer that would handle the touches would be the one on top.

   If i use the touchdispatcher to create an area for the whole screen to receive the touches (in the topmost layer) and set the highest priority for it, the menu from the layer below still gets the touch...

   Posted 2 years ago #
4. 

   crmagicxxx
   Member

   First, even you set that layer to not receiving touches, it doesn't affect menu items.

   Though, my methods should work for you because I am using the exact ones in 2 of my games. But I have to check when I get to my Mac, if I have menu items below at all and if they behave differently compared to other touchable objects, though I doubt that. But I'll test it tomorrow and tell you my results if someone else don't answer you in the meantime. If what you're telling is true, about menu items receiving touches even they are covered with full layers handling all the touches, then that's unexpected behavior for me or intended feature that I don't understand. In that case you'd need to manually disable all menu items or report a bug if that's not some strange intended feature...

   Posted 2 years ago #
5. 

   Clain
   Member

   http://code.google.com/p/cocos2d-iphone/issues/detail?id=247

   If that's the same issue, then a fix is scheduled for 0.8.2

   Posted 2 years ago #
6. 

   riq
   Key Master

   isTouchEnabled disables/disables all touches from the Layer.

   be sure to add: self.

   eg:
   

   self.isTouchEnabled = NO;
   self.isTouchEnabled = YES;

   but this feature (enabling/disabling touches after creating the layer) was introduced in v0.8.1 (or v0.8.0)

   Posted 2 years ago #
7. 

   pabloruiz55
   Member

   @riq, i am using 0.8.1 and doing like you wrote, even then the menu items from the layer below are receiving touches.

   What i am doing exactly is: one of the items, when touched calls a function.

   that function does:

   self.isTouchEnabled = NO;
   [self addChild:[AnotherLayer node]z:2];

   if i touch the screen after that i can still touch the elements of the layer below.

   Posted 2 years ago #
8. 

   MikeSz
   Member

   had same problem yesterday or 2 days ago, it's REALLY simple to solve it ;)

   ready ?

   ok, so Menu is a Layer by itself. and you need to disable it as well ;)

   so just make a Menu * mn; (or whatever) in the header file and then when you disable the layer - self.isTouchEnabled = false; - add a line: mn.isTouchEnabled = false;

   that's all. just disable all the menus manually and you're good to go

   btw - Riq, great thanks for adding dynamic touch control in .8.1, helps a lot if you can switch layers like that in the runtime

   Posted 2 years ago #
9. 

   pabloruiz55
   Member

   Thanks mike! That solved my problem :D

   Posted 2 years ago #
10. 

    MikeSz
    Member

    np mate ;) good timing really, that's all

    @ riq - not sure but maybe this behavior should be posted under issues ? it's quite unexpected that disabling a layer does not disable it's menus... should be easy to solve too, just check all the children and look for menus ?

    Posted 2 years ago #
11. 

    riq
    Key Master

    @mikesz: I'm not sure if that should be the default behavior. But at least it should be documented that the "isTouchEnabled" property is not propagated to it's children.

    Posted 2 years ago #
12. 

    MikeSz
    Member

    maybe add a function like

    -(void) DisableTouchDelegate:(bool) forAllChildren;

    just a suggestion ;)

    Posted 2 years ago #
13. 

    MCroswell
    Member

    Is this still the case? I am using 99.4 and when disabling the layer's touch, the children still receive it.

    @riq: Good idea regarding docs.
    @mikesz: I like that last suggestion. Also, thanks all for the education. I was going nuts until I saw how I just have to do the children explicitly.

    Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.