Open GoogleCodeExporter opened 9 years ago
Could you post the code to reproduce it ? Thanks
Original comment by ricardoq...@gmail.com
on 28 Apr 2010 at 10:41
having a bunch of 480x320 frames from photoshop or whatever, with the buttons
and their out/over states in
the correct places..
1) create a 512x512 plist and png using zwoptex
2) create a ccmenuitemsprite with a ccsprite using the [[CCSpriteFrameCache
sharedSpriteFrameCache]
spriteFrameWithName: @"buttonimage.png"]
3) add it to a ccmenu.
no changing positions, so it'll use the offsets set up from zwoptex.
when the ccmenu goes to check the hit area, it'll go into the ccmenuitem "rect"
function, which only responds
using the contentsize.
as the contentsize of the ccsprite is 480x320, the hit area will be fullscreen,
instead of the proper bounding
box of the offset etc spriteframe.
i tried to figure out the proper offset maths today (would need to override the
ccmenuitem's rect function in
ccmenuitemsprite) but couldn't figure it out in a reasonable amount of time.
Original comment by psioni...@gmail.com
on 29 Apr 2010 at 12:10
Original comment by ricardoq...@gmail.com
on 26 May 2010 at 6:20
Original comment by ricardoq...@gmail.com
on 14 Jul 2010 at 9:48
Hi, I still find this important bug in the latest version, any news on when
could it be fixed? Thanks!
Original comment by guidog...@gmail.com
on 26 Jul 2010 at 1:55
@guidogoni: could you attach the code to reproduce it ? If possible a simple
project should be enough. thanks.
Original comment by ricardoq...@gmail.com
on 26 Jul 2010 at 4:38
Steps to reproduce:
1. Load a swoptex resource : [[CCSpriteFrameCache sharedSpriteFrameCache]
addSpriteFramesWithFile:@"animation.plist"]
2. Create a CCSprite from the texture loaded : CCSPrite *sprite = [CCSprite
spriteWithSpriteFrameName:@"animationFrame1.png"]
3. Size of image : [sprite contentSize] <---- this will return the size of the
texture loaded in step1, not only the sprite used later. Exactly the same
happens to the menu item, so it doesn't detect touch correctly
Original comment by guidog...@gmail.com
on 30 Jul 2010 at 3:50
Original comment by ricardoq...@gmail.com
on 17 Mar 2011 at 7:02
rescheduled for v1.1
Original comment by ricardoq...@gmail.com
on 13 Jul 2011 at 9:44
Original issue reported on code.google.com by
psioni...@gmail.com
on 28 Apr 2010 at 9:12