What if I did not want the selector to move randomly?

Should I then change the Random Round 0,3 code line?

In that case, you should change

Set XXXX to round(random(0, 3))[/code:10jfkiqt] to [code:10jfkiqt]Set XXXX to XXXX % 3 + 1[/code:10jfkiqt]

What is that "%" between "XXXX" and "3", you might ask ... That is modulo, that is the remainder of dividing. 
In my example, it will divide XXXX by 3 and get what remains:
[ul][li]XXXX = 0, XXXX / 3 = 0, [b]0[/b] remains => XXXX % 3 = [b]0[/b][/li]
[li]XXXX = 1, XXXX / 3 = 0, [b]1[/b] remains => XXXX % 3 = [b]1[/b][/li]
[li]XXXX = 2, XXXX / 3 = 0, [b]2[/b] remains => XXXX % 3 = [b]2[/b][/li]
[li]XXXX = 3, XXXX / 3 = 1, [b]0[/b] remains => XXXX % 3 = [b]0[/b][/li]
[li]XXXX = 4, XXXX / 3 = 1, [b]1[/b] remains => XXXX % 3 = [b]1[/b][/li][/ul]
and so on.

Then, I add + 1 to it, so you get 1, 2, 3 instead of 0, 1, 2.

The modulo operator is useful here to make sure your numbers stay between 1 and 3 instead of constantly going up and up to the moon. :p

If you are going to export it as NW.js (executable file to be run on desktop operating systems), you will have an option when exporting.

Yeah ... Makes sense. Every 1 second, the up arrow key simulation will be pressed – a single press is enough for the player to jump. The same will happen to the left arrow key simulation – it will be pressed only for a short moment, so you cannot see any difference ...

Yeah ... Makes sense. Every 1 second, the up arrow key simulation will be pressed – a single press is enough for the player to jump. The same will happen to the left arrow key simulation – it will be pressed only for a short moment, so you cannot see any difference ...

> oh yea.. also "else" condition wont work

>

'Else' does work, but without seeing your code or an example .capx, how are we to know what you mean?

Please read the Tips for posting so that we can offer better assistance.

Adding "Else" condition next to a trigger one will say "Else is invalid here".

The solution which Pulstar provided and gaelsev showed should work.

It depends on which iFrame plugin you are using. Some may have an option "iFrame -> Set URL". This should do the trick.

If you want to redirect the whole thing, then you might want to use "Browser -> Go To URL".

This bug is problematic, as if you request a post with id 1909769338, it is ok, but if you request 1909769337.999998, you obviously get an error.

I can confirm this bug. Here are my findings:

If I access 2 array datums in the same action (i. e. set text to Array.At(0, 0) & newline & Array.At(0, 1) & newline), then I get this error. If I access them one by one, however, and add some text at the end, then it works normally (according to comments here, I guess it's because then it converts it into a string).

Here's the number I'm having problems with, but I see that some (not all) other numbers cause problems as well: 1909769338

capx: http://www.filedropper.com/c2arraybug

By the way, round() expression doesn't work here.

I get an error (Parse Error) whenever I try to parse some JSON data starting with two tildas in a row (~~). Is that normal?

Example of such data:

{"total": 1380, "posts": [{"text": "~~"}]}[/code:21tu1wb4]

As far as I am aware, Letterbox scale doesn't fill the whole screen. If the device has different aspect ratio (usually they have 16 : 9, but they can also have 4 : 3 or 3 : 2 etc.), then black bars will be shown. I usually use Scale outer and then position the elements correctly, so the game fills the screen.

You may want to check out this tutorial: https://www.scirra.com/tutorials/73/sup ... reen-sizes

Awesome, this can come in handy! I'd also recommend a download link.

I agree, this would be useful.