[Bf-committers] Patch 6402 Bug in IDProperty handling of matrices
hannu at astro.helsinki.fi
Fri Apr 13 12:01:05 CEST 2007
Thanks, that clarifies things. What about string-type properties, are
under heavy development? The reason I'm asking is that I've got code like
dataStr = (char*) RM_GetPropertyPointer(&ob->id, "example", IDP_STRING, 1);
uiDefBut(block, TEX, 0, "", 90,180,150,20, dataStr, 0, 40.0, 0, 0,
"Example string data");
where dataStr now points to the IDProperty example->data.pointer, and
string leads to severe unstability. The property is initialized with the
IDP_new() as a string
and has enough room for the text.
> Actually, I just remembered we decided not to implement those types.
> Instead, special flags would be made to tag a Array property as a
> vector, matrix, etc.
> On 3/23/07, joe <joeedh at gmail.com> wrote:
>> Hrm. For some reason I can't see how to download the patch here on
>> gmail webmail.
>> Anyway, the reason the matrix and vertex ID property types don't work
>> is because I haven't finished them. To properly get them working,
>> I'll have to also implement the python side of things. I'll look at
>> maybe doing that tomorrow.
More information about the Bf-committers