I was sure this was posted on the current suggestions github, but haven't spotted it yet (link it here and I will edit post and add a comment there, or I will post it myself and link it). I know I posted it years back, and could have sworn I saw it again this year!
AND yes, sorry, I know the point of the features suggestions github is for exactly this, but I guess it's random hope after seeing the exciting recent UI changes in Construct 3. No demands here!
Object Icons
Objects, such as Sprites, TiledBG, they auto-generate an icon for themselves - Very helpful visually when scrolling through event sheets.
Other object types, such as JSON, Dictionary, Array, they have the same icon. Not as visually identifiable, or sometimes impossible to identify if you choose to set the Event Sheet UI to hide the object's name partially.
If ANY object type, including Sprites and Families, could have a dedicated "icon" section, two buttons like "Use default icon" and "Edit" which opens the image editor window to let you draw an icon... wow... this would save so many mistakes I continue to make, despite my lengthy time using Construct! Honestly I'd take a pre-defined list of icons at this point.
Why does it matter?
Lets say we have many Array object types: Sure, you are careful when starting off, but when in a deep flow state, and you are working on events that involve 2 or more Arrays, you may unintentionally make mistakes with logic, maybe the name of the object is long, or starts similarly like "jsonUI_Window", "jsonUI_Button".
"get gud, read more", I DO, but Idunno, I comprehend things visually, the very reason I enjoy Event Sheets so much.
Workarounds
I've adapted over the years to make this as smooth as possible, such as renaming objects to be obvious earlier in the object's name (e.g. "jWinUI", "jButUI") although it makes things less organised/tidy, and I still make the same mistakes, especially when all names are shorter and thus looking for 2 or 3 character differences.
I also tried to keep things in less object types, keep things as 1 array with a few instances with an instance var to manage types, but then this has other issues - both practically and using C3's features like find/find all references when there's hundreds of results.
Anyway, yes... Thoughts?