[Bf-committers] Weekly irc meeting, october 4 2009

[Brecht Van Lommel]

Hi,

On Mon, Oct 5, 2009 at 6:46 PM, Dalai Felinto <dfelinto at gmail.com> wrote:
>> Now, I don't know what Dalai wanted to use this for exactly, but I
>> think it's important he explains it, and we think of how it can fit
>> in, rather than assume notifiers are the solution.
>
> My request may even be simpler than what Matt suggested. I have so far
> two uses for it. Interesting those are the two scripts I ported to 2.5
> so far, and both would take advantage of it:
>
> 1) a script that requires a password input [1]. Every time one types a
> char I want to store it internally and replace it with a '*'.
> 2) a script that requires fine tuning of parameters to calculate
> something. It's too annoying to (a) change the parameter and then (b)
> press "calculate". I can see multiple examples of this being needed.
> eg to move an object in scene through this script.
>
> Making long short: Think about how to re-create a "F6" (redo last)
> kind of functionality. In cases like that you don't want to set a
> parameter and then click in an operator, you want it to change right
> away.

The point is that you shouldn't have to recreate F6, it already
exists, doing it manually is not very reliable and means the tool
doesn't fit in with other things. If you write an operator, you get
this functionality. And writing a script that requires password input,
doing it this way is really a hack, better implement a password
textbox in the Blender code then.

Brecht.