Re: [Bf-committers] [Bf-blender-cvs] SVN commit: /data/svn/bf-blender [32165] trunk/blender/source/blender/ editors/space_image/image_ops.c: Make Cycle Render Slot actually cycle through all slots.

Is it intentional that this also cycles to an unused slot (eg. if slot 1 and 2 are full, going to 3)? Because it's very annoying - it means you can't just press J, J to flip between two slots to compare them, you get the empty buffer in between. If it's going to be cycling, it should just cycle

[Bf-committers] derived mesh in modifier stack

Hi, As far as i found out, a DerivedMesh is created as soon as some modifier needs to construct its own geometry. There are the utility functions get_dm() and get_cddm() in MOD_util. What is their purpose? I looked at what they are doing and it looked like get_cddm() would ensure a

[Bf-committers] Issue to build blender-2.54 on Fedora Linux

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hallo, I have try to build blender-2.54 for Fedora Linux. Unfortunately, I have got the follwoing error messages shown above. Because the error occurs during the install step, I assume this is an issue with the implicite DSO linking feature on

Re: [Bf-committers] [Bf-blender-cvs] SVN commit: /data/svn/bf-blender [32165] trunk/blender/source/blender/ editors/space_image/image_ops.c: Make Cycle Render Slot actually cycle through all slots.

I personally thought J+# would be good. So just J would toggle between slots one and two, but J+3 would go straight to slot 3, J+6 would jump to slot 6 etc. That way it would be possible to compare renders in slots that are not right next to one another. -Sean On Sun, Oct 10, 2010 at 12:40 AM,

Re: [Bf-committers] derived mesh in modifier stack

Hi Tobias, I've taken a quick peek and it looks like get_dm() and get_cddm() return copies of the original or derived mesh and therefore leave the originals untouched. So i dont think you will find updated vertices from either of these functions. It only makes sense so that when you remove

[Bf-committers] No custom properties on bones?

I'm unsure if this is a bug, so I'll hold off filing a bug report. It seems that it's not possible to create custom properties on bones or pose bones. This works: bpy.types.Object.new_prop = bpy.props.FloatProperty() But these don't: bpy.types.Bone.new_prop = bpy.props.FloatProperty()

Re: [Bf-committers] No custom properties on bones?

On Mon, Oct 11, 2010 at 1:13 AM, Nathan Vegdahl ces...@cessen.com wrote: I'm unsure if this is a bug, so I'll hold off filing a bug report. It seems that it's not possible to create custom properties on bones or pose bones. This works:    bpy.types.Object.new_prop = bpy.props.FloatProperty()

Re: [Bf-committers] No custom properties on bones?

Thanks Campbell! :-D --Nathan On Sun, Oct 10, 2010 at 9:53 PM, Campbell Barton ideasma...@gmail.com wrote: On Mon, Oct 11, 2010 at 1:13 AM, Nathan Vegdahl ces...@cessen.com wrote: I'm unsure if this is a bug, so I'll hold off filing a bug report. It seems that it's not possible to create