[Bf-committers] Feedback on macro design
aligorith at gmail.com
Mon Sep 14 08:46:27 CEST 2009
I'd just like to make a mention here that these issues are probably some of
the most critical issues with macros now.
The first one (modal operators only coming last) is quite restrictive, since
IMO that's the step you'd want to occur first most of the time with a
select/create then operate workflow. As a workaround, I've once tried
creating an operator using the python api which would call these operators
one by one. However, it soon became apparent that this approach was worse
than just using macros (unless the py-api was only defining a macro too),
since the operators were not executed in the order I had defined. (NOTE: for
those interested, see the Grease-Pencil related script linked to in an
earlier mail about py-api calling operators)
On Mon, Sep 14, 2009 at 6:03 PM, joe <joeedh at gmail.com> wrote:
> There's a few issues with macros I think need to be solved:
> * You can't combine a modal operator with other ones, e.g. a special
> select tool that calls another tool afterwards. For example,
> edge ring select (with preview) and subdivide to create loopcut.
> Note that edge ring select isn't a modal tool from the users
> point of view, but it is a modal operator (to draw the preview while
> the mouse button is held down).
> * You need to be able to set properties in components of a macro
> operator at macro definition time. This is important for extrude,
> for e.g. properly calling normal grab after the extrude, instead of
> just grab.
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers