As a Roblox developer, it is currently too hard to know what properties you’ve changed on instances.
Scenarios where this is helpful:
One instance is behaving differently from one with an expected behavior. You suspect they have some differing property that is doing this, but you’re not sure what. If you could see what was changed, this would be a lot easier.
You want to make UI with scripts (like with Roact), and you make your UI in Studio first to make sure it’s what you want. You then copy over the properties from the UI to your scripts. Without any indication, it’s common to miss a few properties like AutoBackgroundColor and the like. This means in game, your UI will look different than what it does in Studio. Furthermore, figuring out which properties are making it different is not always easy. If there was indication, you would ideally get it right every time (or at least more often).
Prior art:
Firefox’s about:config menu bolds properties you’ve changed.
Changing variables on BYOND atoms in the editor makes them bold.
Changing properties on Unity components makes them bold.
In Unity, bolding shows what you’ve changed since your last save. I’m guessing this is the same for the other two, or they bold what’s been changed since the config page/dialog was opened. This behavior doesn’t seem to solve either of your use cases, as once you publish/save your game, you’re back to square one. This gets even worse in Team Create where the game is constantly being saved.
It would be more feasible if properties were bolded based on what’s been changed from the default properties, but which default? You get different defaults based on whether an instance is inserted from Advanced Objects/white plus, Instance.new, or the ribbon. If it’s shown based on Instance.new, properties will be immediately bolded as soon as you insert objects in Studio. If it’s done based on Advanced Objects/white plus, the bolding won’t help for your Roact use case since you need to know what’s changed from the Instance.new default.
Doesn’t seem like this feature request is possible in a way that solves any use cases.
