Skip to content

Conversation

@tin2tin
Copy link

@tin2tin tin2tin commented Nov 5, 2019

By no means finished work on updating Code Autocomplete... but maybe a start?

if len(getattr(property, "default_array", [])) > 0:
return repr(property.default_array[:])
return repr(getattr(property, "default", None))
return repr(property.default)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can there be properties that don't have the "default" attribute? I don't know anymore.

@JacquesLucke
Copy link
Owner

Thanks for the update. Are you interested in getting commit access to update the addon step by step in a branch?

I hope you know what to do about them - I don't...
@tin2tin
Copy link
Author

tin2tin commented Nov 19, 2019

This add-on is far too complex for me to grasp. I just think it's a shame that Blender users can benefit from all the work gone into it.

I have a small add-on to check for functions which needs an update and I used it to run throught your files one by one. Even though that has solved a lot of the monkey-work of updating elements, it may have caused new errors. The thing you mention above might be one of them.

I've collected all classes in the init file. When I run it, it gives me errors, but I'm not too familiar with multi file add-ons, so I hope you know what to do from here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants