The order of the bounds message is: ", , , ".
This makes more sense as a pair of top and bottom coordinates and
maybe we can change the window dialog accordingly, but I also think
that is quite confusing. The message seems inverted as it'd make more
sense to me to something like ", , , " or
Em dom., 3 de abr. de 2022 às 19:18, Alexandre Torres Porres <
por...@gmail.com> escreveu:
> Em sáb., 2 de abr. de 2022 às 17:47, João Pais
> escreveu:
>
>> all the "units per pixel" values only affect data structure scalars.
>>
>
> Thanks for clarifying
>
Well, that is not actually true.
Em sex., 1 de abr. de 2022 às 23:42, Alexandre Torres Porres <
por...@gmail.com> escreveu:
> Em sex., 1 de abr. de 2022 às 23:11, Alexandre Torres Porres <
> por...@gmail.com> escreveu:
>
>> I have changed all the patches so the "Y" unit is set to positive values
>>
>
> Many of them already were
Em sáb., 2 de abr. de 2022 às 17:47, João Pais
escreveu:
> all the "units per pixel" values only affect data structure scalars.
>
Thanks for clarifying, here's another question: whenever we have "graph on
parent" checked, the units per pixels get grayed out and it seems that this
parameter is
Em sáb., 2 de abr. de 2022 às 17:47, João Pais
escreveu:
> the problem is that when making new patches where height plays a role,
> unless you know the limits for your height and set your window accordingly,
> you'll always have to play around with the vertical slider for it to
> display
Em sex., 1 de abr. de 2022 às 13:46, Miller Puckette
escreveu:
Because when just making a patch the origin is conventionally top
left,
not bottom left. So pixels count downward, and if you want "y" to
increase
as you go up, that's the opposite dorection.
Sure, but let
Em sex., 1 de abr. de 2022 às 23:11, Alexandre Torres Porres <
por...@gmail.com> escreveu:
> I have changed all the patches so the "Y" unit is set to positive values
>
Many of them already were by the wau, not only 7.sequencer
___
Pd-list@lists.iem.at
Em sex., 1 de abr. de 2022 às 13:46, Miller Puckette
escreveu:
> Because when just making a patch the origin is conventionally top left,
> not bottom left. So pixels count downward, and if you want "y" to increase
> as you go up, that's the opposite dorection.
>
Sure, but let me see if I get
Because when just making a patch the origin is conventionally top left,
not bottom left. So pixels count downward, and if you want "y" to increase
as you go up, that's the opposite dorection.
Just install a mirror on your desktop and look at your screen downward
through it, and you'll see 'y'
Hi, I believe this must have been discussed before... it's surely known. I
wonder why when you add a subpatch the 'scale' section has an inverted "-1"
scale for the vertical axis. This is particularly bad for display data
structures and needs to be corrected by hand.
Should I open a request to
10 matches
Mail list logo
