Discussion from D11344:

In D11344#290900, @Philipp Oeser (lichtwerk) wrote:

In D11344#290267, @Will (WCN) wrote:

I think this only affects the UI and not the underlying property, right?

As a user, I'm a little bit antsy about the idea of having properties which are still valid in the bpy API but will never be exposed in the GUI. It would open up the possibility for scripts to change file contents in a way that is impossible to discover and undo manually, and could then in turn affect other operations.

For example, the bundled "Copy Attributes" add-on has "Copy Dupli" and "Copy Draw Options" operators. That is able to change the setting on a Camera, which could then in turn affect either another script or some future built-in behaviour that eventually leads to problems later down the line— Causing hours to be wasted on trying to track down an errant setting that is impossible to see unless you specifically print it out by path in a console window.

I get the point, some extra care could be taken to warn if this is set from python on an object that does not really support this (or even prevent setting), not sure though if this is worth it

Is there a precedent for properties that are never exposed in the GUI? I know stuff with multiple modes like rotation values, Empty draw type, some modifiers, etc have properties that are only exposed conditionally.

Well, we have one right above my change: you can change the ob.color on a Camera [which is not in the GUI -- and does not have any effect -- same as bounds for Cameras], is that what you mean?

C.active_object.color = (0.0, 1.0, 0.0, 1.0)

Also applies to D11348 and maybe D11349.

Mind dropping a note there also? (it is just easier to keep track of - since these are separate Diffs we might forget about it otherwise)

In D11348#323653, @Taiseibutsu (Taiseibutsu) wrote:

Should be visible for Text Objects at least, or just one option. Instancing by Vertex is needed to enable font objects.

Hi! Thx letting me know, will fix that