I can translate into german if you like:-)

I'll PM you!

Android Crosswalk is definitely the recommended way. At least you got it sorted

[quote:3fzxesqs]For best results publish with Crosswalk, which is like Google Chrome for Android turned in to a wrapper for native apps. For more information see How to export to Android with Crosswalk.

https://www.scirra.com/tutorials/367/how-to-make-android-games

https://www.scirra.com/tutorials/809/how-to-export-to-android-with-crosswalk

Hi Julia. It's hard to see but, in event 4, do you have -- instead of just - ?

edit: I mean are you doing it intentionally or not

If you haven't already, read these. Maybe you don't even need Anchor.

https://www.scirra.com/tutorials/73/sup ... reen-sizes

https://www.scirra.com/tutorials/1126/m ... ces/page-1

https://www.scirra.com/tutorials/1042/h ... creen-size

good luck

Any chance of providing a capx?

Hi!

I would like to translate it into German! And I could probably use some help with my project... .

Cheers,

Julia

Thanks! I'll PM you.

codah im also latin american (mexico) but there is not too much difference between mexican/spain spanish, if you dont use slang both can understand. there are some few words like "pick" mex= "tomar" Spain = "cojer" but we all can understand.

what i mean is, you dont need a latin american spanish translator and a spain translator, if you do you will also need an argentinean translator, colombian translator and so XDD keep up the good work

sorry for the delay. Thanks for the info

Maschka I will PM you

ok well it does look like you're wanting to spawn by name, as FredQ has suggested, but I still think the Family behaviour probably isn't the place to shoehorn that into (IMO). So yeah, Nickname is probably your solution.

Because when you pick an object, it's 'contained' objects are automatically picked, so you can just reference it.

Then perhaps a feature request.... such as, Create family object, where you can specify the ID of the actual family member. It's too bad this isn't possible.

With respect I'm not sure this really makes sense.

Like, say you have Sprite and Family1, with Sprite a member of Family1.

You're saying something like

System: Create object Family1("Sprite") on layer 0 at (0, 0)

Right now you just do

System: Create object Sprite on layer 0 at (0, 0)

for the same result. Am I understanding correctly?

+1 for Container, it's exactly what you want. Even if you didn't have Containers, you could just store an ID or UID to index into a separate array per sprite instance.