<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CAEAsFmhoR50wPNG9Fv15sc5VJOsitkvGo63re82g0XcY+7Vosg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr" class="gmail_attr">Em sex., 1 de abr. de 2022 às
13:46, Miller Puckette <<a href="mailto:msp@ucsd.edu"
moz-do-not-send="true" class="moz-txt-link-freetext">msp@ucsd.edu</a>>
escreveu:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Because
when just making a patch the origin is conventionally top
left,<br>
not bottom left. So pixels count downward, and if you want
"y" to increase<br>
as you go up, that's the opposite dorection.<br>
</blockquote>
<div><br>
</div>
<div dir="ltr">Sure, but let me see if I get things straight.
This is just meaningful for Data Structures, right? Cause if I
change this in a "regular" canvas, I don't see any difference.
But maybe I'm missing something.</div>
</div>
</blockquote>
<p>all the "units per pixel" values only affect data structure
scalars.<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CAEAsFmhoR50wPNG9Fv15sc5VJOsitkvGo63re82g0XcY+7Vosg@mail.gmail.com">
<div dir="ltr">
<div dir="ltr">
<div>Now, I can see the difference is where to consider
the origin (0/0 coordinate), but I don't know what's the
benefit besides maybe having a more intuitive expectation
when resizing the window, right? Perhaps one could argue it
also makes easier to know where to append objects on the
canvas, but I'm not sure about that.</div>
<div><br>
</div>
<div>Anyway, I really think it makes it very confusing for
setting and retrieving field values that represent the
horizontal axis. In the Data Structures tutorial examples,
like 02.getting.data, the height of the triangle is a
negative number. This is particularly troublesome for
arrays, cause we really expect that the higher the element
is, the higher its value should be.</div>
<div> </div>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
Just install a mirror on your desktop and look at your
screen downward<br>
through it, and you'll see 'y' increase upward when 'scale'
is set to 1 :)<br>
</blockquote>
<div><br>
</div>
<div>
<div dir="ltr">
<div>Not sure if that fixes everything and this can be
easily fixed by setting the "Y units per pixel" value to
a positive number, like in the 07.sequencer examples,
which, by the way, makes much more sense to follow the
score.</div>
<div><br>
</div>
<div>I'm now revising the Data Structures tutorial in my
documentation updates and would like to bring this
discussion into attention. I have changed all the
patches so the "Y" unit is set to positive values and
have better documented how this works. But anyway, I
really think it makes more sense for a default value
that we have Y units set to "1".</div>
</div>
</div>
</div>
</div>
</blockquote>
<p>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 correctly. Also, I think I
remember display errors in the windows when opening them, even if
the canvas was saved with enough height; readjusting minimally the
canvas height fixes it.<br>
</p>
<p>Unless that a window slider control method would be added to
pdcontrol to complement such issues, which would anyway be a good
idea - it would allow for lots of new GUI possibilities.</p>
<p>Joao<br>
</p>
</body>
</html>