Part.Changed(property) returning property as lowercase "size" instead of "Size"

Bug Reports Engine Bugs
1

If you create a new part in the workspace and hook up this event in the command bar:

workspace.Part.Changed:connect(function(property) print(property) end)

and resize the part with the default studio tools, you’ll get something like this in the output:

DraggingV1
Transparency
CFrame
Position
Rotation
size
Size

Notice the second to last item. It says “size” and not “Size”. It should say “Size”. I came across this because I have a plugin that mirrors the properties (Size, transparency, etc) of one part to another, and I kept getting “Use “Size” instead of “size”” in the output, and it turned out the .Changed event I had hooked up to the original part to was returning lowercase “size”. This should be “Size” and not “size”.

2

I think ROBLOX uses “size” instead of “Size” internally. Could be wrong though.

3

Roblox, how dare you be inconsistent… :open_mouth: oh wait, I’m thinking of someone else

4

If that’s part of what’s used internally then it shouldn’t be showing up in what’s used externally.

Also, didn’t ROBLOX used to have it where if you changed the size in the properties window, it wouldn’t change the CFrame of the part and move it up above the closest part? It seems now that was regressed and it now moves up to the top of any parts in the way. Just when setting the size of a part inside a baseplate (no other parts in the map), the output said the CFrame was set 9 times just because I set the size in the properties once. Something isn’t right here.

5

instance.Changed:connect(function (change)
change = string.lower(change)
if change == “size” then
– Do stuff
end
end)
[/code]This way you avoid these sorts of problems. However, this doesn’t mean it should be necessary.

6

Not sure if anyone remembers this, but the difference between properties Size and size used to be… interesting.

Before the Custom FormFactor enum, and when .size was “scriptable,” you could do this:

Part.size = Vector3.new(.1,.1,.1);

And this would accurately size the part to that Vector3 - even bringing the physics with it (as Stravant once said, “choking” the physics engine).