On 11/11/2009 07:10 AM, Erik Hofman wrote:
> John Denker wrote:
>> Having used the feature both ways, I remain of the opinion
>> that the string representation is easier for the user to
>> interpret. Doing this safely via a few static char*s is
>> easy to do. Let me work on it.
>
> To be honest
John Denker wrote:
> Having used the feature both ways, I remain of the opinion
> that the string representation is easier for the user to
> interpret. Doing this safely via a few static char*s is
> easy to do. Let me work on it.
To be honest I don't think it's worth the effort, but I wont hold
On Wed, Nov 11, 2009 at 2:43 PM, John Denker wrote:
>
> Before switching to the string representation, I read the
> code for the tie functions. I got the impression the code
> was making a clone, i.e. a deep copy. Apparently this
> impression was incorrect. Sorry.
No, the problem isn't with th
On 11/10/2009 06:36 PM, Csaba Halász wrote:
> On 5 Nov 2009, at 09:18, Erik Hofman wrote:
>
>> John Denker:
>> Add a view debugging functions and represent the viewer quats in the
>> property tree for debugging.
>
> Unfortunately the debug code is broken and causes segfaults. It is
> tieing tempo
Csaba Halász wrote:
> On 5 Nov 2009, at 09:18, Erik Hofman wrote:
>
>> John Denker:
>> Add a view debugging functions and represent the viewer quats in the
>> property tree for debugging.
>
> Unfortunately the debug code is broken and causes segfaults. It is
> tieing temporary char pointers to pr
On 5 Nov 2009, at 09:18, Erik Hofman wrote:
> John Denker:
> Add a view debugging functions and represent the viewer quats in the
> property tree for debugging.
Unfortunately the debug code is broken and causes segfaults. It is
tieing temporary char pointers to property nodes. In its current
inca
6 matches
Mail list logo
