Either way is fine, as long as it is clearly stated which indexing is used, to avoid confusion.

That is a damn fine facepalm moment you got there!

You are using 0-indexing? I believe that Construct is trying to streamline 1-indexing.

A little encouragement:

<img src="http://i269.photobucket.com/albums/jj44/JQB5150/awesome.jpg">

You can use a tiled background, set its X offset to whatever you want it to scroll like - if you want it to scroll with the character, set X offset to Character.X*factor (factor being scrolling speed, parallax). If you want it to scroll over time, set X offset to, umm, whatever that system expression for ticks is. To make sure it doesn't overflow, just substract it by tiled background image width whenever it goes over that number.

My mind is blank at the moment and still don't have Construct installed, so hopefully someone else can produce an example.

Or using the global counter works, too. Just remember to reset it to zero after the background is fully looped, otherwise it will overflow in the future.

Instead of adding 1, add 60*timedelta, 60 being scrolling speed you can adjust if you want. Smooth scrolling!

I... I... I want to have your baby!

Construct is AWESOME.

Compare this:

__________________________________

#include <iostream.h>

void main ()

{

count << " It is my first program !!!";

}

__________________________________

................ // for doing the same thing in Construct you just need insert a text box. That's all!!! So... Construct is easy, C++ is difficult.

Besides, the above example wouldn't work! I believe it is cout

That is why Construct is awesome, you have everything at a mouse's reach, no worries about syntax unless you're into expressions.

There are four developers?

Bombastic!

Intriguing...

My combination tends to be ctrl-alt-del.

Problem is that SOMEONE has to write the extensive documentation. Moreover, Construct is still in development; even though it is reaching the final stage, the numerous changes can warrant corrections or even complete rewrites. So it kind of makes sense to wait until the 1.0 RC before cranking the proper documentation out.

Of course, the other theory is that we are too lazy.