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
This is a good pattern - and probably can be used at various places. Would it make sense to factor this out into utility functions say:
template T bool GroupAddElement( vector<Ref > group, Ref elem)
template T bool GroupRemoveElement( vector<Ref > group, Ref elem)
template T bool GroupReplaceElement( vector<Ref > group, Ref old, Ref new)
Yes, I pushed a few diffs with these group-related interfaces. I probably have even some more just here in the code. I use it extensively to substitute nodes by new ones in NIFopt.
You still need to add it to each class though, as the group is private.
Of course. We also need to pass the count so it can be updated.
The text was updated successfully, but these errors were encountered:
Opens up access to the shape-collection.
https://www.dropbox.com/s/538k841388hopt9/NiBoneLODController.cpp.diff?dl=0
https://www.dropbox.com/s/f9uk6zpyzpjoi3j/NiBoneLODController.h.diff?dl=0
This is a good pattern - and probably can be used at various places. Would it make sense to factor this out into utility functions say:
template T bool GroupAddElement( vector<Ref > group, Ref elem)
template T bool GroupRemoveElement( vector<Ref > group, Ref elem)
template T bool GroupReplaceElement( vector<Ref > group, Ref old, Ref new)
Yes, I pushed a few diffs with these group-related interfaces. I probably have even some more just here in the code. I use it extensively to substitute nodes by new ones in NIFopt.
You still need to add it to each class though, as the group is private.
Of course. We also need to pass the count so it can be updated.
The text was updated successfully, but these errors were encountered: