Purr Data finally released
I tried OSx 64 bit version and shortcuts to put objects, put message ... don't work.
get out edit mode either. but if I exit edit mode with mouse, I can use command+1, command+2 again, but once.
seems when I press command key, purr data move out edit mode without "E" key...
@alfonso.santimone I got it compiling but it's not yet loading the subprocess patch. Once I get it working I'll do a bugfix release.
@emviveros Hm, I'll check it out...
Got the same problem as @emviveros, I can't use any shortcuts. I'm running OSx 10.11 64 bit.
Version 2.1.2 doesn't seem to have this problem, so I am currently using that. btw thank you for the huge work for purr data, hoping that this issue will be solved.
@michaelhnc I've got a bugfix release coming out either today or tomorrow.
2.2.1 Bugfix is now available. See links above.
Unfortunately I still haven't fixed the [pd~] bug yet. That will require a bit more work.
@jancsika Keep up the good work ^^
Thanks for your work!!! 
Inspiring!
Thanks @jancsika !
Looking fwd for the [pd~] fix!
best
Hi @jancsika
I just downloaded 2.1.1 for Windows and I can't seem to get [initbang] working. Should I file a bug report?
Yes, it instantiates, but it doesn't seem to send a bang as expected.
@LiamG Fixed for the next release. You can also grab it off the CI builder when it finishes:
https://git.purrdata.net/jwilkes/purr-data/pipelines/872
Just click the relevant OS and then download the "artifact" on the page that pops up.
Don't have Windows in the CI yet, but I'm working on it...
@jancsika I have just upgraded to 2.2.3 win 10 but had a major problem where pd.exe and unins000.dat and unins000.exe were not replaced (install error: could not replace existing file,,,,) and of course the program would not run (pd,exe not found) and no admin powershell or command prompt would allow access to delete.
I reverted to shift restart (safe mode) and command prompt to finally delete the files and complete the install.
I updated because I thought it may have fixed my current problem of $0 in struct names and scalar names not allowing messages to change colours etc. I think you have already addressed this before, but I couldn't find the post. I will move to Purr Data when I can produce a usable $0 abstraction, but so far it has eluded me. Am I doing something wrong?
@Balwyn Should be fixed in the next release. When the CI finishes you can try a binary from it:
@jancsika Thanks for the new 2.2.3 version! I don't see anymore the Win64 version, tho.
best!
@alfonso.santimone You should be able to run the 32-bit version on 64-bit Windows.
The 64-bit version with previous releases was a 64-bit GUI but still a 32-bit Pd engine.
Some more bug fixes with 2.2.4 (see above)
Hey man, Just wanted to say thanks and great work on the latest Purr-data. I am really stoked that development is being actively maintained on a new version of PD. I have noticed a bug/glitch that has been persistent throughout every version of purr-data so far, but cannot seem to find any mention of it anywhere, so I was wondering if this is a known bug or if I have just configured something in my system improperly. The behavior I am talking about is in many of the UI objects being unresponsive. For instance, [nbx] will send floats when clicked and dragged, but the updated value will not be reflected in the UI until the entire window is closed and reopened or resized. Pretty much every UI object does this, nbx, radios, sliders, bang... they work but the UI doesn't budge. I have worked around it by clever use of feeding the output into a send object which labels the object with its current value, or move canvases and structs around to revlect the position of a slider etc, but I admit that gets a bit tiresome. This behavior seems to be especially present in larger projects with multiple levels of GOP subpatches. Any info or insight on what is causing this would be greatly appreciated. Thanks again!
@th8a What's your OS, and does the bug still happen in 2.2.4?
https://git.purrdata.net/jwilkes/purr-data-binaries
If so, can you send me a demo patch that uses the absolute minimum number of objects required to trigger the bug?
By absolute minimum, I mean less than ten objects-- then I'll probably be able to find the cause of the bug in about 5 minutes. I can also try to track it down in a more complex patch but it will take me orders of magnitude longer.
If you come up with a minimal patch to demo the bug post it here or on the issue tracker:
Oops! Looks like something went wrong!
