hey all, on more on data structures....
i've built an xy pad which workd fine in a valu range of 0 - 100 for x and y, but for reasons of applicability and simplicity i'd like to get it to work in a range of 0 -1 if possible. after i brought the patch into that range, it's no more possible to drag the drag-pointer with the mouse. can somone explain that behaviour? or maybe i miss something? thanks in advance!
here's th patch: xy.zip

EDIT: here's the working patch for the range of 0 - 100.
xy-working.zip

just another question to the data structure wizards here: i still don't really know, why i need a kind of "guiding" polygon (layered under the blue square), but somhow it wouldn't work properly without it (could only drag on the upper left corner of the square). can someone explain, why? please...

@ingox unfortunately it also baffles me, I struggle along trial and error fashion until it works following the help in "/doc/4.data.structures/09.scaling.pd" which is not really helpful.
You can scale the pad using dynamic patching
here is your controlsurface-mod.pd with scaling
pad.pd

Edit: No it does not work properly but I'm sure it can - working on it

@toxonic Very late to this...... and probably not understanding.
I have here......... zoom.pd added a [zoom] to the canvas [pd tracelist] that displays the numerous data structures of the tracelist in \pd-0.50-0\doc\4.data.structures/14.particletracer.pd
It just uses donecanvasdialog to set the x and y units per pixel........ zooming the canvas.
All the datastructures are then accessible with the mouse with much greater accuracy.
No idea whether that is what you are looking for though....... much too simple..... so probably not!
David.

@Balwyn So i used this idea and gave it another try: pad.pd. This seems to work fine.

Well, to make the boundaries go from -5 was not such a good idea, because as an abstraction, the square can not be grabbed outside the border... But as a demonstration it hopefully works

@ingox just brilliant!
A beautifully rendered patch that makes my patch look awkward, you have a real knack of simplifying the difficult stuff and solving too

Here now within the boundaries and with values from zero to max: pad.pd

Or from zero to max minus one, if this is more convenient: pad.pd

Just found another (video) tutorial. Not sure if there is anything new, but I think it is well explained: https://media.ccc.de/v/lac2018-26-understanding_and_being_creative_with_pure_data_s_data_structures#t=6984

@ingox said:

.... now the parentheses come into play: Instead of actually using the given coordinates x0 and y0, Pd arranges each point relative to the value range given in parenthesis:

The first x0 can move between 0 and 240 on the x axis and between 0 and 240 on the y axis. The second x0 can move between 0 and 240 on the x axis and is therefor placed at the same height as the first one.

But the second one can be moved between 10 and 250 on the y axis and is therefor placed below the first one (counting from top on the y axis, if i recall correctly).
.....

hey again! i'm still having problems to understand, how these boundaris exactly work. let's have a look at your example:

the first pair of coordinates seem clear so far. the second pair describes the point below the first one, if i got you correctly. so the x0 variable can move between 0-240 on x-axis and 10-250 on y axis, which is 10 point below the first one.
BUT... why do the boundaries of the y0-variable differ from those of x0? they do describe the same vector, so i presumed, the'd also need to be bound to (0:240)(10:250). the next coordinate pairs are equally obscure to me.... let's look at the third pair, which i guess, is the point to th right from the second one. why is x0 bound between 0 an 240 on the x-axis? shouldn't it be bound to (10:250), as it should have a 10 pixel offset to the other points? sorry for my silly questions, but this is really confusing to me...

ahhhhh..... now the penny dropped!
i completely missunderstood that....the first parentheses value pair sets a value-range, the second one is responsible for the relative positioning! and this way, it's more than easy to get a value range 0-1 for an xy pad. and more: you can set the range on the fly when you assign variables! look at this here, an xy pad where you can select between two retangles in the same subpatch with different value ranges:
xy_range_0-1.pd

@toxonic said:

....you can set the range on the fly when you assign variables!

what a pity, its seems, you can't assign variables to these values - i get a parse error!