2009-11-21 21:39:20 +00:00
|
|
|
# ##### BEGIN GPL LICENSE BLOCK #####
|
|
|
|
#
|
|
|
|
# This program is free software; you can redistribute it and/or
|
|
|
|
# modify it under the terms of the GNU General Public License
|
|
|
|
# as published by the Free Software Foundation; either version 2
|
|
|
|
# of the License, or (at your option) any later version.
|
2009-11-28 23:37:56 +00:00
|
|
|
#
|
2009-11-21 21:39:20 +00:00
|
|
|
# This program is distributed in the hope that it will be useful,
|
|
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
# GNU General Public License for more details.
|
2009-11-28 23:37:56 +00:00
|
|
|
#
|
2009-11-21 21:39:20 +00:00
|
|
|
# You should have received a copy of the GNU General Public License
|
|
|
|
# along with this program; if not, write to the Free Software Foundation,
|
2010-02-12 13:34:04 +00:00
|
|
|
# Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
|
2009-11-21 21:39:20 +00:00
|
|
|
#
|
|
|
|
# ##### END GPL LICENSE BLOCK #####
|
|
|
|
|
2011-07-25 06:40:16 +00:00
|
|
|
# <pep8-80 compliant>
|
2009-12-13 14:38:30 +00:00
|
|
|
|
2009-11-21 21:39:20 +00:00
|
|
|
import bpy
|
2011-08-12 06:57:00 +00:00
|
|
|
from bpy.types import Menu, Operator
|
2012-03-21 22:29:49 +00:00
|
|
|
from bpy.props import StringProperty, BoolProperty
|
2009-12-13 14:38:30 +00:00
|
|
|
|
2012-03-24 07:36:32 +00:00
|
|
|
|
2010-08-02 02:55:12 +00:00
|
|
|
class AddPresetBase():
|
2009-11-22 13:15:21 +00:00
|
|
|
'''Base preset class, only for subclassing
|
2009-11-28 23:37:56 +00:00
|
|
|
subclasses must define
|
2009-11-22 13:15:21 +00:00
|
|
|
- preset_values
|
2009-11-27 18:55:59 +00:00
|
|
|
- preset_subdir '''
|
2010-07-13 23:51:21 +00:00
|
|
|
# bl_idname = "script.preset_base_add"
|
|
|
|
# bl_label = "Add a Python Preset"
|
2011-01-01 07:20:34 +00:00
|
|
|
bl_options = {'REGISTER'} # only because invoke_props_popup requires.
|
2009-11-22 13:15:21 +00:00
|
|
|
|
2012-03-21 22:29:49 +00:00
|
|
|
name = StringProperty(
|
2011-07-25 06:40:16 +00:00
|
|
|
name="Name",
|
|
|
|
description="Name of the preset, used to make the path name",
|
|
|
|
maxlen=64,
|
2012-02-09 13:02:22 +00:00
|
|
|
options={'SKIP_SAVE'},
|
2011-07-25 06:40:16 +00:00
|
|
|
)
|
2012-03-21 22:29:49 +00:00
|
|
|
remove_active = BoolProperty(
|
2011-07-25 06:40:16 +00:00
|
|
|
default=False,
|
2012-02-09 13:02:22 +00:00
|
|
|
options={'HIDDEN', 'SKIP_SAVE'},
|
2011-07-25 06:40:16 +00:00
|
|
|
)
|
2009-11-28 23:37:56 +00:00
|
|
|
|
2010-09-14 16:45:24 +00:00
|
|
|
@staticmethod
|
|
|
|
def as_filename(name): # could reuse for other presets
|
|
|
|
for char in " !@#$%^&*(){}:\";'[]<>,.\\/?":
|
2010-09-14 04:58:25 +00:00
|
|
|
name = name.replace(char, '_')
|
|
|
|
return name.lower().strip()
|
2009-11-22 13:15:21 +00:00
|
|
|
|
|
|
|
def execute(self, context):
|
2010-09-14 04:58:25 +00:00
|
|
|
import os
|
2011-01-01 07:20:34 +00:00
|
|
|
|
2010-09-14 16:45:24 +00:00
|
|
|
if hasattr(self, "pre_cb"):
|
|
|
|
self.pre_cb(context)
|
2011-01-01 07:20:34 +00:00
|
|
|
|
2010-09-14 04:58:25 +00:00
|
|
|
preset_menu_class = getattr(bpy.types, self.preset_menu)
|
|
|
|
|
2012-01-10 16:20:01 +00:00
|
|
|
is_xml = getattr(preset_menu_class, "preset_type", None) == 'XML'
|
|
|
|
|
|
|
|
if is_xml:
|
|
|
|
ext = ".xml"
|
|
|
|
else:
|
|
|
|
ext = ".py"
|
|
|
|
|
2011-01-01 07:20:34 +00:00
|
|
|
if not self.remove_active:
|
2011-05-02 17:29:30 +00:00
|
|
|
name = self.name.strip()
|
|
|
|
if not name:
|
2010-09-14 04:58:25 +00:00
|
|
|
return {'FINISHED'}
|
|
|
|
|
2011-05-02 17:29:30 +00:00
|
|
|
filename = self.as_filename(name)
|
2010-11-01 21:07:25 +00:00
|
|
|
|
2011-07-25 06:40:16 +00:00
|
|
|
target_path = os.path.join("presets", self.preset_subdir)
|
|
|
|
target_path = bpy.utils.user_resource('SCRIPTS',
|
|
|
|
target_path,
|
|
|
|
create=True)
|
2010-12-18 07:22:52 +00:00
|
|
|
|
|
|
|
if not target_path:
|
|
|
|
self.report({'WARNING'}, "Failed to create presets path")
|
|
|
|
return {'CANCELLED'}
|
2010-09-14 04:58:25 +00:00
|
|
|
|
2012-01-10 16:20:01 +00:00
|
|
|
filepath = os.path.join(target_path, filename) + ext
|
2011-01-01 07:20:34 +00:00
|
|
|
|
2010-09-14 16:45:24 +00:00
|
|
|
if hasattr(self, "add"):
|
|
|
|
self.add(context, filepath)
|
2010-09-14 04:58:25 +00:00
|
|
|
else:
|
2011-12-30 08:39:40 +00:00
|
|
|
print("Writing Preset: %r" % filepath)
|
2010-10-06 18:51:07 +00:00
|
|
|
|
2012-01-10 16:20:01 +00:00
|
|
|
if is_xml:
|
|
|
|
import rna_xml
|
|
|
|
rna_xml.xml_file_write(context,
|
|
|
|
filepath,
|
|
|
|
preset_menu_class.preset_xml_map)
|
|
|
|
else:
|
|
|
|
file_preset = open(filepath, 'w')
|
|
|
|
file_preset.write("import bpy\n")
|
|
|
|
|
|
|
|
if hasattr(self, "preset_defines"):
|
|
|
|
for rna_path in self.preset_defines:
|
|
|
|
exec(rna_path)
|
|
|
|
file_preset.write("%s\n" % rna_path)
|
|
|
|
file_preset.write("\n")
|
|
|
|
|
|
|
|
for rna_path in self.preset_values:
|
|
|
|
value = eval(rna_path)
|
|
|
|
# convert thin wrapped sequences
|
|
|
|
# to simple lists to repr()
|
|
|
|
try:
|
|
|
|
value = value[:]
|
|
|
|
except:
|
|
|
|
pass
|
|
|
|
|
|
|
|
file_preset.write("%s = %r\n" % (rna_path, value))
|
|
|
|
|
|
|
|
file_preset.close()
|
2010-11-01 21:07:25 +00:00
|
|
|
|
|
|
|
preset_menu_class.bl_label = bpy.path.display_name(filename)
|
2009-11-22 13:15:21 +00:00
|
|
|
|
2010-09-14 04:58:25 +00:00
|
|
|
else:
|
|
|
|
preset_active = preset_menu_class.bl_label
|
2009-11-22 13:15:21 +00:00
|
|
|
|
2010-09-14 04:58:25 +00:00
|
|
|
# fairly sloppy but convenient.
|
2012-01-10 16:20:01 +00:00
|
|
|
filepath = bpy.utils.preset_find(preset_active,
|
|
|
|
self.preset_subdir,
|
|
|
|
ext=ext)
|
2010-09-14 16:45:24 +00:00
|
|
|
|
2010-09-14 04:58:25 +00:00
|
|
|
if not filepath:
|
2011-07-25 06:40:16 +00:00
|
|
|
filepath = bpy.utils.preset_find(preset_active,
|
|
|
|
self.preset_subdir,
|
2012-01-10 16:20:01 +00:00
|
|
|
display_name=True,
|
|
|
|
ext=ext)
|
2009-11-22 13:15:21 +00:00
|
|
|
|
2010-09-14 04:58:25 +00:00
|
|
|
if not filepath:
|
|
|
|
return {'CANCELLED'}
|
2009-11-28 23:37:56 +00:00
|
|
|
|
2010-09-14 16:45:24 +00:00
|
|
|
if hasattr(self, "remove"):
|
|
|
|
self.remove(context, filepath)
|
|
|
|
else:
|
|
|
|
try:
|
|
|
|
os.remove(filepath)
|
|
|
|
except:
|
|
|
|
import traceback
|
|
|
|
traceback.print_exc()
|
2009-11-22 13:15:21 +00:00
|
|
|
|
2010-09-14 04:58:25 +00:00
|
|
|
# XXX, stupid!
|
2010-09-14 16:45:24 +00:00
|
|
|
preset_menu_class.bl_label = "Presets"
|
|
|
|
|
|
|
|
if hasattr(self, "post_cb"):
|
|
|
|
self.post_cb(context)
|
2009-11-22 13:15:21 +00:00
|
|
|
|
2009-12-24 19:50:43 +00:00
|
|
|
return {'FINISHED'}
|
2009-11-22 13:15:21 +00:00
|
|
|
|
2010-11-01 21:07:25 +00:00
|
|
|
def check(self, context):
|
2011-05-02 17:29:30 +00:00
|
|
|
self.name = self.as_filename(self.name.strip())
|
2010-11-01 21:07:25 +00:00
|
|
|
|
2009-11-22 13:15:21 +00:00
|
|
|
def invoke(self, context, event):
|
2010-09-14 04:58:25 +00:00
|
|
|
if not self.remove_active:
|
|
|
|
wm = context.window_manager
|
2010-11-01 21:07:25 +00:00
|
|
|
return wm.invoke_props_dialog(self)
|
2010-09-14 04:58:25 +00:00
|
|
|
else:
|
|
|
|
return self.execute(context)
|
2009-11-21 23:55:14 +00:00
|
|
|
|
|
|
|
|
2011-08-12 06:57:00 +00:00
|
|
|
class ExecutePreset(Operator):
|
2011-10-20 07:56:04 +00:00
|
|
|
'''Execute a preset'''
|
* Interaction Presets
This adds a new presets menu in the splash screen and the Input section of
User Preferences to choose a preset interaction style, consisting of key configurations
and also other user preferences such as select mouse button, view rotation style, etc.
Currently, just 'Blender' and 'Maya' presets are included, hopefully we can have more
presets contributed (and maintained!) by the community.
It's best to keep these presets minimal to avoid too many key conflicts. In the Maya one
I changed the view manipulation key/mouse combos and also the transform
manipulator keys, not much more than that.
To save an interaction preset, open the user preferences Input section, and press the
[ + ] button next to the presets menu. It will save out a .py file containing any edited key
maps and navigation preferences to the presets/interaction folder in your scripts folder.
---
Part of this commit changes the way that key maps are exported/displayed in
preferences - now partial key configs are allowed. Previously it would export/import the
entire key configuration, regardless of whether individual key maps were edited or not
(which would make them more susceptible to conflicts in unexpected areas).
(note, in blender terminology, a key map is a category of key items, such as
'Object Mode' or 'View 2d'.)
Now, the export and the UI display work in a similar way to how key maps are
processed internally - Locally edited key maps (after pressing the 'Edit' button) are
processed first, falling back to other key maps in the current key config, and then falling
back to the default key config. So it's possible for a key config to only include a few
key maps, and the rest just gets pulled from the default key config. The preferences
UI display works like this too behind the scenes in deciding what to show users,
however using it is just like it was before, the complexity is hidden.
2010-04-14 06:27:50 +00:00
|
|
|
bl_idname = "script.execute_preset"
|
|
|
|
bl_label = "Execute a Python Preset"
|
|
|
|
|
2012-03-21 22:29:49 +00:00
|
|
|
filepath = StringProperty(
|
|
|
|
subtype='FILE_PATH',
|
2011-07-25 06:40:16 +00:00
|
|
|
)
|
2012-03-21 22:29:49 +00:00
|
|
|
menu_idname = StringProperty(
|
2011-07-25 06:40:16 +00:00
|
|
|
name="Menu ID Name",
|
|
|
|
description="ID name of the menu this was called from",
|
|
|
|
)
|
* Interaction Presets
This adds a new presets menu in the splash screen and the Input section of
User Preferences to choose a preset interaction style, consisting of key configurations
and also other user preferences such as select mouse button, view rotation style, etc.
Currently, just 'Blender' and 'Maya' presets are included, hopefully we can have more
presets contributed (and maintained!) by the community.
It's best to keep these presets minimal to avoid too many key conflicts. In the Maya one
I changed the view manipulation key/mouse combos and also the transform
manipulator keys, not much more than that.
To save an interaction preset, open the user preferences Input section, and press the
[ + ] button next to the presets menu. It will save out a .py file containing any edited key
maps and navigation preferences to the presets/interaction folder in your scripts folder.
---
Part of this commit changes the way that key maps are exported/displayed in
preferences - now partial key configs are allowed. Previously it would export/import the
entire key configuration, regardless of whether individual key maps were edited or not
(which would make them more susceptible to conflicts in unexpected areas).
(note, in blender terminology, a key map is a category of key items, such as
'Object Mode' or 'View 2d'.)
Now, the export and the UI display work in a similar way to how key maps are
processed internally - Locally edited key maps (after pressing the 'Edit' button) are
processed first, falling back to other key maps in the current key config, and then falling
back to the default key config. So it's possible for a key config to only include a few
key maps, and the rest just gets pulled from the default key config. The preferences
UI display works like this too behind the scenes in deciding what to show users,
however using it is just like it was before, the complexity is hidden.
2010-04-14 06:27:50 +00:00
|
|
|
|
|
|
|
def execute(self, context):
|
2012-01-10 15:08:12 +00:00
|
|
|
from os.path import basename, splitext
|
2010-09-14 04:58:25 +00:00
|
|
|
filepath = self.filepath
|
|
|
|
|
* Interaction Presets
This adds a new presets menu in the splash screen and the Input section of
User Preferences to choose a preset interaction style, consisting of key configurations
and also other user preferences such as select mouse button, view rotation style, etc.
Currently, just 'Blender' and 'Maya' presets are included, hopefully we can have more
presets contributed (and maintained!) by the community.
It's best to keep these presets minimal to avoid too many key conflicts. In the Maya one
I changed the view manipulation key/mouse combos and also the transform
manipulator keys, not much more than that.
To save an interaction preset, open the user preferences Input section, and press the
[ + ] button next to the presets menu. It will save out a .py file containing any edited key
maps and navigation preferences to the presets/interaction folder in your scripts folder.
---
Part of this commit changes the way that key maps are exported/displayed in
preferences - now partial key configs are allowed. Previously it would export/import the
entire key configuration, regardless of whether individual key maps were edited or not
(which would make them more susceptible to conflicts in unexpected areas).
(note, in blender terminology, a key map is a category of key items, such as
'Object Mode' or 'View 2d'.)
Now, the export and the UI display work in a similar way to how key maps are
processed internally - Locally edited key maps (after pressing the 'Edit' button) are
processed first, falling back to other key maps in the current key config, and then falling
back to the default key config. So it's possible for a key config to only include a few
key maps, and the rest just gets pulled from the default key config. The preferences
UI display works like this too behind the scenes in deciding what to show users,
however using it is just like it was before, the complexity is hidden.
2010-04-14 06:27:50 +00:00
|
|
|
# change the menu title to the most recently chosen option
|
2010-09-09 18:03:57 +00:00
|
|
|
preset_class = getattr(bpy.types, self.menu_idname)
|
2010-09-14 04:58:25 +00:00
|
|
|
preset_class.bl_label = bpy.path.display_name(basename(filepath))
|
2010-04-17 19:05:53 +00:00
|
|
|
|
2012-01-10 15:08:12 +00:00
|
|
|
ext = splitext(filepath)[1].lower()
|
|
|
|
|
* Interaction Presets
This adds a new presets menu in the splash screen and the Input section of
User Preferences to choose a preset interaction style, consisting of key configurations
and also other user preferences such as select mouse button, view rotation style, etc.
Currently, just 'Blender' and 'Maya' presets are included, hopefully we can have more
presets contributed (and maintained!) by the community.
It's best to keep these presets minimal to avoid too many key conflicts. In the Maya one
I changed the view manipulation key/mouse combos and also the transform
manipulator keys, not much more than that.
To save an interaction preset, open the user preferences Input section, and press the
[ + ] button next to the presets menu. It will save out a .py file containing any edited key
maps and navigation preferences to the presets/interaction folder in your scripts folder.
---
Part of this commit changes the way that key maps are exported/displayed in
preferences - now partial key configs are allowed. Previously it would export/import the
entire key configuration, regardless of whether individual key maps were edited or not
(which would make them more susceptible to conflicts in unexpected areas).
(note, in blender terminology, a key map is a category of key items, such as
'Object Mode' or 'View 2d'.)
Now, the export and the UI display work in a similar way to how key maps are
processed internally - Locally edited key maps (after pressing the 'Edit' button) are
processed first, falling back to other key maps in the current key config, and then falling
back to the default key config. So it's possible for a key config to only include a few
key maps, and the rest just gets pulled from the default key config. The preferences
UI display works like this too behind the scenes in deciding what to show users,
however using it is just like it was before, the complexity is hidden.
2010-04-14 06:27:50 +00:00
|
|
|
# execute the preset using script.python_file_run
|
2012-01-10 15:08:12 +00:00
|
|
|
if ext == ".py":
|
|
|
|
bpy.ops.script.python_file_run(filepath=filepath)
|
|
|
|
elif ext == ".xml":
|
|
|
|
import rna_xml
|
|
|
|
rna_xml.xml_file_run(context,
|
|
|
|
filepath,
|
|
|
|
preset_class.preset_xml_map)
|
|
|
|
else:
|
|
|
|
self.report({'ERROR'}, "unknown filetype: %r" % ext)
|
2012-02-11 15:49:25 +00:00
|
|
|
return {'CANCELLED'}
|
2012-01-10 15:08:12 +00:00
|
|
|
|
* Interaction Presets
This adds a new presets menu in the splash screen and the Input section of
User Preferences to choose a preset interaction style, consisting of key configurations
and also other user preferences such as select mouse button, view rotation style, etc.
Currently, just 'Blender' and 'Maya' presets are included, hopefully we can have more
presets contributed (and maintained!) by the community.
It's best to keep these presets minimal to avoid too many key conflicts. In the Maya one
I changed the view manipulation key/mouse combos and also the transform
manipulator keys, not much more than that.
To save an interaction preset, open the user preferences Input section, and press the
[ + ] button next to the presets menu. It will save out a .py file containing any edited key
maps and navigation preferences to the presets/interaction folder in your scripts folder.
---
Part of this commit changes the way that key maps are exported/displayed in
preferences - now partial key configs are allowed. Previously it would export/import the
entire key configuration, regardless of whether individual key maps were edited or not
(which would make them more susceptible to conflicts in unexpected areas).
(note, in blender terminology, a key map is a category of key items, such as
'Object Mode' or 'View 2d'.)
Now, the export and the UI display work in a similar way to how key maps are
processed internally - Locally edited key maps (after pressing the 'Edit' button) are
processed first, falling back to other key maps in the current key config, and then falling
back to the default key config. So it's possible for a key config to only include a few
key maps, and the rest just gets pulled from the default key config. The preferences
UI display works like this too behind the scenes in deciding what to show users,
however using it is just like it was before, the complexity is hidden.
2010-04-14 06:27:50 +00:00
|
|
|
return {'FINISHED'}
|
|
|
|
|
|
|
|
|
2011-08-12 06:57:00 +00:00
|
|
|
class AddPresetRender(AddPresetBase, Operator):
|
2010-02-10 22:18:00 +00:00
|
|
|
'''Add a Render Preset'''
|
2009-11-21 21:39:20 +00:00
|
|
|
bl_idname = "render.preset_add"
|
|
|
|
bl_label = "Add Render Preset"
|
2010-09-14 04:58:25 +00:00
|
|
|
preset_menu = "RENDER_MT_presets"
|
2009-11-21 23:55:14 +00:00
|
|
|
|
2010-12-20 23:26:29 +00:00
|
|
|
preset_defines = [
|
|
|
|
"scene = bpy.context.scene"
|
|
|
|
]
|
|
|
|
|
2009-11-21 23:55:14 +00:00
|
|
|
preset_values = [
|
2010-12-20 23:26:29 +00:00
|
|
|
"scene.render.field_order",
|
|
|
|
"scene.render.fps",
|
|
|
|
"scene.render.fps_base",
|
|
|
|
"scene.render.pixel_aspect_x",
|
|
|
|
"scene.render.pixel_aspect_y",
|
|
|
|
"scene.render.resolution_percentage",
|
|
|
|
"scene.render.resolution_x",
|
|
|
|
"scene.render.resolution_y",
|
|
|
|
"scene.render.use_fields",
|
|
|
|
"scene.render.use_fields_still",
|
2009-11-21 21:39:20 +00:00
|
|
|
]
|
|
|
|
|
2009-11-22 13:15:21 +00:00
|
|
|
preset_subdir = "render"
|
2009-11-21 23:55:14 +00:00
|
|
|
|
|
|
|
|
2011-11-04 14:36:06 +00:00
|
|
|
class AddPresetCamera(AddPresetBase, Operator):
|
|
|
|
'''Add a Camera Preset'''
|
|
|
|
bl_idname = "camera.preset_add"
|
|
|
|
bl_label = "Add Camera Preset"
|
|
|
|
preset_menu = "CAMERA_MT_presets"
|
|
|
|
|
|
|
|
preset_defines = [
|
|
|
|
"cam = bpy.context.object.data"
|
|
|
|
]
|
|
|
|
|
|
|
|
preset_values = [
|
|
|
|
"cam.sensor_width",
|
|
|
|
"cam.sensor_height",
|
|
|
|
"cam.sensor_fit"
|
|
|
|
]
|
|
|
|
|
|
|
|
preset_subdir = "camera"
|
|
|
|
|
|
|
|
|
2011-08-12 06:57:00 +00:00
|
|
|
class AddPresetSSS(AddPresetBase, Operator):
|
2010-02-10 22:18:00 +00:00
|
|
|
'''Add a Subsurface Scattering Preset'''
|
2009-11-22 00:22:29 +00:00
|
|
|
bl_idname = "material.sss_preset_add"
|
2009-11-22 10:02:32 +00:00
|
|
|
bl_label = "Add SSS Preset"
|
2010-09-14 04:58:25 +00:00
|
|
|
preset_menu = "MATERIAL_MT_sss_presets"
|
2009-11-22 00:22:29 +00:00
|
|
|
|
2010-12-20 23:26:29 +00:00
|
|
|
preset_defines = [
|
2011-07-25 06:40:16 +00:00
|
|
|
("material = "
|
|
|
|
"bpy.context.material.active_node_material "
|
|
|
|
"if bpy.context.material.active_node_material "
|
|
|
|
"else bpy.context.material")
|
2010-12-20 23:26:29 +00:00
|
|
|
]
|
|
|
|
|
2009-11-22 00:22:29 +00:00
|
|
|
preset_values = [
|
2010-12-20 23:26:29 +00:00
|
|
|
"material.subsurface_scattering.back",
|
|
|
|
"material.subsurface_scattering.color",
|
|
|
|
"material.subsurface_scattering.color_factor",
|
|
|
|
"material.subsurface_scattering.error_threshold",
|
|
|
|
"material.subsurface_scattering.front",
|
|
|
|
"material.subsurface_scattering.ior",
|
|
|
|
"material.subsurface_scattering.radius",
|
|
|
|
"material.subsurface_scattering.scale",
|
|
|
|
"material.subsurface_scattering.texture_factor",
|
2009-11-22 00:22:29 +00:00
|
|
|
]
|
|
|
|
|
2009-11-22 13:15:21 +00:00
|
|
|
preset_subdir = "sss"
|
2009-11-28 23:37:56 +00:00
|
|
|
|
2009-12-13 14:38:30 +00:00
|
|
|
|
2011-08-12 06:57:00 +00:00
|
|
|
class AddPresetCloth(AddPresetBase, Operator):
|
2010-02-10 22:18:00 +00:00
|
|
|
'''Add a Cloth Preset'''
|
2009-11-22 10:32:37 +00:00
|
|
|
bl_idname = "cloth.preset_add"
|
|
|
|
bl_label = "Add Cloth Preset"
|
2010-09-14 04:58:25 +00:00
|
|
|
preset_menu = "CLOTH_MT_presets"
|
2009-11-28 23:37:56 +00:00
|
|
|
|
2010-12-20 23:26:29 +00:00
|
|
|
preset_defines = [
|
|
|
|
"cloth = bpy.context.cloth"
|
|
|
|
]
|
|
|
|
|
2009-11-22 10:32:37 +00:00
|
|
|
preset_values = [
|
2010-12-20 23:26:29 +00:00
|
|
|
"cloth.settings.air_damping",
|
|
|
|
"cloth.settings.bending_stiffness",
|
|
|
|
"cloth.settings.mass",
|
|
|
|
"cloth.settings.quality",
|
|
|
|
"cloth.settings.spring_damping",
|
|
|
|
"cloth.settings.structural_stiffness",
|
2009-11-22 10:32:37 +00:00
|
|
|
]
|
2009-11-28 23:37:56 +00:00
|
|
|
|
2009-11-22 13:15:21 +00:00
|
|
|
preset_subdir = "cloth"
|
2009-11-22 00:22:29 +00:00
|
|
|
|
2012-04-15 21:02:08 +00:00
|
|
|
class AddPresetFluid(AddPresetBase, Operator):
|
|
|
|
'''Add a Fluid Preset'''
|
|
|
|
bl_idname = "fluid.preset_add"
|
|
|
|
bl_label = "Add Fluid Preset"
|
|
|
|
preset_menu = "FLUID_MT_presets"
|
|
|
|
|
|
|
|
preset_defines = [
|
|
|
|
"fluid = bpy.context.fluid"
|
|
|
|
]
|
|
|
|
|
|
|
|
preset_values = [
|
|
|
|
"fluid.settings.viscosity_base",
|
|
|
|
"fluid.settings.viscosity_exponent",
|
|
|
|
]
|
|
|
|
|
|
|
|
preset_subdir = "fluid"
|
|
|
|
|
2010-02-07 13:56:36 +00:00
|
|
|
|
2011-08-12 06:57:00 +00:00
|
|
|
class AddPresetSunSky(AddPresetBase, Operator):
|
2010-02-10 22:18:00 +00:00
|
|
|
'''Add a Sky & Atmosphere Preset'''
|
2010-02-07 13:56:36 +00:00
|
|
|
bl_idname = "lamp.sunsky_preset_add"
|
|
|
|
bl_label = "Add Sunsky Preset"
|
2010-09-14 04:58:25 +00:00
|
|
|
preset_menu = "LAMP_MT_sunsky_presets"
|
2010-02-07 13:56:36 +00:00
|
|
|
|
2010-12-20 23:26:29 +00:00
|
|
|
preset_defines = [
|
|
|
|
"sky = bpy.context.object.data.sky"
|
|
|
|
]
|
|
|
|
|
2010-02-07 13:56:36 +00:00
|
|
|
preset_values = [
|
2010-12-20 23:26:29 +00:00
|
|
|
"sky.atmosphere_extinction",
|
|
|
|
"sky.atmosphere_inscattering",
|
|
|
|
"sky.atmosphere_turbidity",
|
|
|
|
"sky.backscattered_light",
|
|
|
|
"sky.horizon_brightness",
|
|
|
|
"sky.spread",
|
|
|
|
"sky.sun_brightness",
|
|
|
|
"sky.sun_intensity",
|
|
|
|
"sky.sun_size",
|
2011-04-21 12:14:10 +00:00
|
|
|
"sky.sky_blend",
|
|
|
|
"sky.sky_blend_type",
|
|
|
|
"sky.sky_color_space",
|
|
|
|
"sky.sky_exposure",
|
2010-02-07 13:56:36 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
preset_subdir = "sunsky"
|
|
|
|
|
2010-04-17 19:05:53 +00:00
|
|
|
|
2011-08-12 06:57:00 +00:00
|
|
|
class AddPresetInteraction(AddPresetBase, Operator):
|
* Interaction Presets
This adds a new presets menu in the splash screen and the Input section of
User Preferences to choose a preset interaction style, consisting of key configurations
and also other user preferences such as select mouse button, view rotation style, etc.
Currently, just 'Blender' and 'Maya' presets are included, hopefully we can have more
presets contributed (and maintained!) by the community.
It's best to keep these presets minimal to avoid too many key conflicts. In the Maya one
I changed the view manipulation key/mouse combos and also the transform
manipulator keys, not much more than that.
To save an interaction preset, open the user preferences Input section, and press the
[ + ] button next to the presets menu. It will save out a .py file containing any edited key
maps and navigation preferences to the presets/interaction folder in your scripts folder.
---
Part of this commit changes the way that key maps are exported/displayed in
preferences - now partial key configs are allowed. Previously it would export/import the
entire key configuration, regardless of whether individual key maps were edited or not
(which would make them more susceptible to conflicts in unexpected areas).
(note, in blender terminology, a key map is a category of key items, such as
'Object Mode' or 'View 2d'.)
Now, the export and the UI display work in a similar way to how key maps are
processed internally - Locally edited key maps (after pressing the 'Edit' button) are
processed first, falling back to other key maps in the current key config, and then falling
back to the default key config. So it's possible for a key config to only include a few
key maps, and the rest just gets pulled from the default key config. The preferences
UI display works like this too behind the scenes in deciding what to show users,
however using it is just like it was before, the complexity is hidden.
2010-04-14 06:27:50 +00:00
|
|
|
'''Add an Application Interaction Preset'''
|
|
|
|
bl_idname = "wm.interaction_preset_add"
|
|
|
|
bl_label = "Add Interaction Preset"
|
2010-09-14 04:58:25 +00:00
|
|
|
preset_menu = "USERPREF_MT_interaction_presets"
|
2010-04-17 19:05:53 +00:00
|
|
|
|
2010-12-20 23:26:29 +00:00
|
|
|
preset_defines = [
|
|
|
|
"user_preferences = bpy.context.user_preferences"
|
|
|
|
]
|
|
|
|
|
* Interaction Presets
This adds a new presets menu in the splash screen and the Input section of
User Preferences to choose a preset interaction style, consisting of key configurations
and also other user preferences such as select mouse button, view rotation style, etc.
Currently, just 'Blender' and 'Maya' presets are included, hopefully we can have more
presets contributed (and maintained!) by the community.
It's best to keep these presets minimal to avoid too many key conflicts. In the Maya one
I changed the view manipulation key/mouse combos and also the transform
manipulator keys, not much more than that.
To save an interaction preset, open the user preferences Input section, and press the
[ + ] button next to the presets menu. It will save out a .py file containing any edited key
maps and navigation preferences to the presets/interaction folder in your scripts folder.
---
Part of this commit changes the way that key maps are exported/displayed in
preferences - now partial key configs are allowed. Previously it would export/import the
entire key configuration, regardless of whether individual key maps were edited or not
(which would make them more susceptible to conflicts in unexpected areas).
(note, in blender terminology, a key map is a category of key items, such as
'Object Mode' or 'View 2d'.)
Now, the export and the UI display work in a similar way to how key maps are
processed internally - Locally edited key maps (after pressing the 'Edit' button) are
processed first, falling back to other key maps in the current key config, and then falling
back to the default key config. So it's possible for a key config to only include a few
key maps, and the rest just gets pulled from the default key config. The preferences
UI display works like this too behind the scenes in deciding what to show users,
however using it is just like it was before, the complexity is hidden.
2010-04-14 06:27:50 +00:00
|
|
|
preset_values = [
|
2010-12-20 23:26:29 +00:00
|
|
|
"user_preferences.edit.use_drag_immediately",
|
|
|
|
"user_preferences.edit.use_insertkey_xyz_to_rgb",
|
2011-04-28 09:52:16 +00:00
|
|
|
"user_preferences.inputs.invert_mouse_zoom",
|
2010-12-20 23:26:29 +00:00
|
|
|
"user_preferences.inputs.select_mouse",
|
|
|
|
"user_preferences.inputs.use_emulate_numpad",
|
|
|
|
"user_preferences.inputs.use_mouse_continuous",
|
|
|
|
"user_preferences.inputs.use_mouse_emulate_3_button",
|
|
|
|
"user_preferences.inputs.view_rotate_method",
|
|
|
|
"user_preferences.inputs.view_zoom_axis",
|
|
|
|
"user_preferences.inputs.view_zoom_method",
|
* Interaction Presets
This adds a new presets menu in the splash screen and the Input section of
User Preferences to choose a preset interaction style, consisting of key configurations
and also other user preferences such as select mouse button, view rotation style, etc.
Currently, just 'Blender' and 'Maya' presets are included, hopefully we can have more
presets contributed (and maintained!) by the community.
It's best to keep these presets minimal to avoid too many key conflicts. In the Maya one
I changed the view manipulation key/mouse combos and also the transform
manipulator keys, not much more than that.
To save an interaction preset, open the user preferences Input section, and press the
[ + ] button next to the presets menu. It will save out a .py file containing any edited key
maps and navigation preferences to the presets/interaction folder in your scripts folder.
---
Part of this commit changes the way that key maps are exported/displayed in
preferences - now partial key configs are allowed. Previously it would export/import the
entire key configuration, regardless of whether individual key maps were edited or not
(which would make them more susceptible to conflicts in unexpected areas).
(note, in blender terminology, a key map is a category of key items, such as
'Object Mode' or 'View 2d'.)
Now, the export and the UI display work in a similar way to how key maps are
processed internally - Locally edited key maps (after pressing the 'Edit' button) are
processed first, falling back to other key maps in the current key config, and then falling
back to the default key config. So it's possible for a key config to only include a few
key maps, and the rest just gets pulled from the default key config. The preferences
UI display works like this too behind the scenes in deciding what to show users,
however using it is just like it was before, the complexity is hidden.
2010-04-14 06:27:50 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
preset_subdir = "interaction"
|
2010-02-07 13:56:36 +00:00
|
|
|
|
2010-09-07 15:17:42 +00:00
|
|
|
|
2011-11-07 12:55:18 +00:00
|
|
|
class AddPresetTrackingCamera(AddPresetBase, Operator):
|
|
|
|
'''Add a Tracking Camera Intrinsics Preset'''
|
|
|
|
bl_idname = "clip.camera_preset_add"
|
|
|
|
bl_label = "Add Camera Preset"
|
|
|
|
preset_menu = "CLIP_MT_camera_presets"
|
|
|
|
|
|
|
|
preset_defines = [
|
|
|
|
"camera = bpy.context.edit_movieclip.tracking.camera"
|
|
|
|
]
|
|
|
|
|
|
|
|
preset_values = [
|
|
|
|
"camera.sensor_width",
|
|
|
|
"camera.units",
|
|
|
|
"camera.focal_length",
|
|
|
|
"camera.pixel_aspect",
|
|
|
|
"camera.k1",
|
|
|
|
"camera.k2",
|
|
|
|
"camera.k3"
|
|
|
|
]
|
|
|
|
|
|
|
|
preset_subdir = "tracking_camera"
|
|
|
|
|
|
|
|
|
|
|
|
class AddPresetTrackingTrackColor(AddPresetBase, Operator):
|
|
|
|
'''Add a Clip Track Color Preset'''
|
|
|
|
bl_idname = "clip.track_color_preset_add"
|
|
|
|
bl_label = "Add Track Color Preset"
|
|
|
|
preset_menu = "CLIP_MT_track_color_presets"
|
|
|
|
|
|
|
|
preset_defines = [
|
2011-11-15 20:26:44 +00:00
|
|
|
"track = bpy.context.edit_movieclip.tracking.tracks.active"
|
2011-11-07 12:55:18 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
preset_values = [
|
|
|
|
"track.color",
|
|
|
|
"track.use_custom_color"
|
|
|
|
]
|
|
|
|
|
|
|
|
preset_subdir = "tracking_track_color"
|
|
|
|
|
|
|
|
|
2011-11-28 13:26:46 +00:00
|
|
|
class AddPresetTrackingSettings(AddPresetBase, Operator):
|
|
|
|
'''Add a motion tracking settings preset'''
|
|
|
|
bl_idname = "clip.tracking_settings_preset_add"
|
|
|
|
bl_label = "Add Tracking Settings Preset"
|
|
|
|
preset_menu = "CLIP_MT_tracking_settings_presets"
|
|
|
|
|
|
|
|
preset_defines = [
|
|
|
|
"settings = bpy.context.edit_movieclip.tracking.settings"
|
|
|
|
]
|
|
|
|
|
|
|
|
preset_values = [
|
|
|
|
"settings.default_tracker",
|
|
|
|
"settings.default_pyramid_levels",
|
|
|
|
"settings.default_correlation_min",
|
|
|
|
"settings.default_pattern_size",
|
|
|
|
"settings.default_search_size",
|
|
|
|
"settings.default_frames_limit",
|
|
|
|
"settings.default_pattern_match",
|
2012-01-26 15:33:16 +00:00
|
|
|
"settings.default_margin",
|
|
|
|
"settings.use_default_red_channel",
|
|
|
|
"settings.use_default_green_channel",
|
|
|
|
"settings.use_default_blue_channel"
|
2011-11-28 13:26:46 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
preset_subdir = "tracking_settings"
|
|
|
|
|
|
|
|
|
2012-01-10 16:20:01 +00:00
|
|
|
class AddPresetInterfaceTheme(AddPresetBase, Operator):
|
|
|
|
'''Add a theme preset'''
|
|
|
|
bl_idname = "wm.interface_theme_preset_add"
|
|
|
|
bl_label = "Add Tracking Settings Preset"
|
|
|
|
preset_menu = "USERPREF_MT_interface_theme_presets"
|
|
|
|
preset_subdir = "interface_theme"
|
|
|
|
|
|
|
|
|
2011-08-12 06:57:00 +00:00
|
|
|
class AddPresetKeyconfig(AddPresetBase, Operator):
|
2012-02-08 04:37:37 +00:00
|
|
|
'''Add a Key-config Preset'''
|
2010-09-14 16:45:24 +00:00
|
|
|
bl_idname = "wm.keyconfig_preset_add"
|
|
|
|
bl_label = "Add Keyconfig Preset"
|
2010-10-06 20:29:00 +00:00
|
|
|
preset_menu = "USERPREF_MT_keyconfigs"
|
2010-09-14 16:45:24 +00:00
|
|
|
preset_subdir = "keyconfig"
|
|
|
|
|
|
|
|
def add(self, context, filepath):
|
|
|
|
bpy.ops.wm.keyconfig_export(filepath=filepath)
|
|
|
|
bpy.utils.keyconfig_set(filepath)
|
|
|
|
|
|
|
|
def pre_cb(self, context):
|
|
|
|
keyconfigs = bpy.context.window_manager.keyconfigs
|
|
|
|
if self.remove_active:
|
|
|
|
preset_menu_class = getattr(bpy.types, self.preset_menu)
|
|
|
|
preset_menu_class.bl_label = keyconfigs.active.name
|
|
|
|
|
|
|
|
def post_cb(self, context):
|
|
|
|
keyconfigs = bpy.context.window_manager.keyconfigs
|
|
|
|
if self.remove_active:
|
|
|
|
keyconfigs.remove(keyconfigs.active)
|
|
|
|
|
|
|
|
|
2011-08-12 06:57:00 +00:00
|
|
|
class AddPresetOperator(AddPresetBase, Operator):
|
2010-12-24 07:46:40 +00:00
|
|
|
'''Add an Application Interaction Preset'''
|
|
|
|
bl_idname = "wm.operator_preset_add"
|
|
|
|
bl_label = "Operator Preset"
|
|
|
|
preset_menu = "WM_MT_operator_presets"
|
|
|
|
|
2012-03-21 22:29:49 +00:00
|
|
|
operator = StringProperty(
|
2011-07-25 06:40:16 +00:00
|
|
|
name="Operator",
|
|
|
|
maxlen=64,
|
|
|
|
options={'HIDDEN'},
|
|
|
|
)
|
2010-12-24 07:46:40 +00:00
|
|
|
|
|
|
|
preset_defines = [
|
2011-11-08 16:59:06 +00:00
|
|
|
"op = bpy.context.active_operator",
|
2010-12-24 07:46:40 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
@property
|
|
|
|
def preset_subdir(self):
|
2011-07-11 05:50:49 +00:00
|
|
|
return AddPresetOperator.operator_path(self.operator)
|
2010-12-24 07:46:40 +00:00
|
|
|
|
|
|
|
@property
|
|
|
|
def preset_values(self):
|
2011-08-12 06:57:00 +00:00
|
|
|
properties_blacklist = Operator.bl_rna.properties.keys()
|
2010-12-24 07:46:40 +00:00
|
|
|
|
|
|
|
prefix, suffix = self.operator.split("_OT_", 1)
|
2011-07-25 06:40:16 +00:00
|
|
|
op = getattr(getattr(bpy.ops, prefix.lower()), suffix)
|
|
|
|
operator_rna = op.get_rna().bl_rna
|
|
|
|
del op
|
2010-12-24 07:46:40 +00:00
|
|
|
|
|
|
|
ret = []
|
|
|
|
for prop_id, prop in operator_rna.properties.items():
|
2011-07-25 06:40:16 +00:00
|
|
|
if not (prop.is_hidden or prop.is_skip_save):
|
|
|
|
if prop_id not in properties_blacklist:
|
|
|
|
ret.append("op.%s" % prop_id)
|
2010-12-24 07:46:40 +00:00
|
|
|
|
|
|
|
return ret
|
|
|
|
|
|
|
|
@staticmethod
|
|
|
|
def operator_path(operator):
|
|
|
|
import os
|
|
|
|
prefix, suffix = operator.split("_OT_", 1)
|
|
|
|
return os.path.join("operator", "%s.%s" % (prefix.lower(), suffix))
|
|
|
|
|
|
|
|
|
2011-08-12 06:57:00 +00:00
|
|
|
class WM_MT_operator_presets(Menu):
|
2010-12-24 07:46:40 +00:00
|
|
|
bl_label = "Operator Presets"
|
|
|
|
|
|
|
|
def draw(self, context):
|
2011-11-08 16:59:06 +00:00
|
|
|
self.operator = context.active_operator.bl_idname
|
2011-08-12 06:57:00 +00:00
|
|
|
Menu.draw_preset(self, context)
|
2010-12-24 07:46:40 +00:00
|
|
|
|
|
|
|
@property
|
|
|
|
def preset_subdir(self):
|
|
|
|
return AddPresetOperator.operator_path(self.operator)
|
|
|
|
|
|
|
|
preset_operator = "script.execute_preset"
|