Aphrodite

Of course I understand the benefits of visual representation, I never meant that C2 had to have a non visual method of object creation and parameterization. I think that having created an object and set it's initial parameters of that type should be enough, since it exists as a class (?) within the Project. I think of the unity's workflow, where you create your object(s), make them a prefab and then delete them from the scene if you wish. At any time they are accessible thru scripting. In Construct this limitation some times can be little confusing. At least to me

I understand what you're saying. I trouble's me too, since I know nothing about programming and software development, I don't really get why does an object have to exist somewhere on a layout. Why it's existence on the Project's "pool" isn't enough...? It's confusing but I am sure there has to be a solid reason behind Scirra's design decision.

With the Canvas Plugin.

https://www.scirra.com/forum/viewtopic.php?f=153&t=64239

You have to do some reading on the topic though, it's not a straight forward plugin like scroll-to or something...

In order to scroll, your layout has to be bigger than your window size. If they have the same dimensions, then you will see the whole layout at once, so there will be nowhere to scroll to.

An other option will be to set the "Unbound scrolling" to "yes" in the layout properties, but that's more of a game design option, not to "fix" the scrolling issue.

I believe that if you have a placeholder layout for your objects, you don't have to populate your current layout with the "Spawner" object. So, you can create it with events at run time and you should be ok.

An other thing you could do is to put an "on layout start" event and destroy both the "Spawner" and the "spawned" objects out side of the layout.

If applied to the Enemy object, Enemy.Y = self.Y

In some programing languages I believe is the "this" keyword.

Tom

Can you please give your insight in relation to this problem?

I kinda went overboard choosing the top tutorial, took me 4 days to complete and, as it is now is hard and confusing to read in Greek, it's somewhat a waste of effort

No pressure, if it's something hard just let me know!

You are welcome!

1) Create a global variable. Lets name it "TouchTime" (without the quotes)

2) Create an event and add the "Is in touch" condition

3) Create an action and choose "system", "Add to" and select the "TouchTime" variable.

4) On the "Value" field, input "60 *dt" (without the quotes)

5) Create an other event an add the "Compare variable" condition (under system).

6) Set the comparison for the "TouchTime" variable to be grater or equal to 120.

You are ready to create your action.

You need to reset the "TouchTime" variable every time you lift your finger though. Create an other event:

1) Put the "on any touch end" condition.

2) As an action choose the "set value" (under system) and input "0" (without the quotes)

Done!

You can also put the enemies into an "Enemies" family and pick them randomly either with the "pick random instance" expression or using the the "pick by evaluate" expression and a Family variable.

See attached file.

Welcome to the "no proper way to do masking" land

10) I think that the layout properties and the project properties should be somehow combined into a single panel. I understand that most of us are probably already used to it, but having to click into a small "view" link to access similar in function properties is strange and, most importantly, having them separately as they are now, is confusing to new users that haven't yet realized the difference between "Window" and "Layout" size, or where did the "effects" link for the layout went after clicking the "view" link and how to get it back...

I know that I was frustrated at first and had found it very disorientating. I am still bothered by the workflow, especially if I am in the Event Sheet and have an object selected. To access the project properties, I am forced to toggle back to the layout view, click on an empty space, then click the little "view" link. At least I know what I have to do now, I am not lost in the process.