purr-data issueshttps://git.purrdata.net/jwilkes/purr-data/-/issues2018-12-30T23:36:57Zhttps://git.purrdata.net/jwilkes/purr-data/-/issues/495new build warning in GCC 8 due to -Wcast-function-type2018-12-30T23:36:57ZJonathan Wilkesnew build warning in GCC 8 due to -Wcast-function-typeGCC 8 adds this noisy warning: `warning: cast between incompatible function types from` etc.
This is happening for the t_newmethod cast in `*_setup` functions.GCC 8 adds this noisy warning: `warning: cast between incompatible function types from` etc.
This is happening for the t_newmethod cast in `*_setup` functions.https://git.purrdata.net/jwilkes/purr-data/-/issues/494toplevel makefile light-double recipe broken on OSX2018-12-27T03:01:35ZJonathan Wilkestoplevel makefile light-double recipe broken on OSXIt appears that `make light-double` on OSX produces a binary with PD_FLOATSIZE set to 32.
It should set PD_FLOATSIZE to 64.
Haven't checked the other platforms yet.It appears that `make light-double` on OSX produces a binary with PD_FLOATSIZE set to 32.
It should set PD_FLOATSIZE to 64.
Haven't checked the other platforms yet.Albert GräfAlbert Gräfhttps://git.purrdata.net/jwilkes/purr-data/-/issues/493autotune~ uses float instead of t_sample2019-03-03T17:11:09ZJonathan Wilkesautotune~ uses float instead of t_sampleLooks like `[autotune~]` hard-coded `float` in some places instead of `t_sample`.
Fix this and test to make sure the algo itself doesn't depend on any single-precision float bitmath or anything else like that.Looks like `[autotune~]` hard-coded `float` in some places instead of `t_sample`.
Fix this and test to make sure the algo itself doesn't depend on any single-precision float bitmath or anything else like that.https://git.purrdata.net/jwilkes/purr-data/-/issues/492make light depends on fluid-soundfont-gm and python2018-12-19T23:20:42ZJonathan Wilkesmake light depends on fluid-soundfont-gm and pythonThe light install shouldn't depend on fluid-soundfont-gm and python 2.7. That requires about 120 megs of dependencies that we shouldn't be pulling in for a light install.The light install shouldn't depend on fluid-soundfont-gm and python 2.7. That requires about 120 megs of dependencies that we shouldn't be pulling in for a light install.Albert GräfAlbert Gräfhttps://git.purrdata.net/jwilkes/purr-data/-/issues/491make light2018-12-19T23:24:06ZJonathan Wilkesmake lightfor make light it appears all we need on a debian system are `autoconf` and `rsync`
Also needed for the nw.js gui is libgconf-2-4
Update the docs to make this clear.for make light it appears all we need on a debian system are `autoconf` and `rsync`
Also needed for the nw.js gui is libgconf-2-4
Update the docs to make this clear.Jonathan WilkesJonathan Wilkeshttps://git.purrdata.net/jwilkes/purr-data/-/issues/486Dragging does not work on touchscreen2019-04-15T00:08:10ZVáclav HruškaDragging does not work on touchscreenHi, I am using purr-data on a tablet PC running win10 32-bit. In pure data, i could drag both sliders and numbers to change the values with my finger, now, in purr data, the dragging motion does not do anything. i can only set the slider...Hi, I am using purr-data on a tablet PC running win10 32-bit. In pure data, i could drag both sliders and numbers to change the values with my finger, now, in purr data, the dragging motion does not do anything. i can only set the sliders by clicking when i turn off steady on click.
Would be great if you could look into it, sliders are quite essential for my setup, and i do not want to go back to pure data for various reasons.
Thanks!
Václav Hruška3.0.0https://git.purrdata.net/jwilkes/purr-data/-/issues/479console search does not get updated when new messages arrive2018-07-26T16:04:36ZGilbertoconsole search does not get updated when new messages arriveThe console search feature does not get updated when new messages arrive. If one toggles the highlight all option, any new messages containing the searched string will not be highlighted. The user then must delete the search string and i...The console search feature does not get updated when new messages arrive. If one toggles the highlight all option, any new messages containing the searched string will not be highlighted. The user then must delete the search string and input it again in order to update the search results.https://git.purrdata.net/jwilkes/purr-data/-/issues/478Node Insertion/deletion2018-07-13T15:02:50ZAntonio RobertsNode Insertion/deletionAt the moment their is no easy way to insert nodes between a current connection without cutting the cords and reattaching them with the new nodes. A workaround is to connect all nodes which creates simultaneous connections and can have s...At the moment their is no easy way to insert nodes between a current connection without cutting the cords and reattaching them with the new nodes. A workaround is to connect all nodes which creates simultaneous connections and can have some unintended consequences, as seen below
https://imgur.com/a/1TKDEUQ
What would solve this problem is to have easy code insertion. Inserted nodes would be connected via their hot inlets and outlets. Here's an example from Blender's compositor, where the user holds the Alt whenever they want to insert or detach a node.
https://imgur.com/a/MaXkP6X
In the above example the nodes are connected automatically via their colour coding.
This would especially be useful in live coding/livie noding environments. I wrote a bit about this some years ago https://www.hellocatfood.com/thoughts-on-live-coding-visuals-in-pure-data/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/473font problem in 2.5.1 under ubuntu/xubuntu2018-05-19T01:53:05ZJonathan Wilkesfont problem in 2.5.1 under ubuntu/xubuntuA user has reported some weird font problems like the one below:
![purr-data-ubuntu18.04-fontbug](/uploads/dd9de3354b256d473e00c7ecb43b79e7/purr-data-ubuntu18.04-fontbug.png)
The original report is at the end of this thread on the Pd f...A user has reported some weird font problems like the one below:
![purr-data-ubuntu18.04-fontbug](/uploads/dd9de3354b256d473e00c7ecb43b79e7/purr-data-ubuntu18.04-fontbug.png)
The original report is at the end of this thread on the Pd forum:
https://forum.pdpatchrepo.info/topic/11307/purr-data-2-5-0/65
@aggraef Have you experienced anything like this on Ubuntu?Jonathan WilkesJonathan Wilkeshttps://git.purrdata.net/jwilkes/purr-data/-/issues/470behaviour of [pow] for nans2018-09-13T19:31:01ZAlexandre Porresbehaviour of [pow] for nanshi, I'm checking this discussion https://lists.puredata.info/pipermail/pd-list/2013-04/102309.html
and I agree that there should be no special handling of this case, and that it should output nan instead of 0, like expr doeshi, I'm checking this discussion https://lists.puredata.info/pipermail/pd-list/2013-04/102309.html
and I agree that there should be no special handling of this case, and that it should output nan instead of 0, like expr doeshttps://git.purrdata.net/jwilkes/purr-data/-/issues/469make pow~ deal with negative numbers like pow does2018-09-13T17:35:40ZAlexandre Porresmake pow~ deal with negative numbers like pow does[pow] in purr data handles negative number inputs, but not [pow~]. I see this as an inconsistency as both should behave the same way, one way or another.[pow] in purr data handles negative number inputs, but not [pow~]. I see this as an inconsistency as both should behave the same way, one way or another.https://git.purrdata.net/jwilkes/purr-data/-/issues/466fix/update help file of the [expr] family2018-04-24T18:23:34ZAlexandre Porresfix/update help file of the [expr] familycurrently there's a help file only for [expr], so if you ask for help on [expr~]/[fexpr~] you get only information on [expr].
Don't know if there are special help files for [expr~]/[fexpr~] and they're just not called, but in vanilla th...currently there's a help file only for [expr], so if you ask for help on [expr~]/[fexpr~] you get only information on [expr].
Don't know if there are special help files for [expr~]/[fexpr~] and they're just not called, but in vanilla there's only one help file for the whole family, and it has been largely updated by me in Pd 0.48 and 0.48-1 to include all functionalities.
By the way, Pd 0.48-1 carries a newer version (expr 0.55) than 0.48-0 (expr 0.5).
Seems expr in Purr Data has been updated to 0.55 from 0.48-0, if no further updates are to happen, at least the help files should be upgraded/fixed.
cheershttps://git.purrdata.net/jwilkes/purr-data/-/issues/464[plot] bug - variable distance value doesn't get updated in window2018-04-22T05:07:17ZJoão Pais[plot] bug - variable distance value doesn't get updated in windowwhen a plot has a variable for the distance value and that value is changed, the scalar doesn't refresh the view. close and open the scalar window, and it will be shown correctly.
See the patch attached.
Also another bug there, route lo...when a plot has a variable for the distance value and that value is changed, the scalar doesn't refresh the view. close and open the scalar window, and it will be shown correctly.
See the patch attached.
Also another bug there, route loses pointers?
[distance-bug.pd](/uploads/60a5e7d67950f813cd7585705b05b6bf/distance-bug.pd)https://git.purrdata.net/jwilkes/purr-data/-/issues/463scalar properties window - some details2018-04-22T04:37:02ZJoão Paisscalar properties window - some detailsIn the scalar properties window, it would help to add an "apply" button. Or to use the vanilla behaviour, which only closes the window when "done" is pressed; "save" can be re-used.
Although the vector fields window looks quite nice, wo...In the scalar properties window, it would help to add an "apply" button. Or to use the vanilla behaviour, which only closes the window when "done" is pressed; "save" can be re-used.
Although the vector fields window looks quite nice, would it help to see the vector structure as in vanilla? I can't rememeber the template's structure when checking out scalars, and I try to work regularly with data structures. Maybe an option to show it, or showing it as non-editable text outside the vector area.
It is a bit cumbersome to have to check the "edit vector data" box - the properties window should give immediate access to this information, it is as if it is inside another window.https://git.purrdata.net/jwilkes/purr-data/-/issues/462drawnumber y mirror2018-04-21T21:08:54ZJoão Paisdrawnumber y mirrorIf the X and Y units per pixel of the patch have the opposite signal (x negative and y positive), then the text displayed in scalars will be mirrored as well, making it unreadable. Try this in any patch with [drawnumber] or similar.If the X and Y units per pixel of the patch have the opposite signal (x negative and y positive), then the text displayed in scalars will be mirrored as well, making it unreadable. Try this in any patch with [drawnumber] or similar.https://git.purrdata.net/jwilkes/purr-data/-/issues/461mouse pointer direction reaction to GUI objects (+ drawpolygon corners)2018-04-20T05:43:43ZJoão Paismouse pointer direction reaction to GUI objects (+ drawpolygon corners)In vanilla, the selectable points on scalars (the ones assigned to variables) change the mouse pointer direction when the mouse is over them. It would help if in purr-d the behaviour is the same - for now, the mouse doesn't change.
Come ...In vanilla, the selectable points on scalars (the ones assigned to variables) change the mouse pointer direction when the mouse is over them. It would help if in purr-d the behaviour is the same - for now, the mouse doesn't change.
Come to think of it, only now I notice that the mouse pointer doesn't react to any other gui objects
Also, the polygon's top corner isn't always completely shown, depending on its angle. In vanilla the corners are slightly rounded, in purr they're usually pointy. Move the top corners height to see.
I didn't compare with a polygon, only a filledpolygon.
See attached patch, subpatch graphic2.
[data-s_06-bug.pd](/uploads/2e047b5b046eedd2f6673c3bbce068f5/data-s_06-bug.pd)https://git.purrdata.net/jwilkes/purr-data/-/issues/460"add-to-path" message to Pd & "cyclone solution"2019-10-15T22:41:24ZAlexandre Porres"add-to-path" message to Pd & "cyclone solution"Pd 0.48-0 has a new message that allows us to add things to Pd's search path, see https://github.com/pure-data/pure-data/commit/c917dd1938e8b48927dc6414916bdc47bbcfeb34 I would consider this a bug as Purr Data says it uses 0.48. Now, you...Pd 0.48-0 has a new message that allows us to add things to Pd's search path, see https://github.com/pure-data/pure-data/commit/c917dd1938e8b48927dc6414916bdc47bbcfeb34 I would consider this a bug as Purr Data says it uses 0.48. Now, you might wanna hold this update, as there is still a consistency error popping up, nonetheless, I'd like to have this highlighted.
By the way, current GEM uses this and Cyclone is about to use it to automatically add cyclone's path. This will allow libdir_loader to add cyclone as a library and also add it to the path, which was a problem we were having. This is the perfect solution, as it makes cyclone's installation as we wanted and it doesn't require changes to libdir_loader, etc.
Actually, old GEM in Purr Data already does this, but in an old way. So you can load objects like [gemmouse], which is an abstraction, because GEM's path gets added when the library is loaded via libloader! Hence, if the new way doesn't come soon for Purr Data, we can also do this the old way for the sake of including cyclone.
cheershttps://git.purrdata.net/jwilkes/purr-data/-/issues/459text box display2019-01-27T02:54:40ZJoão Paistext box displayHere are some bugs in text boxes;
��������- when editing the patch, the text box takes up more vertical space than the visible text. This "invisible box" increases with the number of lines. This was a problem in pd-ext, but has been cor...Here are some bugs in text boxes;
��������- when editing the patch, the text box takes up more vertical space than the visible text. This "invisible box" increases with the number of lines. This was a problem in pd-ext, but has been corrected in pd-van;
������- if the font is set to 12 (or a multiple), when editing the display of the text shifts a couple of pixels higher;
���- when opening this patch in pd-van, there are many weird symbols after a semicolon. Correcting the patch in pd-van solves the problem (I copy-pasted the text in here, so you can see them at the start of each line);
��- the font display (and line height?) in pd-van is smaller than in purr
See attached file as well.
[text_comments.pd](/uploads/aada7125192e4b8ecb4f288929715e55/text_comments.pd)https://git.purrdata.net/jwilkes/purr-data/-/issues/458make -nrt flag a noop on Windows/OSX2018-04-12T02:17:53ZJonathan Wilkesmake -nrt flag a noop on Windows/OSXI keep wasting time by erroneously typing the "-nrt" flag on Windows or OSX machine.
On those platforms that flag should simply do nothing. Instead it causes an error and triggers the stderr help.
This is annoying.I keep wasting time by erroneously typing the "-nrt" flag on Windows or OSX machine.
On those platforms that flag should simply do nothing. Instead it causes an error and triggers the stderr help.
This is annoying.