Timeline for Translate all vertices of all selected objects
Current License: CC BY-SA 3.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 15, 2013 at 5:25 | comment | added | mg007 | Well... updated for community demands :/ | |
Jun 15, 2013 at 5:25 | history | edited | mg007 | CC BY-SA 3.0 |
community demand :/
|
Jun 15, 2013 at 4:43 | history | edited | mg007 | CC BY-SA 3.0 |
only_selected and Vector issue
|
Jun 15, 2013 at 4:35 | comment | added | mg007 | I also talked with my friend who's an artist, and I learnt about Blender artists terminology of dealing with selected objects. So I'll update answer to consider only selected objects (and fill the developer-artist gap :P) | |
Jun 15, 2013 at 4:32 | comment | added | mg007 | @ideasman42 Thanks for feedback. Just compared with Vector() solution with timeit, but the total difference is not more than 0.02 sec (for mesh having over 100K vertices, so about .2 microsec per vertex). And I say difference because in some (few) cases this solution is faster (by negligible amount). So I'll keep it as it is and add a comment regarding this. | |
Jun 15, 2013 at 0:43 | comment | added | ideasman42 | Also note, typically you wont want to access all meshes in a blend file, so useful for an example but if you write a tool, use visible/selected objects from the context. | |
Jun 15, 2013 at 0:35 | comment | added | ideasman42 | Suggest to += a Vector() rather then x,y,z - which will be slower because of multiple attribute access and internal update functions. | |
Jun 14, 2013 at 18:22 | comment | added | mg007 | @zeffii yes.. I've already written that in comment. But we can add one more simple for loop in exchange of simplicity... :-) | |
Jun 14, 2013 at 17:13 | comment | added | Alessandro Pezzato | Even if zeffii's solution works, this function solution is more elegant. | |
Jun 14, 2013 at 17:12 | vote | accept | Alessandro Pezzato | ||
Jun 17, 2013 at 7:51 | |||||
Jun 14, 2013 at 17:05 | history | answered | mg007 | CC BY-SA 3.0 |