purr-data issueshttps://git.purrdata.net/jwilkes/purr-data/-/issues2022-02-08T17:39:08Zhttps://git.purrdata.net/jwilkes/purr-data/-/issues/856link to self2022-02-08T17:39:08ZJonathan Wilkeslink to selfSince the repo is mirrored at Github, we need a big, bold url at the top of README.md that directs users here.
Cost is that people who have already navigated here might click it to reload, but that's not a big deal.Since the repo is mirrored at Github, we need a big, bold url at the top of README.md that directs users here.
Cost is that people who have already navigated here might click it to reload, but that's not a big deal.https://git.purrdata.net/jwilkes/purr-data/-/issues/674Clicking on the resize text object that is not a GOP still offers a diagonal ...2021-03-29T14:11:19ZIvica BukvicClicking on the resize text object that is not a GOP still offers a diagonal resize in the bottom right corner that results in an error: canvas: no method for '_click_for_resizing'https://git.purrdata.net/jwilkes/purr-data/-/issues/661"inlet: expected x but got y" should name the object that owns it2021-04-21T09:57:28ZJonathan Wilkes"inlet: expected x but got y" should name the object that owns itreplace it with:
"inlet of z: expected x but got y"
where z is the classnamereplace it with:
"inlet of z: expected x but got y"
where z is the classnamehttps://git.purrdata.net/jwilkes/purr-data/-/issues/583update doc/refererence/netsend-help.pd and netreceive-help.pd2020-05-09T01:13:16ZJonathan Wilkesupdate doc/refererence/netsend-help.pd and netreceive-help.pdNetsend and netreceive have xlets so that both objects can send *and* receive messages.
Once connected, they both accept a "send" message to the inlet.
This isn't clear in the help patches for each object so they need to be updated.Netsend and netreceive have xlets so that both objects can send *and* receive messages.
Once connected, they both accept a "send" message to the inlet.
This isn't clear in the help patches for each object so they need to be updated.https://git.purrdata.net/jwilkes/purr-data/-/issues/577Improve the download link in README.md2020-03-13T11:50:50ZJonathan WilkesImprove the download link in README.mdThe download link should point at the OBS binaries for Ubuntu and friends, as those are the most up-to-date packages from Albert.The download link should point at the OBS binaries for Ubuntu and friends, as those are the most up-to-date packages from Albert.https://git.purrdata.net/jwilkes/purr-data/-/issues/551garray_getfloatarray warning is wrong2021-04-02T14:44:17ZJonathan Wilkesgarray_getfloatarray warning is wrongThe [warning](https://git.purrdata.net/jwilkes/purr-data/blob/master/pd/src/g_array.c#L1611) for garray_getfloatarray says:
"warning: extern using garray_getfloatarray() won't work in 64-bit version"
Now that we have begun to support P...The [warning](https://git.purrdata.net/jwilkes/purr-data/blob/master/pd/src/g_array.c#L1611) for garray_getfloatarray says:
"warning: extern using garray_getfloatarray() won't work in 64-bit version"
Now that we have begun to support PD_FLOATSIZE == 64 this is wrong. For example, purr-double running on a 32-bit machine should trigger this warning as well.
Consequently, the warning should be made more precise.https://git.purrdata.net/jwilkes/purr-data/-/issues/546Get rid of legacy -L/sw/lib linker options2019-07-31T22:33:54ZAlbert GräfGet rid of legacy -L/sw/lib linker optionsThis affects macOS only. Some of the externals are littered with these linker options from a bygone era (anyone remember Fink?), which don't serve any purpose any more and cause lots of warnings from the compiler. We can and should get r...This affects macOS only. Some of the externals are littered with these linker options from a bygone era (anyone remember Fink?), which don't serve any purpose any more and cause lots of warnings from the compiler. We can and should get rid of these.https://git.purrdata.net/jwilkes/purr-data/-/issues/543recommend using [declare] in [import] help patch2023-04-04T02:23:22ZJonathan Wilkesrecommend using [declare] in [import] help patch`[declare]` is the standard library loading mechanism. So unless someone needs `[import]` to iterate through the list of loaded libraries `[declare]` should be used.
The help patch for `[import]` should reflect this.`[declare]` is the standard library loading mechanism. So unless someone needs `[import]` to iterate through the list of loaded libraries `[declare]` should be used.
The help patch for `[import]` should reflect this.https://git.purrdata.net/jwilkes/purr-data/-/issues/532switch arg meaning for key, keyname, keyup2020-05-22T10:20:08ZJonathan Wilkesswitch arg meaning for key, keyname, keyupApparently Pd-l2ork 1.0 has autorepeat with `[key]` and no autorepeat with `[key 1]`. But in Purr Data it's reversed.
Change the arg so that "1" means no autorepeat and "0" means autorepeat.
This is a breaking change.Apparently Pd-l2ork 1.0 has autorepeat with `[key]` and no autorepeat with `[key 1]`. But in Purr Data it's reversed.
Change the arg so that "1" means no autorepeat and "0" means autorepeat.
This is a breaking change.3.0.0https://git.purrdata.net/jwilkes/purr-data/-/issues/522Key autorepeat disable option not working on Windows2019-03-25T02:09:36ZIvica BukvicKey autorepeat disable option not working on WindowsThis is on the latest purr-data 2.8.1 and Win 8.1 64bit. Basically optional argument does not disable autorepeat. The help file should be also updated as in pd-l2ork I reversed the behavior to ensure backwards compatibility to no arg bei...This is on the latest purr-data 2.8.1 and Win 8.1 64bit. Basically optional argument does not disable autorepeat. The help file should be also updated as in pd-l2ork I reversed the behavior to ensure backwards compatibility to no arg being autorepeat on. The help file should be also updated accordingly. Hope this helps.https://git.purrdata.net/jwilkes/purr-data/-/issues/521fix background in dmg installer for osx2019-03-19T14:42:04ZJonathan Wilkesfix background in dmg installer for osxFor the OSX dmg installer, the background image isn't getting displayed in the little window where the user drags Purr Data's icon into the Applications folder.
The relevant background image is `purr-data/packages/darwin_app/background....For the OSX dmg installer, the background image isn't getting displayed in the little window where the user drags Purr Data's icon into the Applications folder.
The relevant background image is `purr-data/packages/darwin_app/background.png`
Might want to check both `purr-data/packages/darwin_app/Makefile` as well as the build output to see if there's an error somewhere.https://git.purrdata.net/jwilkes/purr-data/-/issues/516use sys_open and sys_fopen in all relevant places2019-03-08T05:02:34ZJonathan Wilkesuse sys_open and sys_fopen in all relevant placesWe need to do a pass through both the core (`pd/src`) and the externals (`externals`) and replaces syscalls to open and fopen with sys_open and sys_fopen, respectively. (Both are defined in `pd/src/s_path.c`.)
That will ensure the files...We need to do a pass through both the core (`pd/src`) and the externals (`externals`) and replaces syscalls to open and fopen with sys_open and sys_fopen, respectively. (Both are defined in `pd/src/s_path.c`.)
That will ensure the files are opened properly on Windows machines, and with filenames converted properly for non-ASCII characters.
Edit: we initally hooked these in for binbuf_read, but there are other places in the code where we need it.https://git.purrdata.net/jwilkes/purr-data/-/issues/509update build guide2021-03-11T04:31:34ZJonathan Wilkesupdate build guideThe build guide is here:
https://git.purrdata.net/jwilkes/purr-data#build-guide
The first sentence says this:
`The instructions below talk about running the `tar_em_up.sh` build
script, which is still the recommended way to build Purr...The build guide is here:
https://git.purrdata.net/jwilkes/purr-data#build-guide
The first sentence says this:
`The instructions below talk about running the `tar_em_up.sh` build
script, which is still the recommended way to build Purr Data right now.`
It should be changed to this:
`The instructions for Windows and OSX below talk about running the tar_em_up.sh build
script, which is still the recommended way to build Purr Data right now on those platforms.`https://git.purrdata.net/jwilkes/purr-data/-/issues/474move PD_FLOATSIZE message from Pd Window to "About Pd" using [pdinfo]2018-06-01T00:33:52ZJonathan Wilkesmove PD_FLOATSIZE message from Pd Window to "About Pd" using [pdinfo]Currently we've got PD_FLOATSIZE printing out at startup to the Pd Window for easy reference.
Once the core is fully compatible with double precision t_float, we should move the PD_FLOATSIZE to "About Pd." To do this we can easily add a...Currently we've got PD_FLOATSIZE printing out at startup to the Pd Window for easy reference.
Once the core is fully compatible with double precision t_float, we should move the PD_FLOATSIZE to "About Pd." To do this we can easily add a method like "floatsize" to `[pdinfo]`.https://git.purrdata.net/jwilkes/purr-data/-/issues/397s_stuff.h.in is bad2019-03-04T15:26:40ZJonathan Wilkess_stuff.h.in is bad`PD_BUILD_VERSION` needs to be moved from s_stuff.h.in into its own file like s_version.h.in or something.
The problem is that there is a *lot* of other functionality inside s_stuff.h, and a developer (like me) is very likely to just go...`PD_BUILD_VERSION` needs to be moved from s_stuff.h.in into its own file like s_version.h.in or something.
The problem is that there is a *lot* of other functionality inside s_stuff.h, and a developer (like me) is very likely to just go to town on s_stuff.h forgetting that it's generated by s_stuff.h.in.
Then when doing `git status` the changes to s_stuff.h aren't listed in the "Changes not staged for commit." That's because s_stuff.h isn't tracked-- it's auto-generated. That makes it extremely easy to commit, completely forgetting about one's changes to s_stuff.h and consequently losing data.
Alternatively, if you just do `git add .` you'd end up tracking the autogenerated s_stuff.h file and then get confused when those changes end up getting overwritten in the CI by s_stuff.h.in.
Either way, it's way better to cordon off the auto-generated version number into its own header that nobody is ever likely to touch.Jonathan WilkesJonathan Wilkeshttps://git.purrdata.net/jwilkes/purr-data/-/issues/393Dependency problem with libgsl on Kubuntu 17.102019-08-16T05:52:20ZPhilipDependency problem with libgsl on Kubuntu 17.10On artful aardvark there are dependency problems with libgsl:
```
dpkg: dependency problems prevent configuration of pd-l2ork:
pd-l2ork depends on libgsl0ldbl | libgsl2; however:
Package libgsl0ldbl is not installed.
Package libgsl2...On artful aardvark there are dependency problems with libgsl:
```
dpkg: dependency problems prevent configuration of pd-l2ork:
pd-l2ork depends on libgsl0ldbl | libgsl2; however:
Package libgsl0ldbl is not installed.
Package libgsl2 is not installed.
```
The package that is used on 17.10 is libgsl23, so maybe it should be added as an option if API is compatible.https://git.purrdata.net/jwilkes/purr-data/-/issues/391Dependency Problems Building for Raspbian Stretch2018-01-05T23:30:55Zben schmausDependency Problems Building for Raspbian StretchI'm trying to build/install Purr Data following the instructions for GNU/Linux at https://github.com/agraef/purr-data#linux on Raspbian Stretch Lite running LXDE.
The first issue I ran into is that the the following packages could not b...I'm trying to build/install Purr Data following the instructions for GNU/Linux at https://github.com/agraef/purr-data#linux on Raspbian Stretch Lite running LXDE.
The first issue I ran into is that the the following packages could not be located:
```
ladspa-foo-plugins
ubuntustudio-audio-plugins
```
So I removed those libraries and ran into the following conflict, which I have been unable to resolve.
```
The following packages have unmet dependencies:
libjpeg62-turbo : Conflicts: libjpeg62
libmagick++-dev : Depends libmagick++-6.q16-dev but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by help packages.
```
Note that I did try adding the ladspa-foo-plugins PPA by going through the steps at http://kxstudio.linuxaudio.org/Repositories but it still wasn't found there so I just removed those two deps to see if I could install without them.
Any advice is appreciated. Also, if this is better suited to discussion on the mailing list let me know and I'll post there. Thanks.https://git.purrdata.net/jwilkes/purr-data/-/issues/385raspbian missing libgsl0ldbl dependency2018-01-22T18:02:58ZNewkraspbian missing libgsl0ldbl dependencymissing libgsl0ldbl dependency (at repo) when trying to install pd-l2ork-2.4.1-raspbian-armv7l.deb
on latest raspbian.missing libgsl0ldbl dependency (at repo) when trying to install pd-l2ork-2.4.1-raspbian-armv7l.deb
on latest raspbian.https://git.purrdata.net/jwilkes/purr-data/-/issues/290comments should have a dotted box around them in edit mode2021-04-11T15:23:46ZJonathan Wilkescomments should have a dotted box around them in edit mode'nuff said'nuff said