purr-data issueshttps://git.purrdata.net/jwilkes/purr-data/-/issues2022-12-05T01:56:17Zhttps://git.purrdata.net/jwilkes/purr-data/-/issues/876Update list store to latest from vanilla2022-12-05T01:56:17ZAlbert GräfUpdate list store to latest from vanillaThe issue I noticed personally is that the 2017 version of `list store` that we got doesn't support a `get` message with just one index argument. Looking at the [upstream history](https://github.com/pure-data/pure-data/commits/master/src...The issue I noticed personally is that the 2017 version of `list store` that we got doesn't support a `get` message with just one index argument. Looking at the [upstream history](https://github.com/pure-data/pure-data/commits/master/src/x_list.c), I see that this is part of a bunch of other changes by Spacechild1 on Aug 11 2020, as well as various other bugfixes. So we should look at these changes (basically anything committed upstream July 2017 and later), and see what needs to be backported to Purr Data.https://git.purrdata.net/jwilkes/purr-data/-/issues/843nw.js 0.23.7 arm64 not compatible with Ubuntu on the Raspberry Pi2021-04-19T13:47:26ZAlbert Gräfnw.js 0.23.7 arm64 not compatible with Ubuntu on the Raspberry PiIn !766 we added support for building arm64 packages for the Raspberry Pi 3/4 and similar ARM-based 64 bit systems. For this we leverage a build of nw.js 0.23.7 done some time ago by Maurits Lamers, available at https://github.com/Leonar...In !766 we added support for building arm64 packages for the Raspberry Pi 3/4 and similar ARM-based 64 bit systems. For this we leverage a build of nw.js 0.23.7 done some time ago by Maurits Lamers, available at https://github.com/LeonardLaszlo/nw.js-armv7-binaries/releases/tag/v0.23.7.
I've tested the OBS builds on various 64 bit Linux distros for the Pi4 now. While Maurits' package appears to work fine on Debian/Raspbian 10 arm64 systems such as the [Raspbian Buster arm64 beta](https://www.raspberrypi.org/forums/viewtopic.php?t=275370), it is incompatible with the various Ubuntu flavors readily available for the Pi. The error I'm getting there when trying to run purr-data in the terminal is always the same:
~~~
$ purr-data
guidir is /opt/purr-data/lib/pd-l2ork/bin
[0419/002948.525184:WARNING:chrome_main_delegate.cc(569)] final extension:
(nw:4662): Pango-ERROR **: 00:29:49.007: Harfbuzz version too old (1.4.2)
Trace/breakpoint trap (core dumped)
~~~
Leonard Laszlo's own armv7l builds of nw.js (using version 0.27.6) aren't affected by this, so our armv7l builds on the OBS work just fine both in Debian/Raspbian Buster *and* Ubuntu 32 bit ARM systems (tested with Ubuntu Mate 20.04 so far).
I therefore removed the arm64 Ubuntu builds from the [stable OBS channel](https://build.opensuse.org/package/show/home:aggraef/purr-data) again, but they're still available on the [OBS preview channel](https://build.opensuse.org/package/show/home:aggraef:purr-data-git/purr-data) in case anyone wants to fiddle around with them.
Unfortunately, that arm64 nw.js package by Maurits Lamers is a unicorn; there's not a single other arm64 build of nw.js on the Internet that we can use right now. So for the time being that means that if you want to run Purr Data on the Pi under Ubuntu right now, you'll have to stick to the 32 bit variants.
Maybe one day arm64 packages will be offered by https://nwjs.io/ now that these systems are becoming popular, but they've been dragging their feet to officially support ARM for so long, I don't expect that too happen any time soon. So in the (not so) long run, we'll likely have to build our own nw.js arm64 packages if we want to improve the situation. I'm not very much into these low-level things myself, so here's a challenge:
**Build an arm64 version of nw.js** (if possible, close to the 0.28.1 release that we're currently using elsewhere) that works on both Debian/Raspbian 10(+) and **recent Ubuntu releases** for the Raspberry Pi.
This isn't for the faint of heart. While there are some guides to be found on https://github.com/LeonardLaszlo/nw.js-armv7-binaries, and Maurits has documented his progress in [this issue](https://github.com/LeonardLaszlo/nw.js-armv7-binaries/issues/16), the build process is complicated and involves cross-compilation. It also requires substantial resources (cpu, RAM, and harddrive space).
If there's anyone who's willing to give it a whirl, please get in touch or just post to this issue! (Jonathan, we might also consider this as a project in GSoC 2022 if nobody bites before that. I really think that this is important, and will only become more important in the future.)Albert GräfAlbert Gräfhttps://git.purrdata.net/jwilkes/purr-data/-/issues/691Needed: Automatic detection of dependencies on Windows2020-10-07T08:13:38ZAlbert GräfNeeded: Automatic detection of dependencies on WindowsAs #690 shows again, the dependencies of some externals we ship on Windows keep changing. A proper solution is in order, along the lines of the dependencies script that we have on the Mac, which takes care of at least some of the most im...As #690 shows again, the dependencies of some externals we ship on Windows keep changing. A proper solution is in order, along the lines of the dependencies script that we have on the Mac, which takes care of at least some of the most important and problematic externals, in particular Gem and fluid~. (I think that a full-blown dependencies script, like the one we use on the Mac, would be overkill for now, and in any case it would probably be quite slow on the Windows file system.)https://git.purrdata.net/jwilkes/purr-data/-/issues/686text object, message, and comment, when edited are reinstantiated and thrown ...2020-09-23T03:41:39ZIvica Bukvictext object, message, and comment, when edited are reinstantiated and thrown on top of the glist stacktext object, message, and comment, when edited, are reinstantiated and thrown on top of the glist stack which messes with the preset hub instances that rely on externally saved presets and which rely on prerecorded node locations. This r...text object, message, and comment, when edited, are reinstantiated and thrown on top of the glist stack which messes with the preset hub instances that rely on externally saved presets and which rely on prerecorded node locations. This renders saved presets useless. May also need to warn users that to front/to back commands may exacerbate this problem for all objects. May need to be addressed through both retaining the existing object position and improving the hub logic.https://git.purrdata.net/jwilkes/purr-data/-/issues/680pddp link does not always revert to its instantiated format after editing2020-09-02T19:38:02ZIvica Bukvicpddp link does not always revert to its instantiated format after editingIn the about patch, in edit mode, click on a pddp/link, and it will be activated and become editable. If one clicks outside any other object, it will be properly deselected and re-instantiate in its clickable (non-activated) format. Howe...In the about patch, in edit mode, click on a pddp/link, and it will be activated and become editable. If one clicks outside any other object, it will be properly deselected and re-instantiate in its clickable (non-activated) format. However, if while pddp/link is activated, if you click on something else and immediately select it, it will become deselected but its content will remain as if it is in activated mode.https://git.purrdata.net/jwilkes/purr-data/-/issues/678Data dialog issues2020-08-28T04:37:25ZIvica BukvicData dialog issuesData dialog should auto-update when the data structure is manipulated directly. This includes vars and the vector.
The second issue is not entirely clear to me. When editing vector data, are we allowed to add new data or only edit exist...Data dialog should auto-update when the data structure is manipulated directly. This includes vars and the vector.
The second issue is not entirely clear to me. When editing vector data, are we allowed to add new data or only edit existing? If we should be able to add new data, then this is impossible since enter is mapped to the dialog's OK button and this should be fixed. A common way of addressing this is (e.g. via social media platforms) when trying to send a multiline comment, one presses shift+return(or shift+enter) which gives them a newline without sending the message.https://git.purrdata.net/jwilkes/purr-data/-/issues/677Adjusting font size back and forth at a zoom level than default (100%) distor...2020-08-27T05:04:25ZIvica BukvicAdjusting font size back and forth at a zoom level than default (100%) distorts location of objects in gop-enabled subpatches and toplevelsResized GOP windows suddenly lose visibility of its contents (which is expected if it is a subpatch whose font is tied to the parent patch). However, resetting font size does not restore original position. Sometimes objects remain stale ...Resized GOP windows suddenly lose visibility of its contents (which is expected if it is a subpatch whose font is tied to the parent patch). However, resetting font size does not restore original position. Sometimes objects remain stale outside the GOP window and one cannot get rid of them.https://git.purrdata.net/jwilkes/purr-data/-/issues/676Subpatch data scalar toplevel window should rescale its scalars when the wind...2020-08-27T05:02:23ZIvica BukvicSubpatch data scalar toplevel window should rescale its scalars when the window is rescaledOpen disis_wiimote-help.pd and the subpatch for either blobs or joystick and resize it and note that the data scalar does note rescale accordingly.Open disis_wiimote-help.pd and the subpatch for either blobs or joystick and resize it and note that the data scalar does note rescale accordingly.https://git.purrdata.net/jwilkes/purr-data/-/issues/675Selection boxes of data scalars in the GOP-enabled subpatch window are way of...2020-08-27T05:01:23ZIvica BukvicSelection boxes of data scalars in the GOP-enabled subpatch window are way off and correlate to the distance from the top-left corner of the patch windowOpen disis_wiimote-help.pd and open the subpatch with blobs, go to edit mode and try selecting and moving the 4 blobs. This may be related to #647Open disis_wiimote-help.pd and open the subpatch with blobs, go to edit mode and try selecting and moving the 4 blobs. This may be related to #647https://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/6480.47 transition remaining known issues2020-06-17T21:29:30ZIvica Bukvic0.47 transition remaining known issues* it is impossible to move points on toplevel non-joc patches that open with the patch (even if you afterwards close it and reopen it and even change the joc settings) (this is a major issue)
* Need to rework dialog window sizes and mak...* it is impossible to move points on toplevel non-joc patches that open with the patch (even if you afterwards close it and reopen it and even change the joc settings) (this is a major issue)
* Need to rework dialog window sizes and make them fixed in height and width
* Adjust vertical offset for the search box
Also, given the discussion here: https://github.com/nwjs/nw.js/issues/7504 I am now moving from 0.46.2 to the 0.47.0beta1
NB: menu background color now matches that of the OS theme, so it is not changeable.https://git.purrdata.net/jwilkes/purr-data/-/issues/647Remaining issues for the GOP/toplevel Plots2020-08-27T05:01:24ZIvica BukvicRemaining issues for the GOP/toplevel Plots* last element on the plots is not clickable
* make bezier plot look like bezier (may need to leverage curve_path)
* @jwilkes it looks like the elements not being clickable may be linked to the overall miscalculation of the scalar hitbox...* last element on the plots is not clickable
* make bezier plot look like bezier (may need to leverage curve_path)
* @jwilkes it looks like the elements not being clickable may be linked to the overall miscalculation of the scalar hitbox. See disis_wiimote-help.pd patch and open the subpatch with the 4 blobs (found on the right). Selecting each blob creates a much larger selection box than it should and it is larger the more the object is to the right and down. If you position the object the top left corner of the patch screen, its bbox is near perfect. This is clearly a miscalculation/regression from the port to nw.js as this was not an issue before.
I also edited this issue title since it affects all nw.js versions.Ivica BukvicIvica Bukvichttps://git.purrdata.net/jwilkes/purr-data/-/issues/646Different plots inside GOP tend to either overlap or spill over the GOP edges2020-06-17T19:09:03ZIvica BukvicDifferent plots inside GOP tend to either overlap or spill over the GOP edgesSee attached patch. Note that resizing and zooming can also mess with values. I spent probably good 8 hours tracking this issue, so while I am pleased to report I have this fixed, the upcoming commit has some less user-friendly variable ...See attached patch. Note that resizing and zooming can also mess with values. I spent probably good 8 hours tracking this issue, so while I am pleased to report I have this fixed, the upcoming commit has some less user-friendly variable names as a result of the ensuing mental marathon...[test.pd](/uploads/5afba140b088a47d43daab3eab06f0fe/test.pd)Ivica BukvicIvica Bukvichttps://git.purrdata.net/jwilkes/purr-data/-/issues/642Need to find a consistent scaling value for different OSs to ensure that the ...2020-06-08T05:16:14ZIvica BukvicNeed to find a consistent scaling value for different OSs to ensure that the same window size fits the same amount of contentIvica BukvicIvica Bukvic