Editor Workflow Suggestions

Hi, Ive been using C3 for a while now and here is my list of most notable suggestions. Apologies if there is already a board for things like this but I couldn't find it. Take it all with a pinch of salt. I will update as I go. Please add yours to the list.

• A colour variable or a colour picker built into the Set Colour action dialogue.
• When you drag external images onto a sub folder in a project they currently go to the root of the Object Types folder. They should stay in the folder you dragged them onto.
• Default sprite size when creating a new sprite should be able to adjust in settings. The current 250 size is pretty heavy for mobile and its easy to forget to change it.
• Add the relevant shortcut keys to all of the menu dropdown items in the editor. For Example"Toggle Bookmark" should read "Toggle Bookmark (F2)"
• When creating a new object it should be created inside the current folder that you have selected in the project view. I am forever dragging objects between the parent folder and sub folders.
• In the Scene graph we should be able to transfer the parents current "opacity" to children.

• A shortcut key for moving an object up/down through the z order. As far as I know there is only a key to either move it to the bottom or top. I know there is the zorder bar but a shortcut key would help.

• Ability to select multiple objects in the project view and add a behaviour to them all at the same time (not just the last one selected)

• Same goes for selecting multiple objects and selecting 'Add to Family' All should go in and not just the last selected

That's all for now :)

Cheers

Was the idea not to review the suggestions in six months intervals?

Even just to give a simple "maybe" or "no" response, which would at least let us know that it's been considered, and encourage more suggestions.

EDIT: I really like a lot those suggestions Grimmy! Especially controlling the defaults.

We get so many ideas, and many of them are complex enough to require a lengthy review to determine feasibility, that merely providing any kind of response would itself be an enormous amount of work. Besides, even minor features can unexpectedly become very complicated. As a small company with limited resources we need to find ways to cut the amount of work we have to do, not increase it with lots of admin work.

Yeah I think pretty much everything has been said about this already. From my experience with it I have seen quite some of the features that I thought to be really useful/important eventually end up in Construct. Though admittedly, it always took a very long time from suggestion to implementation.

I have one specific in mind I first suggested on the old platform in 2017 (without much success/interest) but it got suggested several times by other users down the line, perhaps formulated better. Eventually it was implemented... 1-2 months ago. Just a mere 5 years later. There's 2 suggestions I'm specifically eying right now so I hope I see them come to life in 2027 :)

I'm just joking around a little, Scirra is not obliged to even take suggestions in the first place. I guess it's a good way to get some ideas and the odd "good" suggestion but it's impossible to base the entire development of Construct around it. Also the updates almost always brought something new/useful/exciting to the table, even if it wasn't the feature I was hoping for.

Hi, I didn't want to start any bad feelings with my post, I understand that most if not all will never be implemented, I'm not expecting anything. Just keeping some mental notes for myself if not for anybody else. C3 is excellent! These are not criticisms! But if there is any easy to implement low hanging fruit in there for the team, then great!