[Bf-committers] UI idea: do operation delete and toggle visibility/select/render on object including all child-objects
rogerwickes at yahoo.com
Sat Sep 18 15:46:36 CEST 2010
you can also use the renderability icon in the outliner view. it is very quick
to just go down the list and click. For more advanced or repeatable sets, use a
Check out my website at www.rogerwickes.com for a good deal on my book and
training course, as well as information about my latest activities. Use coupon
Papasmurf for $15 off!
----- Original Message ----
From: Michelangelo Manrique <michelangelomanrique at hotmail.com>
To: bf-blender developers <bf-committers at blender.org>
Sent: Sat, September 18, 2010 7:44:35 AM
Subject: Re: [Bf-committers] UI idea: do operation delete and toggle
visibility/select/render on object including all child-objects
indeed, i'm using this method actually in a current project but just
wanted a quicker method to do exactly that, current method needs to
select object, "/" key on numpad and 0 Key on numpad to select active
camera before render -if you want to check also the view- but would be
nice having same effect by clicking a single icon :) :P
On Sat, 2010-09-18 at 13:22 +0200, Pablo Vazquez - www.venomgfx.com.ar
> Many of this ideas are already there, so to speak (if not, go improve them! :D
> Torsten' idea of changing visibility/render for many objects:
> This can be done already by using object groups, thanks to Campbell on
> Durian, since a few months we can restrict visibility/select/render on
> Groups in the outliner (groups view).
> Michelangelo's idea for rendering individual objects:
> Can be done by selecting the objects and going to Local view with "/"
> on the numpad, it even respects lights, can be used mixed with the
> feature above.
> Michael Williamson' s idea for changing properties of many objects at once:
> An attempt to this we needed on Durian, so Campbell quickly made a
> script to allow us this, is currently an 3D View addon called: "Object
> Property Chart", it *really* helped us and is really handy, though it
> was a quick approach he said, so maybe it could be improved by someone
> else (like adding an option to toggle all options on that column at
> once or so).
> On Sat, Sep 18, 2010 at 11:21, Michael Williamson
> <michaelw at cowtoolsmedia.co.uk> wrote:
> > 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
> > screenspace...
> > 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
> >> Mich
> >> 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).
> >>> Torsten
> >>> _______________________________________________
> >>> Bf-committers mailing list
> >>> Bf-committers at blender.org
> >>> http://lists.blender.org/mailman/listinfo/bf-committers
> >> _______________________________________________
> >> Bf-committers mailing list
> >> Bf-committers at blender.org
> >> http://lists.blender.org/mailman/listinfo/bf-committers
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> Bf-committers mailing list
> Bf-committers at blender.org
Bf-committers mailing list
Bf-committers at blender.org
More information about the Bf-committers