1
$\begingroup$

I was wondering if there is a way to hide custom properties we add to objects in our add-ons - to keep them from being displayed on the side (N) panel: enter image description here

Some type of "internal only" option?

As an artist, I've always hated how addons clutter up this area. Especially when we (the user) want to maintain our own custom properties that get exported to game engines and such. It makes a mess. I saw a similar question here Hide custom properties in the UI panel with python, but I believe it was misunderstood.

$\endgroup$
  • 1
    $\begingroup$ Have you considered storing your data on global properties (bpy.props) or in a external file? (a .txt file in the addon folder should do the trick) $\endgroup$ – Tareyes Sep 8 '19 at 21:24
  • $\begingroup$ Would there be a way to store object-specific properties in those? For example, if I have an object reference, can I access the properties that relate to that object specifically? Or would I need to use some type of searching system? $\endgroup$ – Robert Sep 8 '19 at 21:42
  • $\begingroup$ That's the tricky part: if you are willing to use a single custom property (maybe on the scene, which custom properties are less used) to store a dictionary in, you could use that to store a list of the objects' id_data and the name they have in the .txt (for that you can use bpt.props to I guess). This way you still have a custom property, but one is less than 20... If not you could tag all the objects affected by your addon, so you can create a search system only between them based on the name (or even better, based on the name of their mesh, which name doesn't get changed often) $\endgroup$ – Tareyes Sep 8 '19 at 21:59
  • $\begingroup$ A modal timer would be perfect, because you can momentarily store the id_datas in your modal operator and trigger a simple function every minute or whatever that checks if their name have been changed (or you can just place that function in other modal operators if you have them in your addon). $\endgroup$ – Tareyes Sep 8 '19 at 22:08
  • 2
    $\begingroup$ When Developer Extras is disabled, the properties should not show up... so artists won't see them (usually). $\endgroup$ – p2or Sep 10 '19 at 10:49
0
$\begingroup$

p2or: When Developer Extras is disabled, the properties should not show up... so artists won't see them (usually).

Answer by p2or. Leaving this here until he returns and posts this as an answer. To sum it up, there is no reason to hide these properties because they are not shown to users unless Developer Extras is enabled.

| improve this answer | |
$\endgroup$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.