When using the keyboard shortcuts in the event editor to create an event, condition or action, after going through the wizard and pressing enter, when it appears, everything is deselected. This means that you have to click something again to use the keyboard shortcuts again.

My request is for it to work a little more like construct classic does - that after creation, the event, condition or selection is highlighted instead of everything being deselected, so the user can type their way through multiple ACEs without the wizard deselecting everything and having to click each time. With C2's ability to move the selection with the arrow keys, it should work even better.

My second request is that if there is no code in the editor, pressing E creates a new event, or if nothing is selected, pressing E creates a new event at the bottom of the event sheet, again like construct classic did it.

Third, I think it would be a lot better if created conditions and actions appeared underneath the selected condition or action, the same way pressing E creates an event underneath the selected event, rather than at the end of the list.

nilesh I moved your post to the appropriate forum.

I'm not sure of the answer, but I seem to recall R0j0hound's resource plugin being useful for that. http://www.scirra.com/forum/plugin-resource-access_topic39986.html

Keep in mind to use a free font, otherwise distributing the font might not be allowed by the font's licence.

seac This is the wrong place to post that, as it's not about the bug posting process, which this thread is about, and is in the construct classic forum. I assume you're talking about C2, because construct classic already has an else condition.

Ashley has mentioned that else is already on the to do list for C2.

profMobi - Ah well. Thanks for the response!

Yeah, I think it's a lot better to have to manually put in a loop. Please, please put it back to the way it was! I think it's way less confusing than having construct automatically run one, and also gives the user more control about if they want one or not. I'm not even sure how to work around it the way it is. :/

Ashley You fixed it! Thanks again!

amirai.net/bugs/loopswithoutloopsbug.zip

Apparently having an object overlap multiple instances of another object and doing a collision check causes a 'for each object' loop to run even though there's no condition for it.

Happens on chrome, IE, FF. Vista 32 bit.

Yeah, it still works that way. There are some gaming keyboards I've heard of that fix the problem, but most people don't have them.

Yep. Global objects aren't destroyed when switching layouts.

Drat. Oh well, thanks for the info.

Hmm, thanks for the info. I can't play with it myself though because I don't have a device to test it on.

Try it with a thousand bullets. Or make it so it makes more and more of them until the fps dips. Make them invisible too, so the results aren't affected by the rendering speed. The behavior is probably faster, regardless.