purr-data issueshttps://git.purrdata.net/jwilkes/purr-data/-/issues2020-03-24T17:52:34Zhttps://git.purrdata.net/jwilkes/purr-data/-/issues/602Dragging an object in edit mode at the end of the drag activates it for editing.2020-03-24T17:52:34ZIvica BukvicDragging an object in edit mode at the end of the drag activates it for editing.This destroys the edit flow when trying to drag multiple objects and disables undo drag because the undo tries to change the content of the activated object instead, requiring an additional click to unfocus the object's text. There shoul...This destroys the edit flow when trying to drag multiple objects and disables undo drag because the undo tries to change the content of the activated object instead, requiring an additional click to unfocus the object's text. There should be distinction between click->edit and click+drag->move. I believe 1.x behaves this way but may need to double-check. 2.10. windowshttps://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/379draw image file path2017-11-02T21:31:09Zpatrice coletdraw image file pathI don't know if it's a bug or feature, this would be more consistent with filename appended to path in first argumentI don't know if it's a bug or feature, this would be more consistent with filename appended to path in first argumenthttps://git.purrdata.net/jwilkes/purr-data/-/issues/450drawnumber gui interaction to accept decimal numbers2018-04-11T14:18:18ZJoão Paisdrawnumber gui interaction to accept decimal numberswhen editing a number stored in a drawnumber scalar, be it by typing or mouse-dragging, it's only possible to input whole numbers. Since decimal numbers are accepted, it would make sense to have the same behaviour as in a number atom: ty...when editing a number stored in a drawnumber scalar, be it by typing or mouse-dragging, it's only possible to input whole numbers. Since decimal numbers are accepted, it would make sense to have the same behaviour as in a number atom: type . and input the decimal part, and shift-click goes through the decimal numbers.
This is a new feature also not present in any other pd version, so it would be good to make the code vanilla-compatible (and see if Miller wants to take it in).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/438drawtext not implemented?2019-02-20T05:33:38ZJoão Paisdrawtext not implemented?is [drawtext] not working?
Would it be interesting to add "font" and "size" methods to it?is [drawtext] not working?
Would it be interesting to add "font" and "size" methods to it?2.9.0https://git.purrdata.net/jwilkes/purr-data/-/issues/143dsp on/off shortcuts not working on international keyboards2017-10-16T12:24:20ZAlbert Gräfdsp on/off shortcuts not working on international keyboardsToday I noticed that the dsp on shortcut is not working on the German keyboard where the `/` character is on a shifted key. Digging into this I also found that on the French keyboard *both* `/` and `.` are on shifted keys and neither of ...Today I noticed that the dsp on shortcut is not working on the German keyboard where the `/` character is on a shifted key. Digging into this I also found that on the French keyboard *both* `/` and `.` are on shifted keys and neither of them works in purr-data. In the Tcl GUI (in both vanilla and pd-l2ork) these all work as intended.
These keyboard shortcuts are quite important (especially the dsp off shortcut) and they seem to be a kind of de facto standard (if I recall correctly, they also work the same way in SuperCollider at least). So they are usually among the very first shortcuts that I teach to the students.
Alas, I can't find anything in the nw.js docs about localization of keyboard shortcuts which happen to be punctuation. It does work with some keys (e.g., Ctrl+ +/- do the right thing on my German keyboard), but not with these keys.
The only way I found to work around this (for the German keyboard, where `/` is the shifted `7` key) is by changing the corresponding entry in pd_menus.js as follows:
~~~
media_menu.append(m.media.audio_on = new gui.MenuItem({
label: l("menu.audio_on"),
key: "7",
modifiers: cmd_or_ctrl + "+shift",
tooltip: l("menu.audio_on_tt")
}));
~~~
But this is an awful kludge, and I'd have to reapply it every time I update the purr-data package. Any better idea?https://git.purrdata.net/jwilkes/purr-data/-/issues/197dsp-status method of [pdinfo] doesn't give useful info at loadtime2017-10-16T12:24:18ZJonathan Wilkesdsp-status method of [pdinfo] doesn't give useful info at loadtimeCalling [dsp-status(--[pdinfo] at patch load time gives technically correct yet unhelpful output.
This is because dsp is temporarily suspended when loading a toplevel patch.
Since [dsp-status(--[pdinfo] is likely to be used with [loadb...Calling [dsp-status(--[pdinfo] at patch load time gives technically correct yet unhelpful output.
This is because dsp is temporarily suspended when loading a toplevel patch.
Since [dsp-status(--[pdinfo] is likely to be used with [loadbang] the vast majority of the time, it should have a workable interface that doesn't require adding a [delay 0] to get useful output.
RFC: signal whether dsp is being temporarily suspended in the output for the "dsp-status" method of [pdinfo].
I propose the following four possible outputs for [dsp-status(--[pdinfo]:
1. `-1` means dsp is off and dsp is currently suspended
2. `0` means dsp is off and dsp is not currently suspended
3. `1` means dsp is on and dsp is not currently suspended
4. `2` means dsp is on and dsp is currently suspended
This way the user can just do `[loadbang]--[dsp-status(--[pdinfo]--[> 0]` to get sane default behavior in logical time.
This can be acheived by adding a single field to the pd_this struct and querying it in [pdinfo].Jonathan WilkesJonathan Wilkeshttps://git.purrdata.net/jwilkes/purr-data/-/issues/126dubious conversions in Gem will no longer compile2017-10-16T12:24:19ZJonathan Wilkesdubious conversions in Gem will no longer compileThe newer compiler in msys2 will no longer let Gem compile due to some dubious implicit casting. Probably need to look into bumping the version and see what happensThe newer compiler in msys2 will no longer let Gem compile due to some dubious implicit casting. Probably need to look into bumping the version and see what happensJonathan WilkesJonathan Wilkeshttps://git.purrdata.net/jwilkes/purr-data/-/issues/233edit window in cyclone: coll / capture / capture~2020-04-18T00:06:03ZAlexandre Porresedit window in cyclone: coll / capture / capture~edit window does not work for coll / capture / capture~ or any other that might use it that I dont remember. I'm in Mac Os
trying out the help file for [coll], I tried "load stuff" and then clicked on the object to see the edit window....edit window does not work for coll / capture / capture~ or any other that might use it that I dont remember. I'm in Mac Os
trying out the help file for [coll], I tried "load stuff" and then clicked on the object to see the edit window.
edit window didn't come up, instead I got many errors in the terminal:
"legacy tcl command at 180 of ../shared/hammer/file.c: hammereditor_open .49b2f0 600x600 {coll: /tmp/test.coll} 1
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 {1}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 {,}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 { 10}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 {;...
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 {2}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 {,}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 { some_symbol}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 {;...
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 {3}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 {,}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 { and}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 { another}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 { one}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 { with}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 { 12345}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 { in}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 { it}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 {;...
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 {4}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 {,}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 { this}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 { is}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 { a}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 { message}
legacy tcl command at 220 of ../shared/hammer/file.c: hammereditor_append .49b2f0 {;...
legacy tcl command at 227 of ../shared/hammer/file.c: hammereditor_setdirty .49b2f0 0"https://git.purrdata.net/jwilkes/purr-data/-/issues/581EditMode - Reliability Issues2020-06-11T06:23:24ZJoseph GastelaisEditMode - Reliability IssuesIn add to one of my previous posts (#553 Copy/Paste - Duplicate - Move Weird behavior), I would like to mention 3 new key problems making the daily usage of EditMode a pain.
1. Purr Data doesn't have an '*edit*' indicator in the windows...In add to one of my previous posts (#553 Copy/Paste - Duplicate - Move Weird behavior), I would like to mention 3 new key problems making the daily usage of EditMode a pain.
1. Purr Data doesn't have an '*edit*' indicator in the windows tittle bar like Pure Data when EditMode is turned ON. So each time we have to visit again and again its Edit Menu to check if EditMode is ON or OFF. It's more than boring and not productive at all.
2. Both in patch and subpatch with Edit Mode = ON, when an object is under either the horizontal or vertical scrolling bar a click at this place on the bars will unfortunately select the object-s for edition. This bad behaviour is leading to enormous and continuous edition errors (known and unknown or known but much-much later when trying to understand what was going wrong).
3. At least for the top level parent patch there is not protection - advise against unwanted switch to EditMode = ON. An example among others, with a French AZERTY keyboard and Edit Mode = OFF, 'CTRL' + '-' lead directly to add a [dropdown] object when the expected result was to decrease the zoom level. A patch developer can +/- deal with such kind of behaviour but not standard users of your patch. A security mechanism should be added to the top level parent patch asking confirmation from the user before turning ON or not the EditMode.
I'm using Purr Data v.2.10.0 64-bit under GNU/Linux (Linux Mint 19.3 Cinnamon 64-bit based on Ubuntu 18.04).
I would appreciate a lot if above reliability issues can have a solution.
Thank you.https://git.purrdata.net/jwilkes/purr-data/-/issues/835editmode background doesn't update with GUI presets2021-04-13T16:43:56ZJonathan Wilkeseditmode background doesn't update with GUI presets1. Open a patch in editmode with snap-to-grid enabled.
2. Open prefs
2. Choose a new GUI preset
Bug: the editmode background doesn't update until you toggle editmode *or* you drag the patch window.
Secondary issue-- dang, I guess we're...1. Open a patch in editmode with snap-to-grid enabled.
2. Open prefs
2. Choose a new GUI preset
Bug: the editmode background doesn't update until you toggle editmode *or* you drag the patch window.
Secondary issue-- dang, I guess we're redrawing the editmode background every time we move the window?Jonathan WilkesJonathan Wilkeshttps://git.purrdata.net/jwilkes/purr-data/-/issues/170Empty field in preferences2017-10-16T12:24:19Z60-hzEmpty field in preferencesIn OSX, there is an empty named toggle box under "blocksize" field.
OSX 10.9.5, RC1
![Capture_d_écran_2016-11-25_à_00.07.17](/uploads/2e2acf4996d801f260f60063459466dc/Capture_d_écran_2016-11-25_à_00.07.17.png)In OSX, there is an empty named toggle box under "blocksize" field.
OSX 10.9.5, RC1
![Capture_d_écran_2016-11-25_à_00.07.17](/uploads/2e2acf4996d801f260f60063459466dc/Capture_d_écran_2016-11-25_à_00.07.17.png)https://git.purrdata.net/jwilkes/purr-data/-/issues/719Emscripten Installation: 'update-tags' no longer needed2021-03-15T10:52:32ZSanket Bhukanbsankt16@gmail.comEmscripten Installation: 'update-tags' no longer needed![update_tags](/uploads/b1277560375a548f7455dcaf36f42f23/update_tags.png)![update_tags](/uploads/b1277560375a548f7455dcaf36f42f23/update_tags.png)https://git.purrdata.net/jwilkes/purr-data/-/issues/730Error coming after clicking "Manual " option of Help menu2021-03-16T07:02:08ZGunjan YaduError coming after clicking "Manual " option of Help menuThere is one error message coming in the console after clicking the Manual option of the Help menu, as shown in the screenshot attached.
![Screenshot_from_2021-03-16_12-10-42](/uploads/dcf88baf8574764cc492baeb0fa09036/Screenshot_from_202...There is one error message coming in the console after clicking the Manual option of the Help menu, as shown in the screenshot attached.
![Screenshot_from_2021-03-16_12-10-42](/uploads/dcf88baf8574764cc492baeb0fa09036/Screenshot_from_2021-03-16_12-10-42.png)
The error message is shown below the image.
![Screenshot_from_2021-03-16_12-25-39](/uploads/b40cadd27581c7e468486112926dc6f4/Screenshot_from_2021-03-16_12-25-39.png)
@jwilkes Do we have to attach any doc file? Please let me know so that this issue can be resolved.
Thankshttps://git.purrdata.net/jwilkes/purr-data/-/issues/841Error in Readme file2021-04-20T12:45:57ZSrashti MittalError in Readme fileUser Guide does not open on clicking.User Guide does not open on clicking.https://git.purrdata.net/jwilkes/purr-data/-/issues/526Escape character lost on copy and save.2019-04-09T08:32:16ZArthurEscape character lost on copy and save.I need to be able to escape the comma in message boxes in order the send text, strings including comma's, white space, etc. to a serial port. I can enter a comma with a backslash escape character and this won't break up the message into ...I need to be able to escape the comma in message boxes in order the send text, strings including comma's, white space, etc. to a serial port. I can enter a comma with a backslash escape character and this won't break up the message into multiples. BUT, the backslash gets lost, stripped out on saving the patch or even on copying the message box in patch..
Edit: Purr Data 2.8.1 on Linux
![Screenshot_from_2019-04-07_22-56-05](/uploads/b9265407190be6db87835e5749df8392/Screenshot_from_2019-04-07_22-56-05.png)https://git.purrdata.net/jwilkes/purr-data/-/issues/599Escaping characters in objects2020-03-23T23:33:04ZIvica BukvicEscaping characters in objects[Select \, \;] object properly catches those characters (e.g. when building per-character string). Upon reloading the patch escape '\'s are lost resulting in [Select , ;] object that still works but does not look the same.[Select \, \;] object properly catches those characters (e.g. when building per-character string). Upon reloading the patch escape '\'s are lost resulting in [Select , ;] object that still works but does not look the same.https://git.purrdata.net/jwilkes/purr-data/-/issues/273Escaping of semicolon in post() and error()2017-10-16T12:25:44ZAlbert GräfEscaping of semicolon in post() and error()This is a minor thing I just noticed while playing with my upcoming pd-pure release. Calling post() or error() from C code with a string containing a semicolon, the semicolon gets escaped with a backslash. E.g.:
![error-msg-purr](/uploa...This is a minor thing I just noticed while playing with my upcoming pd-pure release. Calling post() or error() from C code with a string containing a semicolon, the semicolon gets escaped with a backslash. E.g.:
![error-msg-purr](/uploads/b8ba505eb1646e10afea1727b13a020a/error-msg-purr.png)
Note the message "warning: rule never reduced: foo x = bar (x-1)**\;**" there, of course this should actually be "warning: rule never reduced: foo x = bar (x-1)**;**".
Looking at the code of dopost() and doerror() in s_print.c, obviously there is some escaping of FUDI special chars (backslash, curly braces and semicolon) going on there, surely that shouldn't be needed in gui_vmess any more?https://git.purrdata.net/jwilkes/purr-data/-/issues/47estimate time for compilation on each platform2018-01-07T17:58:16ZJonathan Wilkesestimate time for compilation on each platformGive the developer the estimated time it takes to compile Pd on each platform.
For Windows:
1. install msys - 5 minutes
Note: unclick the box that says "run when finished"
2. from start menu, run mingw-64 win32 environment - less t...Give the developer the estimated time it takes to compile Pd on each platform.
For Windows:
1. install msys - 5 minutes
Note: unclick the box that says "run when finished"
2. from start menu, run mingw-64 win32 environment - less than a minute
3. pacman packages - 5 minutes
4. exit - less than a minute
5. download repo - 3 minutes
6. `git submodule init` and `git submodule sync` and `git submodule update` for gem - 3 minutes
7. download and place nw.js binary in pure-data/nw/nw - 5 minutes
7. download asio - less than a minute
8. copy asio - less than a minute
9. remove "flext" from externals/Makefile - 1 minute
9. download nw.js binary, name it "nw", and copy it to purr-data/pd/nw - 3 minutes
10. make install - 45 minutes
fix issue with flextJonathan WilkesJonathan Wilkes