EDIT - I fixed it. It is a weird thing though in that it doesn't happen on export as long as I define and clear the arrays explicitly at the start of the layout. I don't know why it fixes the problem, but one cannot always look a gift horse in the mouth. Maybe something was writing to or reusing some specific memory address/ i don't really know.

Presumably, you know that Arrays don't start blank. They start with 10 slots, all filled with 0's. I discovered this by outputting the JSON to a debug Text object.

I've never found margins to be helpful in C2.

Sadly, I am not as good with Android or Crosswalk.

Start by getting rid of your 500,500 margins.

I think it might be better to get rexrainbow to encrypt the key in the plug, or at least allow users to set what the key is at runtime which we can in turn encrypt/ decrypt ourselves via some other plug.

But you need to make a post in his thread about the plug, otherwise he may not see this.

It's not like he's not super busy with other stuff.

You can't really encrypt anything in the browser, because people can simply take your key and encryption algorithm and decrypt the key in the source. Javascript is never secure.

Does C3 have non-canvas layers available?

Look at using a spriter, or Spine. If you want to do it yourself, you have to make a separate frame in the Sprite object for like 60 different directions.

I think they are working on it. I have had to login again recently, so hopes to fixing it.

Other useful technical terms include 'thingamajig' and 'thingamabob'

My DoD mentor used the word 'jabi' for everything too, lol.

Yes, it is possible.

It is a severe PITA. If you are REALLY insistent, I will send you a few test files I have lying around.

Your best bet is to use iFrames and actual HTML pages. Make sure you have the iFrame security headers set. If you look at the pages in our website, this uses iFrames and independent pages.

You would have to use an external library like https://stuk.github.io/jszip/

If you give your master API key to all of your users, they will have the same permissions with your database as you do.

1. Yes, but you should generate more keys for each of your users (or at least for each user group, like Player)

2. Yes. (Assuming the API key is used as a session ID)

3. Authorization will allow you to give each user group fine-grained control over what they .read or .write to.

We're going to assume that Google takes care of the deeper security aspects.

Although, this fellow seems to disagree: https://stackoverflow.com/questions/374 ... the-public

I would still make a separate API key for your users though, just to be safe.

You have to add a lot more frames than 8.