That seems reasonable explanation.

But I bet Windows uses that order because that order makes sense there. Where Cancel takes priority over OK. As if users changes something in Windows, then best option is to Cancel and clicking OK should not be clicked so easily. Because there, OK and Cancel can have big serious consequences. While in C3, it's just change variable, create project, insert object.

I bet they also have statistic, that shows when users goes to change something in Windows, they Cancel more often then Confirm it.

While in C3, clicking Cancel is opposite effect, you loose all inserted math/values and Browsers offers UNDO / REDO if you even overwrite your stuff, so it makes no sense to protect users for clicking OK. While you cannot redo your stuff which you inserted into some dialog.

I took another look at it, and indeed it possible to keep Default theme nice in dark version.

Fast mockup I tried, comparison to official ones. Even tried Kenyonb one, but it did not look so good.

That's even more then 1 year ago.

Anyway, it just took 4 css properties to change most buttons around. Is all ok now for me.

Official dark theme, seems to be made to look good. As someone who have designed my own theme and while doing so, the official theme problems seemed to come from design patten and workarounds from all cases, which i also faced: event size and order, different events after another, editor size, select focus hover style, reasonable contrast between everything, all which editor has to support and still look good.

To overcome thous problems, editor has to look very simple and with simple style. Or you just add a lot of padding everywhere.

And i think if official theme gets pure dark version, it won't look good. Black and white suits, but other colors get really messy, with no good contrast etc

I told them about this years ago, but they didn't seem to care.

Well then. But if problem has already been pointed out before, there must be a reason and no action has been taken. Then it could be safe to assume, no futher action is taken on default theme in future.

Construct3 has "50+ dialogs " as stated in docs, swapping buttons around for my own use, which will take time. I would need confirmation like that.

You need to write your own shader, to do it correctly. I don't think there is anything simple that can do it currently.

Sometime ago I wrote myself correct hsl changer - to 100% match google color tool hsl changes. I used it on your yellow image to test it.

You would need something similar but with rgb etc swap. For precision, it takes a lot of time to calibrate it corretly. So output color is 100% for example 198,165,76 and not few precisions off. So you should look into it if you wanna get it easily done, and not use multiple sprites for overlay etc.

Saw there are some topics about new feature called scene graph and thought, how I would see it?

Firstly, I think the name scene graph is what timeline is, so i rename the feature now on to Fixset.

So what is Fixset? It's predefine object group with relative coordinate system.

How does it work?

Object group that can be prebuilt and created durning runtime, with all properties it had assigned before and ability to modifie each object seperatly inside group relative system.

1. Build

User can prebuild hierarhy of objects inside layoutview and define object group relative connections by custom imagepoints.

• User can select and drag objects into group
• User can set each object connection points
• User can prebuild object group and define custom properties for each object.
• User can define parent and child objects inside object group

Example image of object group inside Fixset feature. Each object can be predefine with custom properties and relation between other objects. Even body element is child to global Fixset properties, so body can also be destroyed if needed.

2. Use

Fixset object can be created durning preview and keeps all predefined settings from build phase.

• User can create and destroy Fixset object
• User can save and reuse previous Fixset state, or default state
• User can change child object properties: like angle,size while keeping other properties relative to group
• User can change imagepoint connections or swap them between child objects
• User can change parent object properties indepenently from rest of the group, while still keeping other setting relative to global Fixset properties and its childs.
• User can assign parent state to some child object
• User can delete each fixset object seperatly or create them back

Examples:

User can select and rotate child object.

User can redefine parent object to child and then rotate everything else around it.

User can change multiple child object properties same time: position and rotate them, while keeping object still relative to body element

Fixset benefits.

Add easy way to maniplulate group of objects.

Simplifies object group relative handling.

Create and delete predefine object group.

Load and save old object group settings.

This will add things to already big list of things that is nice to have. But anyway:

How hard, if possible and does not have big impact - is to enable mipmap per object basis. This is clearly needed, like a lot of other cool things, but not every object is zoomed and object that need zoom are mostly together with ones that don't need it. Currect case is big middle ground! Maybe per layer basis? Ofc the end benefit might super minimal.