[Bf-committers] Hard lock while using GUI-Scripts Was Re: [Bf-committers] Quicktime & autoconf

[Meino Christian Cramer]

From: Kester Maddock <Christopher.Maddock.1@uni.massey.ac.nz>
Subject: Re: [Bf-committers] Quicktime & autoconf
Date: Mon, 5 May 2003 11:52:57 +1200

Hi Kester,

 ...will try this this evening, since I am not at home for a while
 this day.

 I am eager to catch the bug and to help the blender sourcerer a
 little bit in makeing Blender a stable place in life :)

 I have another script found (an exporter to the yafray renderer -- by
 the way: yafray is excellent compared to its early state of
 development!),  which puts some buttons on the screen.

 I will try to lock my box with it as soon as I am at home  ;))

 Thank you very much for your support, Kester ! :)

 Kind regards,
 Meino

 PS: I haeve changed the subject of the mail to distinguish this
 thread from that which deals with the other problem: The
 quicktime-I-cannot-compile-this-without-hacking-configure.ac-bug.
 OK?


> Hi Meino,
> 
> I don't think pdb's --> or step function is very accurate. :)
> You can insert breakpoints and step to those, or move the set_trace call to 
> change the stop point.  You have to find the latest point in the script you 
> can break at before crashing.  It is probably before trace_rectangle3(r,c,c1)
> in draw1 which has the first GL calls.
> 
> Otherwise (workaround), set_trace after "That's began!" and type this into the 
> pdb prompt:
> export_file(anim, patchtype, debug, 'inc',  G_Set, layer, export, 
> texturestype)
> 
> Can you get a gui out of any other script?
> 
> Kester
> 
> _______________________________________________
> Bf-committers mailing list
> Bf-committers@blender.org
> http://www.blender.org/mailman/listinfo/bf-committers
>