You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should get rid of the assumption that all datablocks want to use a data attribute, and that they should all use _data_setter for that. It's either resctrictive or useless for how groublocks or simply more complex datablocks work.
I think all datablock where it's obvious and intuitive should have easy access through __setitem__ like now, but without forcing an internal api for how to do that. As for more complex stuff: we should probably implement a "smart" setter/getter; maybe:
Particles[2]
should return something like
[position, orientation, property]
The text was updated successfully, but these errors were encountered:
We should get rid of the assumption that all datablocks want to use a
data
attribute, and that they should all use_data_setter
for that. It's either resctrictive or useless for how groublocks or simply more complex datablocks work.I think all datablock where it's obvious and intuitive should have easy access through
__setitem__
like now, but without forcing an internal api for how to do that. As for more complex stuff: we should probably implement a "smart" setter/getter; maybe:should return something like
The text was updated successfully, but these errors were encountered: