Make Object Property Values Selectable

[lightcube]

Situation: I wanted to get the height/width of an object. Simple: Open the object properties. Now I wanted to copy the values to use in another object properties. Problem (Not so simple): The values in the Object Information field are not selectable (except the Name field). This means you cannot copy the data with CTR+C. Instead you have to remember the values. And because the object properties are Modal, you cannot select another object in the scene to enter the data into--meaning you have to type the data into a separate text editor, write it down, or remember the values (which is not often easy and made more difficult by the fact that you may need to remember multiple values).

I propose making the values selectable so that you can use the data more accessibly. 

Also see this suggestion to Make Object Properties Non Modal and dockable.

[Kranos_Orphydian]

yeah, too bad this wasnt suggested way more earlier

[rene_alex]

You can copy and paste that data in the Object track in the curve editor and paste it to any other object keeping the Property Values of the parametric object, even making instances if you want. This is doable since R1.
Also, you can convert any object into another this way too, for example you can right click and copy the Object track of a point helper and paste it to an animated box primitive and "convert" it into a point helper with the same parameters and the animation of the replaced box.
I use this all the time while rigging.
http://help.autodesk.com/view/3DSMAX/2020/ENU/?guid=GUID-2CB79D65-606B-43BB-9C25-3A64E6386563

[lightcube]

@rene_alex  I think you misunderstand my request 🙂 I'm not implying that you cannot access properties of an object and use them elsewhere via methods like copying/instancing controllers, tracks, wiring, etc. All I'm focused on here is the actual Object Properties dialog which includes an array of data that you might use that isn't available in any one spot elsewhere in Max. Among those properties are derived properties like the Dimensions which (for most object types) are derived values rather than actual baseobject properties. Although some objects like a Box primitive have a "height" parameter that you could utilize as the Z value of height, others like an Editable Poly or most others have no height property and you need to either measure the object, do some math with the Min/Max properties or get from the Object Properties floater. Selecting/Copying this data from the floater is really all I'm interested here.

[rene_alex]

OK, I get you wrong then, You mean the dimensions in world space like height, volume, area, etc. (I could add velocity, direction, position) The ability to use that data to drive others parameters. Right?

If is that; yeah that is not in the UI, you got to write some tool to get max to give you that, You can expose some data with the expose transform helper but the access you ask is less convoluted more streamlined. This script gives some of that data but it only shows it (you can copy and paste) you cannot use it to drive other stuff.

[lightcube]

@rene_alex I am certainly aware that these things can be scripted 🙂 I am just asking that the current Object Properties dialog is more useful to the user without need of an extra toolset. I'm not even asking for the data to be used to drive other data... I'm just talking about the floater UI itself.

[rene_alex]

Oh okey dokey!