Indeed, bpy.types.Macro is a pretty useful mechanism which is left completely unexplained in the official documentation. I had no idea that stringing operators together is even possible until I accidenatlly stumbled upon Macro usage in someone's code. Just in case, here's one more link to a stackexchange question regarding Macro: https://blender.stackexchange.com/questions/39716/running-code-after-a-modal-operator-finished-its-job
Hm, perhaps this discussion also concerns [email protected]? On Mon, May 1, 2017 at 5:25 AM, James Crowther <[email protected] > wrote: > Hi there, > After spending some time researching the bpy.types.macro class both in the > api an on blender stack exchange, I’m keen to learn more about macros, the > code I have found suggests that it can be used to group operators together > into a single operation (ref blender stack exchange - > https://blender. > stackexchange.com/questions/60385/macro-operator-children- > are-not-called-from-python). But the blender python api really doesn’t > give information on what the use case for macros are. Things like modal > operators overriding context are well explains, but macros seem to be a bit > secretive! It would be great to see some more informative documentation on > the subject. Since it appears that others (see the webpage link above) are > finding it difficult to get even basic examples to work as desired. If > someone could give a quick introduction to macros and what they are best > used for, it would be greatly appreciated! > > > Kind Regards > > James > > > > _______________________________________________ > Bf-python mailing list > [email protected] > https://lists.blender.org/mailman/listinfo/bf-python > >
_______________________________________________ Bf-python mailing list [email protected] https://lists.blender.org/mailman/listinfo/bf-python
