Page MenuHome

particle presets
Closed, ResolvedPublic

Description

added a preset functionality for the particle settings, i used a dir(ParticleSettings) to get all the settings and then removed some read-only from the presets list, so im not sure that complies with the coding guideline.

Patch:

Details

Type
Patch

Event Timeline

dan grauer (kromar) raised the priority of this task from to Needs Triage by Developer.
dan grauer (kromar) updated the task description. (Show Details)
dan grauer (kromar) set Type to Patch.

The thing is, particles are gonna to have major refactor, so not sure it worth adding features in the current code.

@Lukas Toenne (lukastoenne), your opinion here?

Sergey Sharybin (sergey) lowered the priority of this task from Needs Triage by Developer to Normal.Sep 12 2014, 10:55 AM

I would rather not add more features to particles. The system is terribly broken and any additional code, even if it's just a python script, will cause more maintenance overhead and delay eventual replacement.

Presets for particles also seem to be slightly redundant: the ParticleSettings are already an ID datablock that can be shared between multiple systems, copied and modified. What would presets bring to the table that can not already be done with a settings datablock?

dan grauer (kromar) added a comment.EditedOct 8 2014, 4:20 PM

we share the same location of the scripts folder over the network for multiple users and there is where the presets become very powerful. as soon as someone creates a preset everybody on the network has it available in his blender, without the need to update a file or link it from a blend file.
correct me if im wrong but i dont think this is possible with a ID datablock

This can be made into an addon quite comfortably, there should be no changes necessary to the C code. So that's what i would suggest as an in-house solution.