[PD] Keeping Number box's
pkstone at ucdavis.edu
Mon Apr 14 23:39:28 CEST 2014
oops, meant to send this to the list, sorry Jonathan.
On 4/14/14, 1:11 PM, Phil Stone wrote:
> You have a point, if you are init'ing to zero; otherwise, it's easy to
> see that a Number2 box is init'd when you open the patch, because it
> has a non-zero value in it.
> But yeah, it's a little kludgey (especially the "init"/"no init"
> button: is it status, or what *will* happen when you press it -- hint,
> it's the latter, like most buttons). I wouldn't recommend it for use
> with all those Pd nuclear weapon-control patches that are out there.
> On 4/14/14, 12:56 PM, Jonathan Wilkes wrote:
>> On 04/14/2014 02:03 PM, Phil Stone wrote:
>>> Or use the "Number2" number box, and set its "init" attribute in
>>> properties. It will then init itself with the last value that was in
>>> the box at the time the parent patch was saved.
>> I try to avoid the iemgui "init" method because it isn't represented
>> in the Pd diagram.
>> I'd rather do this:
>> Then you can see if you made a mistake. For example, I forgot to
>> connect [loadbang] to [42(. I can quickly scan all other places
>> where I use [loadbang] to see if I made a similar error.
>> But if you use the "init" method, you must right-click and choose
>> "Properties" on every single numbox to do error checking. The time
>> wasted isn't worth whatever it is you think you save by using "init".
>> Digression-- consider a Properties dialog with the following button:
>> [don't fire nukes]
>> Do you press it or not?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pd-list