• jancsika

    That's certainly possible. I'll show a demo when I get a chance.

    The only thing missing atm is the possibility to define a "drag" event in editmode for scaling the scalar. That's why I put it in runmode on the other demo.

    posted in technical issues read more
  • jancsika

    @th8a Would you be shipping a scalable square-circle-triangle-piano, or do you want to ship a library that allows users to make arbitrary combinations of squares, circles, triangles, and pianos?

    posted in technical issues read more
  • jancsika

    Also notice that there are only two fields to the struct: x and y. That means if you copy and paste the widget, the only data saved with the scalar are the x/y coordinates. If you wanted to be able to have multiple collections of widgets operating independently you would need an additional field in the struct for each piece of data. For example, adding xSize and ySize would allow you to save the dimensions of each scalar. (You'd also have to change the guts of the drawing routine to fetch and set those values.)

    posted in technical issues read more
  • jancsika

    @th8a Here's a quick hack:

    responsive-demo.pd

    The hack is that I currently don't have an easy way to do clipping, so I'm using grouping and opacity to work around that.

    The logic for the keyboard is: when the scaling factor is large enough AND the proportions of the box are wide enough, the piano appears. Otherwise it hides itself. You could define other size/position changes for each widget based on the size of the container.

    As hacky as this is, I think it's still easier to comprehend than GOP's behavior.

    posted in technical issues read more
  • jancsika

    I take that back-- you probably can do the responsive thing using [draw g].

    I can give you a demo if you want.

    posted in technical issues read more
  • jancsika

    @th8a Do you want to scale individual widgets-- the way Purr Data does with iemguis?

    Or are you actually talking about a responsive design where the widgets scale and pad themselves accordingly as the viewport itself changes size (e.g., when the user drags the GOP box to scale things)?

    The first option is certainly doable with the [draw] event callbacks. Getting an actual responsive design isn't currently possible with any of the public interfaces provided by Pd or Purr Data. (At least not in a way that you can ship the patch to someone else and have the responsive design work.)

    posted in technical issues read more
  • jancsika

    @th8a I haven't looked closely at what you're doing, but as far as scaling goes:

    [struct blah float x float y]
    
    [nbx]
    |
    [* 0.01]
    |
    [transform scale $1(
    |
    [draw rect 10 10]
    
    [blah]
    

    That will scale a rectangle by the desired scaling factor.

    See doc/4.data.structures/pd-l2ork/ds-tutorials for more features.

    posted in technical issues read more
  • jancsika

    @seb-harmonik.ar What's your process for getting it to compile? Can you do it only using homebrew packages, or did you have to do some manual hacking to get it to compile?

    posted in extra~ read more
  • jancsika

    There's Purr Data, which tries to be backwards compatible with Pd-extended:

    https://github.com/jonwwilkes/purr-data/releases

    However, it doesn't include Gem atm. If you need Gem you can use a recent version of Pd Vanilla (I think it's 0.48).

    posted in technical issues read more
  • jancsika

    i still don't understand how you got the scalars into the patch without any [append] object?

    You can dynamically instantiate scalars with a "scalar" message to a canvas.

    In Purr Data you can create a scalar by typing the name of the template into a box.

    But I haven't looked at the patch yet so I'm not sure if that's how the author is doing it.

    Is it not possible to use [draw] onto a subpatch? It would solve the graphics all over the place issue to just put the scalars into a subpatch with gop on.

    [draw] can be used in the exact same way as [drawpolygon] and friends.

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!