Yamyam: 1版をインポートしました

2018-06-28T21:21:40Z

1版をインポートしました

wiki>Lijenstina: /* Forward Compatibility */

2017-07-16T13:50:09Z

‎Forward Compatibility

新規ページ

= Blender 2.79: Python API =

== Breaking Changes ==
* Switched default value of <code>do_unlink</code> parameter of <code>bpy.data.xxx.remove()</code> functions from <code>False</code> to <code>True</code>. ({{GitCommit|44b691dc658}}){{clr}}

== Data-block Pointer Properties ==

Custom properties can now store pointers to data-blocks like objects, materials, etc. For this the a <code>PointerProperty</code> with a datablock type can be created.

==== Forward Compatibility ====

Unfortunately, this new custom property type revealed a critical bug in current code, which crashes Blender on unknown property types. This bug has been fixed in {{GitCommit|15189baa52}} for the future, but it is impossible to fix this for existing releases.
<br \>

'''This means that trying to load a .blend file using new data-block custom properties will crash on any version prior to 2.79'''.

For more technical details about the problem, see {{BugReport|51260}}.

== Render Passes ==

Render passes are now identified exclusively by their name, the type property has been removed. The purpose of that change is to allow external rendering engines to produce arbitrary render passes and return them to Blender, rather than being limited to the 31 types of passes exposed by Blender before. ({{GitCommit|4cf7fc3b3a4d}}),)

Changes:
* The properties <code>type</code> and <code>debug_type</code> have been removed from the <code>RenderPass</code> struct.
* The function <code>find_by_name</code> has been added to the <code>RenderPasses</code> struct, and <code>find_by_type</code> has been deprecated.
* <code>SceneRenderLayer</code> now supports custom properties, which allows render engines to add their own pass options.
* <code>RenderEngine</code> has three new functions:
** <code>add_pass</code>, which can be called by the render engine while rendering to add a render pass to the render result by providing its name, amount of channels, characters identifying the channels (like <code>RGBA</code>) and optionally which render layer it should be added to.
** <code>update_render_passes</code>, which has to be implemented by render engines that use render passes. It's purpose is to inform Blender of which passes will be generated given the current options, which is does by calling <code>register_pass</code> for each one.
** <code>register_pass</code> should be called by update_render_passes to inform Blender about a pass that will be generated by passing the name, channels and data type (used to determine the compositor output socket).
* 31 pass names are reserved to represent the former 31 pass types. Render Engines may provide these passes, but should consider that they will be associated with the legacy pass types (for example, compositor node connections will be preserved).

=== Other New APIs ===

* [https://www.blender.org/api/blender_python_api_master/bpy.types.ID.html#bpy.types.ID.make_local <code>bpy.types.ID.make_local()</code>] to make a single ID block local. ({{GitCommit|592e9e9245}})
* Inserting entries in the right click menu (and retrieving data from the UI element that you clicked on the entry). Example in [https://docs.blender.org/api/blender_python_api_current/bpy.types.Menu.html#custom-item-in-the-right-click-menu <code>bpy.types.Menu</code> docs]. ({{GitCommit|d6963630d}})
* ID property arrays support the Python buffer protocol. This makes it possible to create and access those arrays much more efficiently. ({{GitCommit|73a9ff0d2d4f}})

← 古い版	2018年6月28日 (木) 21:21時点における版
(相違点なし)

Dev:Ref/Release Notes/2.79/PythonAPI - 版の履歴

Yamyam: 1版 をインポートしました

wiki>Lijenstina: /* Forward Compatibility */

Yamyam: 1版をインポートしました