Construct 0.98.8 released (stable)

That doesn't really make logical sense; if I have a global online object reading events from global objects, and I don't want it to in one layout, why should it have to? What about a global sprite? Where will it spawn in layouts it isn't placed?

I think it should need to be placed in every layout it'll be used in.

Indeed, I have a couple global objects on the first layout and I can access them anywhere.

I meant event sheets like Deadeye said. Global objects are accessible via events in any event sheet in the application, and global objects are created when their layout is visited for the first time. So if you have a global object copied and pasted through layouts 1, 2 and 3, and you keep using 'next layout', by the 3rd layout you have 3 instances. However, global objects on the first layout are always created when you 'run layout' in Construct.

No, that's not right... you should only need one global object on one layout, then it should appear everywhere...

Yeah, I was gonna say... that seems to be how it's working for me.

Just lemme clear this up, it makes sense now.

I thought if I set an object to global that it'll be loaded in globally whenever we start the runtime.

So I have a couple of layouts and created a new title screen, where I can let people set options, like full-screen, moBlur, save / load, etc.

I put that title screen on top of the level 1 layout. So the KeyboardMouse object was still on level 1, I just thought because it's set to global it'll be loaded anyway.

It didn't. Now I've cut and pasted the audio and keyboard events to the title screen layout and - boom - it works.

Not sure if that's the perfect way though. Wouldn't it make more sense to load the objects that are set to global to load them in any layout?

You only need one global mouse&keyboard, just put it onto the first layout and you're set for the rest of game.

global objects never show in new layouts that i create. i can still use them for new events but there is nothing in the objects window.

For non-layout objects, you don't really need them in the layout. Events are where they are exclusively used. For layout objects (sprite, tiled background), they will be there even if you cannot select them in a different layout. You can reposition them with events (on Start of layout, for example). If you want to change them, go back to their layout and edit them there.

There is NO need to copy global objects; it just creates multiple instances that conflict each other.

For non-layout objects, you don't really need them in the layout. Events are where they are exclusively used. For layout objects (sprite, tiled background), they will be there even if you cannot select them in a different layout. You can reposition them with events (on Start of layout, for example). If you want to change them, go back to their layout and edit them there.

There is NO need to copy global objects; it just creates multiple instances that conflict each other.

sorry, i meant to say that when i make an object global it does not show up in the object window of new layouts. i realize that their is no need to have the keyboard input show up on the objects window.

It is not meant to appear on object bar of another layout, because it belongs to the layout it was created on. If you have to edit it, go to its layout. If you want to move it around or change it in another layout, you can use events to do so.

I've uploaded an example:

P.S.: Perhaps it would make sense to have a list of global objects somewhere.

It is not meant to appear on object bar of another layout, because it belongs to the layout it was created on. If you have to edit it, go to its layout. If you want to move it around or change it in another layout, you can use events to do so.

I've uploaded an example:

P.S.: Perhaps it would make sense to have a list of global objects somewhere.

so it is intentionally like this. it would be much better if I could place the objects like i would in the layout it was created in. using events to place objects does not seam feasible to me. i have one project were there are a lot of instances of one object that need to be placed specifically. it would drive me crazy trying to place potentially a hundred instances of an object with events. and that is just one layout. duplicating from layout to layout just seams the only way.

If you manually place the object in another layout, it will change position in all other layouts too... global objects work like that.

Instead of trying to drag stuff around, consider using "placeholders", small sprites that you make invisible on startup and only serve as a starting position for that layout. On start of layout just tell the global objects to set position to their respective "placeholders". So to build levels you just copy those placeholders and move them around as you see fit on layout editor.

I love this build so very much.

I might be imagining things, but wasn't the picture editor more stable before? I've only used Construct for 10 minutes now and already got 4 crashes because that freaking thing is so unstable.

I just need to double click a character that's already in my layout, flip the sprite, exit = crash.

Often the same thing happens with the animation tab - I click one animation frame, delete it = crash.

Etc. - That's the most annoying part of Construct. The crashes using the Picture Editor / Animations are really bleh.

I have an issue with arrays.

I set array entry 1,1 to 5. Whenever I try to get the value of 1,1 it returns empty. How can I solve this?