[Bf-python] Draw.RegisterEvent proposal

[joeedh]

Willian Padovani Germano wrote:

>Hi Joseph (joeedh),
>
>----- Original Message -----
>From: "joeedh" <joeeagar at prodigy.net>
>To: <bf-python at blender.org>
>Sent: Monday, August 02, 2004 11:58 PM
>Subject: [Bf-python] Draw.RegisterEvent proposal
>
>Not trying to dissuade you, *really*, but as this touches parts outside
>bpython, actually the main event loop, it needs to be discussed at the
>bf-committers list too, starting with a simple proposal, with examples of
>usage.  There people not necessarily know about Draw.Register, etc. so the
>proposal should be more general, about the functionality itself and what it
>could be good for.
>
>That's how it happens always -- Ton would eventually ask you for this.  And
>let me warn that most times it's not as fast as the coder would like.  Your
>idea is a good one, we all just need to discuss, get suggestions from all
>about possible uses and the best way to implement it.
>
>  
>
Fair enough.

>Since the code for scriptlinks is already in place and has a straightforward
>interface, I suggest we start there, there can be more scriptlink event
>types.  And it's easy to set them from scripts now, too.
>
>  
>
My concern is that the scriplinks seem to be designed for non-GUI 
scripts.   They work well enough for scripts without GUIs, but for those 
that use the Draw module I think a special  "function-link" setup would 
work a LOT better.

>>This is something I personally think is vitally needed for, say, the
>>creation of python scripts that can work on a per-object basis easily
>>and without the use of the threading module.
>>    
>>
>
>Object scriptlinks on redraw might be enough for this particular example, or
>not?
>
>  
>
Your right.  I tried that before, but it didn't work. . .I must've been 
using a glitchy version of Blender, or I didn't do it right.  Yay!!  
This solves a great deal of problems.  Hopefully.

joeedh