[Bf-python] creating IPO

[Willian Padovani Germano]

Hi Paolo,

Sorry for taking long to answer, I've not been in touch with Ipo related stuff.
Seems Guignot, the module writer / owner isn't around right now at least.

----- Original Message -----
From: <info at blender3d.it>
To: <bf-python at blender.org>
Sent: Saturday, May 22, 2004 1:17 PM
Subject: [Bf-python] creating IPO


> I'm working on a script using IPOs and I have a couple of questions:
>
> 1. It's correct to create a new ipocurve with statment:
>         ipo = Ipo.New('Object', "name_of_ipo")
>         ipo.addCurve('RotX')
> this is working but is not documented in the API.

Thanks, from looking at the archives this is a working function indeed, let's
document it.

> 2. in the ipo window I can see dRotX and dLocX ipos
>     but if I want to create a dRotX ipocurve I have to write
>     addCurve(DRotX.....
>     is this a bug?

No, more like a decision on naming conventions for the api.  Looking at the
addCurve function, it has a long list of string compares for all possible
parameters.

> 3. Can please someone explain which is the difference between RotX and dRotX
> or between LocX and dLocX

Looking for recent Guignot posts, saw this from Alfredo (eeshlo) about the d***
params:
http://www.blender.org/pipermail/bf-python/2004-February/001112.html :
"
This delta params work when the object has an ipo. So
just add an ipo, add some location keys (only needs
one key, doesn't have to be actual animation), the
dloc values are then the changes relative to the
original location, same for rotation & size.
There is some example scripts in the original dynoise
zip on my old site, which used dLocXYZ/dRotXYZ for
camera jitter using the noise module, maybe a good
example script as well for the new internal noise
module, when I finally get around finishing that...
"

BTW, coders who write scripts that deal with ipos here: recall this module
needed some updates, how is it now?

--
Willian, wgermano at ig.com.br