[Bf-committers] History items for Python API.

dima glib dima.glib at gmail.com
Sat Nov 19 11:25:09 CET 2016

As an addon developer, I think this functionality is a must-have :-)

First of all, because it gives access to a missing part of API (to my
knowledge, there is simply no way for a script to know the size of the undo
stack, the current position in the stack and the names of its items).

This kind of information would be very useful for efficiently & reliably
detecting changes in the scene (for example, if I want to run a
non-realtime computation/update when something in the scene was modified or
when the selection has changed, with the current Blender I have to resort
to a rather tricky distributed-over-time monitoring in

On Sat, Nov 19, 2016 at 10:14 AM, RoAoAo . <roaoao at gmail.com> wrote:

> Hi.
> I want to send a patch which adds an access to* bpy.ops.ed.undo_history*
> menu items (C.history_items or something like that). It will allow to
> create add-ons which can speedup user's workflow.
> For example imagine an add-on which subdivides a mesh using incremental
> *number
> of cuts* value. When you call that operator for the first time it will
> subdivide the mesh using number_cuts=1, the second time - number_cuts=2,
> and so on. So if we assign a hotkey (e.g. S) to that operator, we can use
> it like this - SSS...
> What do you think? Does the patch have a chance to be accepted?
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers

More information about the Bf-committers mailing list