purr-data issueshttps://git.purrdata.net/jwilkes/purr-data/-/issues2018-01-07T17:58:16Zhttps://git.purrdata.net/jwilkes/purr-data/-/issues/74windows binary is missing libftgl-2.dll2018-01-07T17:58:16ZJonathan Wilkeswindows binary is missing libftgl-2.dll... and probably some other Gem dependencies.... and probably some other Gem dependencies.Jonathan WilkesJonathan Wilkeshttps://git.purrdata.net/jwilkes/purr-data/-/issues/53windows build needs to copy nw.js binary to build directory2018-01-07T17:58:16ZJonathan Wilkeswindows build needs to copy nw.js binary to build directorysee titlesee titleJonathan WilkesJonathan Wilkeshttps://git.purrdata.net/jwilkes/purr-data/-/issues/54windows build needs to copy pd/nw into build/bin2018-01-07T17:58:16ZJonathan Wilkeswindows build needs to copy pd/nw into build/binsee titlesee titleJonathan WilkesJonathan Wilkeshttps://git.purrdata.net/jwilkes/purr-data/-/issues/418windows innosetup failure should break build2018-03-12T21:23:41ZJonathan Wilkeswindows innosetup failure should break buildIf innosetup fails, then the *entire* build should break and CI should fail.
Btw-- if *any* part of the monstrous build system fails and that part isn't one of the lines of shell prepended with a `-`, the entire build should fail.
Is t...If innosetup fails, then the *entire* build should break and CI should fail.
Btw-- if *any* part of the monstrous build system fails and that part isn't one of the lines of shell prepended with a `-`, the entire build should fail.
Is there some tractable way to make this so?https://git.purrdata.net/jwilkes/purr-data/-/issues/366windows installer doesn't use pd icon in control panel2018-03-01T01:03:53ZJonathan Wilkeswindows installer doesn't use pd icon in control panel1. Need to change `packages/win32_inno/pd.ico` from the Pd-extended graphic to a Purr Data cat graphic.
2. Need to add directive to packages/win32_inno/pd-inno.iss.in to display the proper Purr Data icon in the uninstaller:
http://www.j...1. Need to change `packages/win32_inno/pd.ico` from the Pd-extended graphic to a Purr Data cat graphic.
2. Need to add directive to packages/win32_inno/pd-inno.iss.in to display the proper Purr Data icon in the uninstaller:
http://www.jrsoftware.org/ishelp/index.php?topic=setup_uninstalldisplayiconhttps://git.purrdata.net/jwilkes/purr-data/-/issues/544Windows/msys2 compilation problems2019-07-30T20:29:46ZAlbert GräfWindows/msys2 compilation problemsOn the latest msys2/mingw (fully updated) I'm getting this error:
~~~
cd /home/ag/purr-data/externals/OSCx && ./configure
configure: loading site script /mingw32/etc/config.site
checking build system type... i686-w64-mingw32
checking ho...On the latest msys2/mingw (fully updated) I'm getting this error:
~~~
cd /home/ag/purr-data/externals/OSCx && ./configure
configure: loading site script /mingw32/etc/config.site
checking build system type... i686-w64-mingw32
checking host system type... i686-w64-mingw32
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/home/ag/purr-data/externals/OSCx':
configure: error: C compiler cannot create executables
See `config.log' for more details
make[3]: *** [Makefile:1362: /home/ag/purr-data/externals/OSCx/Makefile] Error 77
make[3]: Leaving directory '/home/ag/purr-data/externals'
make[2]: *** [Makefile:209: externals_install] Error 2
make[2]: Leaving directory '/home/ag/purr-data/packages'
make[1]: *** [Makefile:69: prebuilt_install] Error 2
make[1]: Leaving directory '/home/ag/purr-data/packages/win32_inno'
~~~
config.log shows:
~~~
configure:2634: gcc -DPD -I/home/ag/purr-data/pd/src -Wall -W -Wno-unused-parameter -ggdb -I/home/ag/purr-data/Gem/src -mms-bitfields -DMSW -DNT -D'O_NONBLOCK=1' -D'srand48(n)=srand((n))' -D'drand48()=((double)rand()/RAND_MAX)' -D'bzero(p,n)=memset(p,0,n)' conftest.c >&5
<command-line>: error: macro names must be identifiers
<command-line>: error: macro names must be identifiers
<command-line>: error: macro names must be identifiers
<command-line>: error: macro names must be identifiers
configure:2638: $? = 1
configure:2676: result: no
~~~
This is 100% reproducible for me. I'm not sure why we don't see these in the Windows runner, maybe it uses an older version of the msys2 base system?
Anyway, I can get rid of this error simply by removing the definitions `-D'srand48(n)=srand((n))'` and `-D'drand48()=((double)rand()/RAND_MAX)' -D'bzero(p,n)=memset(p,0,n)'` from the `WINDOWS_HACKS` variable in externals/Makefile, i.e.:
~~~diff
diff --git a/externals/Makefile b/externals/Makefile
index a193a457..ef699e9c 100644
--- a/externals/Makefile
+++ b/externals/Makefile
@@ -73,8 +73,9 @@ ifeq ($(OS_NAME),linux)
endif
ifeq ($(OS_NAME),windows)
BUILDSRC_OS_NAME = win
- WINDOWS_HACKS = -D'O_NONBLOCK=1' -D'srand48(n)=srand((n))' \
- -D'drand48()=((double)rand()/RAND_MAX)' -D'bzero(p,n)=memset(p,0,n)'
+ WINDOWS_HACKS = -DO_NONBLOCK=1
+# -D'srand48(n)=srand((n))' \
+# -D'drand48()=((double)rand()/RAND_MAX)' -D'bzero(p,n)=memset(p,0,n)'
# These don't seem to be needed:
# -D'PROT_READ=1' \
# -D'MAP_PRIVATE=2' \
~~~
Should I submit this as a merge request so that we can see whether this breaks the Windows runner? It goes without saying that having to patch up the sources each time I try to build the Windows version is a bit inconvenient, and other users might run into this issue as well, thus the sooner we can get rid of these Windows-specific hacks the better.Jonathan WilkesJonathan Wilkeshttps://git.purrdata.net/jwilkes/purr-data/-/issues/304windows: when zoomed in, context menus appear in the wrong place2017-04-05T04:04:13ZEsa Ruohowindows: when zoomed in, context menus appear in the wrong place![context_menu_in_the_wrong_place](/uploads/83339e8d8c24ff82b7613fa0dc1ccaba/context_menu_in_the_wrong_place.png)
if i am zoomed in a bit, or a lot, and i rightclick on an atom, the context menu appears in the wrong place, slightly to t...![context_menu_in_the_wrong_place](/uploads/83339e8d8c24ff82b7613fa0dc1ccaba/context_menu_in_the_wrong_place.png)
if i am zoomed in a bit, or a lot, and i rightclick on an atom, the context menu appears in the wrong place, slightly to the left or even a lot to the left. can this be addressed?https://git.purrdata.net/jwilkes/purr-data/-/issues/507wireless object navigation2019-02-13T19:52:44ZJonathan Wilkeswireless object navigationGo ahead and implement this:
https://git.purrdata.net/jwilkes/summer-of-code-ideas-list#navigation-of-wireless-objects
It's currently in the GSoC list but should be removed because it's too easy a project:
1. Add a global pd receiver ...Go ahead and implement this:
https://git.purrdata.net/jwilkes/summer-of-code-ideas-list#navigation-of-wireless-objects
It's currently in the GSoC list but should be removed because it's too easy a project:
1. Add a global pd receiver named something like "debug_symbol $symbol $classname"
2. Add to m_pd.c: `bindlist_print(t_symbol *s, t_symbol *classname);`
3. Have bindlist_print send to the GUI an array of gui_x(pd) which are part of the s->s_thing bindlist that match the classname given. If there's only one pd behind the s_thing that matches then send it as an array with a single element. If there's nothing then send an empty array. If there's no classname argument given, just spit out all the elements of the bindlist.
4. In the GUI, receive the array and print to console a) the classname and binding symbol, b) the length of the array, c) each matching object, hyperlinked like pd_error does so that the user can click and navigate to the object. Could even make a little slider widget to scrub among them, or possibly a toggled hyperlink where you can mouse over a series of "1 2 3 4 5" links to highlight each object.
5. For send/receive/catch/etc., hyperlink the first argument in the GUI so that clicking it calls "debug_symbol $symbol $classname"
That should pretty much do it.Jonathan WilkesJonathan Wilkeshttps://git.purrdata.net/jwilkes/purr-data/-/issues/348wrap~ is buggy and consistent to wrap2017-08-23T19:02:43ZAlexandre Porreswrap~ is buggy and consistent to wrap[wrap~] has a bug, when you feed it "0", it becomes "1", unlike [wrap], which outputs 0. As a workaround, I need to use 2 [wrap~] object so I can turn the generated "1" back to zero.
The code is different of course, and it's better and ...[wrap~] has a bug, when you feed it "0", it becomes "1", unlike [wrap], which outputs 0. As a workaround, I need to use 2 [wrap~] object so I can turn the generated "1" back to zero.
The code is different of course, and it's better and right in wrap, so maybe just change wrap~ to include the way wrap calculates it
like:
while (n--)
{
t_sample f = *in++;
*out++ = f - floor(f);
}
return (w + 4);https://git.purrdata.net/jwilkes/purr-data/-/issues/600Write command to coll object generates error when coll is empty. Need a more ...2020-03-26T00:24:31ZIvica BukvicWrite command to coll object generates error when coll is empty. Need a more informative message here and probably avoid calling it an error.https://git.purrdata.net/jwilkes/purr-data/-/issues/308write purr-data linux build instructions instead of linking to pd-l2ork ones2017-04-11T01:21:42ZJonathan Wilkeswrite purr-data linux build instructions instead of linking to pd-l2ork onesThe build instructions for Purr Data on linux link to the Pd-l2ork 1.0 instructions. This is confusing because the user ends up downloading the wrong repo.
We need step-by-step instructions for the linux install, just like the other pla...The build instructions for Purr Data on linux link to the Pd-l2ork 1.0 instructions. This is confusing because the user ends up downloading the wrong repo.
We need step-by-step instructions for the linux install, just like the other platforms.https://git.purrdata.net/jwilkes/purr-data/-/issues/203Wrong ALSA MIDI setup after startup2017-10-16T12:24:19ZAlbert GräfWrong ALSA MIDI setup after startupOn Linux, the preferences dialog always shows 0 MIDI devices after startup, even though the MIDI config is properly recorded in the user-settings file and the right number of ALSA sequencer ports is created at startup. The proper number ...On Linux, the preferences dialog always shows 0 MIDI devices after startup, even though the MIDI config is properly recorded in the user-settings file and the right number of ALSA sequencer ports is created at startup. The proper number of ALSA sequencer ports is only shown after switching the MIDI API.
This is obviously due to the fact that s_midi_alsa.c keeps track of the number of MIDI ports in two different sets of state variables. The secondary one, being used by the GUI via midi_alsa_getdevs, isn't properly initialized (it's only updated via midi_alsa_setndevs after switching MIDI APIs, but not when the MIDI devices are first opened).https://git.purrdata.net/jwilkes/purr-data/-/issues/792Wrong comment syntax in CSS files2021-04-10T17:39:53ZPrakhar AgarwalWrong comment syntax in CSS filesIn the CSS files wrong syntax for comments is used which can cause bugs.For eg., "//" is used instead of "/**/" for commenting.In the CSS files wrong syntax for comments is used which can cause bugs.For eg., "//" is used instead of "/**/" for commenting.https://git.purrdata.net/jwilkes/purr-data/-/issues/270wrong date/rev number when building after `git pull`2017-03-23T02:40:46ZJonathan Wilkeswrong date/rev number when building after `git pull`If I `git pull` new code on Tuesday after having successfully build Purr Data on Monday, the binary I get on Windows still has the date/rev from Monday's repository state.If I `git pull` new code on Tuesday after having successfully build Purr Data on Monday, the binary I get on Windows still has the date/rev from Monday's repository state.https://git.purrdata.net/jwilkes/purr-data/-/issues/791Wrong naming of the resulting abstraction after "save as" subpatches2021-04-01T20:24:47ZGabriela BittencourtWrong naming of the resulting abstraction after "save as" subpatchesThe [improving abstractions feature](https://git.purrdata.net/jwilkes/purr-data/-/merge_requests/500
) developed in the GSOC2020 wrongly name the resulting objects after the "save as" operation: it kept the '.pd' suffix, resulting in the...The [improving abstractions feature](https://git.purrdata.net/jwilkes/purr-data/-/merge_requests/500
) developed in the GSOC2020 wrongly name the resulting objects after the "save as" operation: it kept the '.pd' suffix, resulting in the "couldn't create object" error.
![image](/uploads/043f5965022f25db4f753f916facfef1/image.png)https://git.purrdata.net/jwilkes/purr-data/-/issues/639Zexy not included as part of the default libraries2020-06-05T22:23:24ZIvica BukvicZexy not included as part of the default librariesBreaks pd-l2ork 1.x compatibility and the K12 modeBreaks pd-l2ork 1.x compatibility and the K12 modehttps://git.purrdata.net/jwilkes/purr-data/-/issues/106zombie pd processes can get created2017-10-16T12:24:19ZJonathan Wilkeszombie pd processes can get createdCurrently you can only have a single instance of Purr Data running. If you try to create another, an additional Pd process will get instantiated (with no gui), but it won't go away when you close the original instance.Currently you can only have a single instance of Purr Data running. If you try to create another, an additional Pd process will get instantiated (with no gui), but it won't go away when you close the original instance.Jonathan WilkesJonathan Wilkeshttps://git.purrdata.net/jwilkes/purr-data/-/issues/823Zoom In option not working2021-05-19T07:42:50ZPrakhar AgarwalZoom In option not workingZoom In menu option is not working. Click on "View->Zoom In" and see that zoom in is not workingZoom In menu option is not working. Click on "View->Zoom In" and see that zoom in is not workinghttps://git.purrdata.net/jwilkes/purr-data/-/issues/822Zoom Out option not working2021-05-19T07:42:52ZPrakhar AgarwalZoom Out option not workingZoom out menu option is not working. Click on "View->Zoom out" and see that reset zoom is not workingZoom out menu option is not working. Click on "View->Zoom out" and see that reset zoom is not working