[Bf-committers] UI idea: do operation delete and toggle visibility/select/render on object including all child-objects
michaelw at cowtoolsmedia.co.uk
Sat Sep 18 11:21:17 CEST 2010
wouldn't lightwave's "render selected" approach be simpler? just have
another render mode that ignores un-selected objects.
As for the original idea, a simple way of selecting multiple objects and
changing their properties all at once is obviously very desirable....
either by showing "mixed" states, outliner context menus...
I've toyed with the idea of making a "spreadsheet" style editor in
python.... but it'd need python space types to get a decent amount of
On 18/09/2010 08:41, Michelangelo Manrique wrote:
> for rendering it could be interesting a SuperbRender icon in the
> outliner. If you have say twenty objects with different shading and
> textures (talking about heavy ones) and you need to test just a single
> one with final compositing and lighting, it is tedious deselecting the
> render icon close to all the other nineteen objects. Having an option to
> just select the object you desire to test render could be interesting...
> even the others objects have the render icon enabled it should work IF
> SuperbRender IS enabled just render it ELSE render all the others also
> (talking very much in php style sorry :P)
> Well just another idea
> On Sat, 2010-09-18 at 15:39 +0900, Torsten Rupp wrote:
>> Dear developers,
>> just an idea:
>> As I know there is currently no functionality to delete and toggle
>> visibility/selectability/renderability for an object including all
>> child-objects, e. g. an object created out of several parts and put
>> together under an empty as the parent. It would be useful to have
>> this e. g. in the outliner to toggle the visibility of such a
>> multi-part-object or to delete it including all parts.
>> May it be useful to have such a functionality (I know not for 2.5beta
>> now, but in the long run)? Best would IMHO be some click+modifier
>> operation and/or menu entries, but for buttons this seems currently
>> not possible with the existing handler-structure. I just had a short
>> look, but I could not find keyboard modifier information available in
>> the button handlers, e. g. the outliner buttons, isn't it?
>> If I'm wrong and these functionality already exists, please let me
>> know (and apologize that I have bothered you with this mail).
>> Bf-committers mailing list
>> Bf-committers at blender.org
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers