171 reputation
16
bio website tmogames.com
location Tucuman, Argentina
age 34
visits member for 1 year, 9 months
seen Mar 27 at 22:19

I'm a young developer, but and old gamer/animator/rigger and entrepreneur. I've always liked game development but only until a couple of year I've started learning to coding.

I'm learning ActionScript, haXe, C++ (a little) at a time.

I'm co-founder of Teatro Magico, an animation studio, and TMO Games is our brand for making games.


Oct
7
comment CCMoveBy values on update()
Finally, I get it working; but with other method. However, I'm interested in your answer. How should I do the CCSpawn?
Aug
17
comment Cocos2d-x Finding if a CCPoint is inside a sprite rect
This works even without the "touchPoint = littleHouse->converToNodeSpace(touchPoint);" lines
Jul
31
comment Cocos2d-x Finding if a CCPoint is inside a sprite rect
Your answer is almost correct, :), I've just finished with the "translation" to cocos2d-x. The only problem is the boundingBox(). With boundingBox I get all the screen as the "little house". I've solved using the same rect that I've posted initially: CCRect *graneroRect.
Jul
31
comment Cocos2d-x Finding if a CCPoint is inside a sprite rect
To clarify a little more: I have a house in a 1024x768 image, located at 33,83 (x,y) with size 326,382 (w,h). I packed that with TexturePacker, now I want to check if the touch location is in that rect (33,83,326,382)... But I have a coordinate mess
Jul
31
comment Cocos2d-x Finding if a CCPoint is inside a sprite rect
With this code everytime I touch the screen I get "The little...". Instead, I've tried changing CCNode for CCSprite, and getContentSize for getTextureRect().size.width. Now looks like it takes the correct Rect, but now that rect is in the lower left corner. I know this is because a spritesheet has its 0,0 at upper left, and cocos work with 0,0 at lower left. But why if I use Rect(33,83,326,382) I do get the correct "activation rectangle"?
Sep
28
comment What are the advantages and challenges of using HaXe over ActionScript 3?
Sorry if I created a confusion, I don't have experience with HTML5, those limitations are with HTML5 targeted from NME (haxenme.org). I gave it a shallow look when I was working with haXe+NME. The limitations are principally because the target is builded on another project called Jeash, a similar library but with not all the features that came with NME. So, you can read about some limitations here: haxenme.org/documentation/features I hope someone can give you a better answer to your question. In my case, I was using bitmapFill in my tests, and it's not supported by html5 target