[Bf-python] The road to deprecation

[Sybren A. Stüvel]

On Tue, Jan 06, 2015 at 02:42:42PM +1100, Campbell Barton wrote:
> There are so many cases where you _might_ want an update that I
> think its better to be explicit here.

I fully agree.

> For example, if you set a vertex location you don't get the result
> in Python (updated bounding box etc) until you run `scene.update()`.
> But it doesn't make sense to add a vertex.set_co() method just to
> get an instant update. (wouldn't have to be added for every other
> data type... uv's etc).
> 
> 
> Why not instead remove `frame_set` and have an explicit update
> function?
> 
> ::
>     scene.frame_current = 123
>     scene.frame_update()
> 
> Then we keep the rule of thumb that expensive global re-evaluation
> is done explicitly.

That looks like a good plan.

Do you also agree with my 4-step deprecation idea?

-- 
Sybren A. Stüvel

http://stuvelfoto.nl/
http://stuvel.eu/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.blender.org/pipermail/bf-python/attachments/20150106/7ff6ca5e/attachment.sig>