Construct 3 - Irks and Quirks

Now that I´m on vacation and got more time to dev around, I stumbled over some annoyances in C3. I´ll just use this to drop everything I find. I don´t want to post these in either the suggestions or github issue thing, because they are minor and I honestly can´t be bothered to file a complete report (for each?) about. Feel free to expand the list.

Array Editor

• It´s impossible to delete the number 0 out of the array fields. You have to change it to a different number first, then you can delete it. I´d assume 0 is seen as 'empty' but that isn´t exactly true.
• Would be awesome if I could navigate the editor with the arrow keys.

Image Editor

• Two finger zooming is very slow in image editor (on a 4k laptop with touchscreen at least) It seems to go at a fixed maximum speed.
• Trying to set the brush size to e.g. 250 by typing it in the field results in 1250 (then defaults to the maximum of 500) since it doesn´t let me delete everything out of it. One number always has to be present.

Bullet behavior

• Would be great if I could not only set the initial speed, but also the initial angle.

Conditions, Events & Eventsheet

• From C2 I´m used to navigate through most of the Condition and Event creation with keyboard. In C2 pressing 'enter' in this window does the next logical operation (letting me pick the object). In C3 a popup will tell me that I have to pick an object (duh)
  
• When searching through events I get this awesome list of all the events that contain my keyword. Sadly I get no "edit this event" option when I click on it, the closest thing I get is "go to"
• Global constant variables: DOTHEYREALLYHAVETOBEINALLCAPSBECAUSEITHINKITLOOKSUGLY
• When creating (e.g.) a condition for my Object 'zing' I use the search bar to quickly find it between all the Objects. However when I type 'zing' the first shown (and selected) Object will not be 'zing' but 'amazing' because it´s alphabetically ordered. I´d rather have the closest match first though.
  
• If I do this, it would be really neat to either get multiple windows for each selected action or some sort of 'batch edit' where I can edit all selected one after another. Or maybe even both, either way it would save a ton of navigating.
  

Misc

• If I can check for 'If [Sprite] is overlapping [Tiled background/9-patch]' why doesn´t it work the other way around? Is there a particular reason for that?
• Also, if I can check for said overlap, I´d love to at least be able to disable the collision checking on Tiled backgrounds and 9-patches
• When I was deving on the train (with a garbage on-off internet connection) the autosave would constantly ask me to sign in my gdrive again.

When I was deving on the train (with a garbage on-off internet connection) the autosave would constantly ask me to sign in my gdrive again.

hello WackyToaster, go to Settings, Save & Backup and remove the option "Periodically back up active project", I think. (when on the train)

[quote:2n6spwau]hello WackyToaster, go to Settings, Save & Backup and remove the option "Periodically back up active project", I think. (when on the train)

Well, I don´t think disabling autosave/backup is the preferred option here. I mean I could just switch it to local backup I guess. I´d still rather not have to meddle with the settings in this case though.

[quote:22lhck9s]hello WackyToaster, go to Settings, Save & Backup and remove the option "Periodically back up active project", I think. (when on the train)

Well, I don´t think disabling autosave/backup is the preferred option here. I mean I could just switch it to local backup I guess. I´d still rather not have to meddle with the settings in this case though.

I do not disagree on both points with you.

I think bug and request reports must be made if you want to see changes, though.

[quote:3c8x10tk]I think bug and request reports must be made if you want to see changes, though.

Nah, changes and bugfixes must be made if Scirra wants to see money, though.

We´ll see if they fix it, else I´ll go through the slog of creating reports

The reason we prefer using the issue tracker is it keeps everything in one place. This forum post will sink down the pages after a few weeks and end up getting forgotten. If it's on the issue tracker, it can be assigned to the right developer and they'll come back to it when they next have time to review issues.

If you want stuff fixed, then filing an issue on the bug tracker is definitely the way to go...

From a quick look I can tell you the array editor zero thing was definitely a bug, I've fixed it for r76. You can already move around the array editor with the arrow keys, you need to hold ctrl as well though. The gdrive issue is a little more involved, if you file a bug I'll take a look into it soon.

From a quick look I can tell you the array editor zero thing was definitely a bug, I've fixed it for r76.

Great service

Alright alright, I´ll post it in the issue tracker.

[quote:1n9f4q8w]You can already move around the array editor with the arrow keys, you need to hold ctrl as well though.

Why do I have to hold ctrl? Is there a reason for this? :V

The normal function for arrow keys is to move the caret in the text selection, and it would be inconvenient to override that.