[L2Ork-dev] Purr Data straight patch chords option and disabling grid background

Jonathan Wilkes jon.w.wilkes at gmail.com
Wed Dec 30 15:30:30 EST 2020


On Wed, Dec 30, 2020 at 12:53 PM Lorenzo Sutton
<lorenzofsutton at gmail.com> wrote:
>
> On 29/12/2020 23:54, Jonathan Wilkes wrote:
> > Btw-- just merged a branch into master that changes the grid to a
> > little SVG lock that floats in the top right-hand corner.
> >
> > You can't see it in the help docs, but those all have comments which
> > have a different border in runmode/editmode.
>
> Is the 'straight chords' branch also included?

No, but you do `git pull` on master, you can just do `git merge
master` on the vanilla straight lines branch to bring it in.

Actually, I just did that. So now you should be able to just do `git
pull` on that branch.

> I currently have that one
> installed (btw haven't figured out if there's a way to run a compiled
> version without installing it...)

Yes, there's a wonky way to do it:

1. After you've compiled successfully, go to purr-data/pd/src
2. Open s_inter.c
3. On line 24, remove the empty quotes and uncomment the quoted directory
4. Make sure that directory on line 24 points to the pd/nw directory
that's inside your copy of the repository on your local machine
5. In pd/src, do `make`
6. When it finishes, copy the main binary in purr-data/pd/bin to
wherever the main binary is installed on your machine.
6a. The main binary is usually either installed in /usr/bin, or
/opt/something/something.
6b. The main binary in the installation is usually called
'purr-data'-- if you installed from the OBS repos, for example.
However, the binary compiled in purr-data/pd/bin is usually named
pd-l2ork. (We need to fix that so it's *always* named 'purr-data', but
the build system is monstrous so nobody's attempted it yet.)

I really need to just add a startup flag to sets this directory at runtime.

-Jonathan

>
> Lorenzo.
>
> >
> > -Jonathan
> >
> > On Sat, Dec 26, 2020 at 11:02 AM Jonathan Wilkes <jon.w.wilkes at gmail.com> wrote:
> >>
> >> On Sat, Dec 26, 2020 at 9:50 AM Lorenzo Sutton <lorenzofsutton at gmail.com> wrote:
> >>>
> >>> On 23/12/2020 23:28, Jonathan Wilkes wrote:
> >>>> On Wed, Dec 23, 2020 at 3:20 PM Lorenzo Sutton <lorenzofsutton at gmail.com> wrote:
> >>>>>
> >>>>> On 23/12/2020 18:53, Jonathan Wilkes wrote:
> >>>>>> On Wed, Dec 23, 2020 at 4:05 AM Lorenzo Sutton <lorenzofsutton at gmail.com> wrote:
> >>>>>
> >>>>> [...]
> >>>>>
> >>>> Actually, I could just hard-code straight lines to any GUI preset with
> >>>> "vanilla" in its name:
> >>>>
> >>>> https://git.purrdata.net/jwilkes/purr-data/-/merge_requests/603
> >>>>
> >>>> It's a bit hacky because it won't redraw curved connections if you change
> >>>> the GUI preset with open patches.
> >>>>
> >>>> You're welcome to checkout that branch above and let me know if that works for
> >>>> you. If so we can figure out how to redraw the lines for existing patches and
> >>>> merge it in.
> >>>
> >>> Thanks a lot for looking into this!
> >>>
> >>> I had the time to check it out and compile and it seems to work well. I
> >>> guess linking that behaviour to the theme makes sense...
> >>>
> >>>>>
> >>>>> Ideally this would be somehow also saved in the patch, but not sure how
> >>>>> much complexity that would add.
> >>>>
> >>>> Hard-coding with "vanilla"-substring'd GUI presets solves that issue.
> >>>
> >>> But IIRC the theme is an application-wise setting? Or maybe I
> >>> missunderstood.
> >>
> >> Yes. Per-canvas theming is a more complicated thing, especially given that the
> >> CSS files are such a mess atm.
> >>
> >> -Jonathan
> > _______________________________________________
> > L2Ork-dev mailing list
> > L2Ork-dev at disis.music.vt.edu
> > https://disis.music.vt.edu/listinfo/l2ork-dev
> >
>


More information about the L2Ork-dev mailing list