[Pd] Scaling Scalars

Chuckk Hubbard badmuthahubbard at gmail.com
Mon Nov 20 22:14:02 CET 2006


Wonderful, thanks!  How on earth did you learn that?

On 11/20/06, João Miguel Pais <jmmmpais at googlemail.com> wrote:
> have you tried "donecanvasdialog $1 -1 0"? (if I understood the problem)
> send that to your patch window, and will change the "X units per pixel"
> field. the next values are for y and show on parent.
> I use this to rescale a patch with a ds polygon. only the ds get rescaled,
> other bangs and etc don't. all values remain the same.
>
> Am 20.11.2006, 09:55 Uhr, schrieb Chuckk Hubbard
> <badmuthahubbard at gmail.com>:
>
> > Hello.
> > I was thinking I could fix the questionable zoom in my sequencer with
> > scalar scaling.  Instead of redrawing all the scalars, I would have a
> > variable by which all of it were scaled.  This doesn't seem to work,
> > which I expected, but is there some other way?  I tried:
> > [drawpolygon 0 1 0 0 c(-100:100)(a:b) 0 c(-100:100)(a:b) 10 0 10 0 0]
> > I didn't think this would work, but is there something else I could try?
> >
> > The problem is that, as it is, I have a constant 'zoomfact' that feeds
> > into and out of every function that involves display or timing during
> > playing, and every scalar in the score is changed by that factor.
> > Invariably I forget where it goes or what order it should go in and
> > stuff goes wrong.
> > I'm curious whether there's a way for one variable to change only the
> > drawing instructions, but not change the actual values, so that the
> > timing will be unaffected by the zoom.
> >
> > -Chuckk
> >
>
>
>
> --
> Friedenstr. 58
> 10249 Berlin
> Deutschland
> Tel +49 30 42020091
> Mob +49 162 6843570
> jmmmpais at googlemail.com
> skype: jmmmpjmmmp
> http://www.puredata.org/Members/jmmmp
> IBM Thinkpad R51, XP, Pd-Ext-0.39-2-t5
>


-- 
"Far and away the best prize that life has to offer is the chance to
work hard at work worth doing."
-Theodore Roosevelt




More information about the Pd-list mailing list