Howdy all,
Christoph and I have more or less finished some work that updates Pd's networking and also fixes some bugs and a couple pain points:
* IPv6 support
* multicast
* netsend: optional from hostname & port outlet
* netsend: connectionless UDP, no more connection refused (fire & forget without having to manually reconnect)
* netreceive: settable timeout which defaults to 10 seconds (no more super-long frozen Pd)
* improved error printing with netsend and netrceive Find Last Error support
* various small bug fixes (no more polling errors after socket is closed)
The pdsend & pdreceive utils are similarly updated.
The discussion & pull request on Github: https://github.com/pure-data/pure-data/pull/577 <https://github.com/pure-data/pure-data/pull/577>
If you can build Pd and want to try this out, the branch is called feature/netobject-updates
The overall approach taken is to keep IPv4 as default and detect IPv6 addresses so this should not affect existing patches. The IP version handling should also degrade gracefully based if IPv6 is not available. An added bonus is hostnames now resolve (ie. google.com <http://google.com/>) and you can also listen on a hostname if your system can grab it (ie. computername.local).
One current limitation is that Tcl 8.5 does not have IPv6 support, so the core communication with the GUI remains IPv4.
--------
Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>
*Not really feedback, but just a general response.*
One thing I would suggest would be to make this an optional feature in some way. Maybe we can work together with IOhannes and Christof to propose changes to the Pd sources to allow for adding in this kind of functionality without *requiring* it to be built into the core itself. I have been thinking of these kinds of approaches since I see this being a greta feature for the GUI but basically unused for something like libpd. In the latter case, I'd like to simply not compile it and the easiest way would if the main functionality is in a separate set of files that can be left out.
This might be a process that has to happen later on, but something to think of for now in order to balance the addition of new features while maintaining the possibility for a fast, slim core.
> On Jun 10, 2019, at 10:30 AM, pd-dev-request(a)lists.iem.at wrote:
>
> Date: Sun, 9 Jun 2019 19:16:36 +0000
> From: Henri Augusto Bisognini <msndohenri(a)hotmail.com <mailto:msndohenri@hotmail.com>>
> To: "pd-dev(a)lists.iem.at <mailto:pd-dev@lists.iem.at>" <pd-dev(a)lists.iem.at <mailto:pd-dev@lists.iem.at>>
> Subject: Re: [PD-dev] First complete keyboard navigation prototype
> Message-ID:
> <CP2PR80MB0386C0D2C66D1CE34F458BE3CC120(a)CP2PR80MB0386.lamprd80.prod.outlook.com <mailto:CP2PR80MB0386C0D2C66D1CE34F458BE3CC120@CP2PR80MB0386.lamprd80.prod.outlook.com>>
>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Thanks Christof! Indeed it's already been very nice to use it during my tests.
>
> I'l probably wrap up a small file containing some basic infos about how everything works to make it easier for more people to modify the code and test ideas.
--------
Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>
i wonder whether we should switch the official bug-reporting page of Pd
to the issue-tracker at github.
whenever you go to "Help->Report a bug", a browser will go and open the
web-page http://bugs.puredata.info/
This page currently redirects to the sourceforge bug-tracker:
https://sourceforge.net/p/pure-data/bugs/
however, practically all activity in Pd-development has moved from
sourceforge to github, and a lot of people are using the github issues.
so I wondered whether we should direct the people to the github tracker
instead.
afaict, there's a single drawback with github as compared to
sourceforge: you must have a github account in order to be able to
report issues. (on sourceforge, you can create tickets anonymously).
the implementation is simple: i just need to set the redirect on the
puredata.info webserver.
however I would like to have consensus first, that this is actually a
good idea.
gmdasr
IOhannes
---
** [bugs:#1319] Escaped spaces not written to patch file**
**Status:** open
**v0.49:** v0.49
**Created:** Sun Oct 06, 2019 06:30 PM UTC by Anonymous
**Last Updated:** Sun Oct 06, 2019 06:30 PM UTC
**Owner:** nobody
When I am entering my escaped spaces it looks like this:
![image|312x36](https://aws1.discourse-cdn.com/standard17/uploads/critterandguitari/original/2X/9/9b47a3d1354251f56608c3d6c447a8207a82ace5.png)
And upon removing focus from the message block, the \ characters remain there…
![image|310x35](https://aws1.discourse-cdn.com/standard17/uploads/critterandguitari/original/2X/d/d452cffad9b86cfbebdfddd744987e985dd02391.png)
Now, upon saving my patch, i can open it in a text editor and see that my escape are gone!
#X msg 341 60 set Octave transpose %d;
After loading my patch the escapes are not present…
![image|288x36](https://aws1.discourse-cdn.com/standard17/uploads/critterandguitari/original/2X/9/9671b98a47cb0529e3cb02c9a65d880fd865aecd.png)
HOWEVER
If I manually add the escapes in the patch, it works!
#X msg 341 60 set Octave\ transpose\ %d;
---
Sent from sourceforge.net because pd-dev(a)lists.iem.at is subscribed to https://sourceforge.net/p/pure-data/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/pure-data/admin/bugs/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
> Am 15. September 2019 19:46:10 MESZ schrieb jakob skouborg <syntaxerror60(a)hotmail.com <mailto:syntaxerror60@hotmail.com>>:
>>
>> What are your thoughts about this?
>>
>
> to be honest, i didnt even notice.
> usually, if i "save as" any suggested filename is wrong.
One reason this was changed, I believe, is that some people were accidentally overwriting there patches when they forgot to change the original name.
When you don't want to change the name, you'd use "Save" or at least that makes sense to me.
> the only suggestion i think "wrongest" would be "Copy of <orgname>.pd"
Hah, most macOS apps now make a "duplicate" named "<orgname> copy".
--------
Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>
I think that the actual answer is: there is no rationale, it's a bug.
I can't think of anything else, other than the possible reason I came upon with earlier which was pointed out as wrong anyway. It might have been something introduced when we were doing some updates to the Pd GUI. If I find anything more, I will respond to the Github issue.
> On Sep 18, 2019, at 9:26 PM, pd-dev-request(a)lists.iem.at wrote:
>
> Anyway, I am just curious about that the rationale is for starting from “untitled”,
> instead of last saved name? Cause to me it doesn’t make sense at all.
--------
Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>
Done!
Thank you for the hint, Antoine ;)
Jakob
https://github.com/pure-data/pure-data/issues/746
On 18 Sep 2019, at 20:47, Antoine Rousseau <antoine(a)metalu.net<mailto:antoine@metalu.net>> wrote:
Regarding the bug report, you can just fill a new issue in the github repo: https://github.com/pure-data/pure-data
Antoine
Le mer. 18 sept. 2019 à 19:57, jakob skouborg <syntaxerror60(a)hotmail.com<mailto:syntaxerror60@hotmail.com>> a écrit :
> I have to agree - I'm used to having the "save as" start up with the existing
> filename, with the text selected so that you can just type in a new one from
> scratch, or hit the right-arrow to just edit the last letter or digit of the
> name.
Yes, to me that makes the most sense too, rather than starting from “untitled”.
>> I hope we all agree on that :-) "save as" should start at the current file name, that's the convention and IMO there's absolutely no reason for doing it differently. As people have already noted, the "save as" dialog will already warn you when you try to overwrite an existing file.
>>
>> I would do a PR but I'm busy right now. You might file a bug report, so we don't forget.
>>
>> Christof
Thanks, I will do the bug report. I actually already did that long time ago, but it was closed it pretty much right away.
I don’t remember how to do the bug report, but I will find out again and do it ASAP.
Thanks for the understanding and have a great day!
Jakob
> On 18 Sep 2019, at 19:54, Miller Puckette <msp(a)ucsd.edu<mailto:msp@ucsd.edu>> wrote:
>
> I have to agree - I'm used to having the "save as" start up with the existing
> filename, with the text selected so that you can just type in a new one from
> scratch, or hit the right-arrow to just edit the last letter or digit of the
> name.
>
> Git's cool, but when I'm working with others the name+number convention
> often helps a lot.
>
> cheers
> Miller
>
> On Wed, Sep 18, 2019 at 07:50:36PM +0200, Christof Ressi wrote:
>>> Cause to me it doesn???t make sense at all.
>>
>> I hope we all agree on that :-) "save as" should start at the current file name, that's the convention and IMO there's absolutely no reason for doing it differently. As people have already noted, the "save as" dialog will already warn you when you try to overwrite an existing file.
>>
>> I would do a PR but I'm busy right now. You might file a bug report, so we don't forget.
>>
>> Christof
>>
>>> Gesendet: Mittwoch, 18. September 2019 um 19:26 Uhr
>>> Von: "jakob skouborg" <syntaxerror60(a)hotmail.com<mailto:syntaxerror60@hotmail.com>>
>>> An: "IOhannes m zmoelnig" <zmoelnig(a)iem.at<mailto:zmoelnig@iem.at>>
>>> Cc: "Pd-dev(a)lists.iem.at<mailto:Pd-dev@lists.iem.at>" <Pd-dev(a)lists.iem.at<mailto:Pd-dev@lists.iem.at>>
>>> Betreff: Re: [PD-dev] Naming of patch when doing a "save as"
>>>
>>>
>>>
>>>
>>>> the days of "Copy of Copy of Kopie von Comb filter 1.2 (17.12.1997)
>>>> final copy.pd" ought to be gone for good.
>>>
>>> That is not what what I am saying or expecting.
>>>
>>> It is really very simple, just start from the name of last time the patch was saved,
>>> like basically any other app in the world does today. Then anyone can write what
>>> they want from there.
>>>
>>>
>>>> if you want to do versioning of patches, you probably should look into a
>>>> proper version-control-system, like 'git'.
>>>> seriously.
>>>
>>>
>>> I think that is overcomplicating the "save as" function a little bit.
>>>
>>>
>>>> and while i still don't have much of an opinion about the suggested
>>>> filename, i think that the suggestion shouldn't contain spaces at all
>>>> (alternatively you find a simple way to load abstractions with spaces in
>>>> their name).
>>>
>>>
>>> The name heres was just an example.
>>>
>>> Of course I call abstractions something else, without spaces.
>>>
>>> I am talking about main/master patches. All though you can still call them ???Patchname1???, etc.
>>>
>>> Anyway, I am just curious about that the rationale is for starting from ???untitled???,
>>> instead of last saved name? Cause to me it doesn???t make sense at all.
>>>
>>> Cheers!
>>>
>>>
>>>
>>>> On 17 Sep 2019, at 10:00, IOhannes m zmoelnig <zmoelnig(a)iem.at<mailto:zmoelnig@iem.at>> wrote:
>>>>
>>>> On 16.09.19 18:05, jakob skouborg wrote:
>>>>>
>>>>> I often do a lot of versioning when making complex patches, to avoid
>>>>> ruining them. So most of my patches have numbers included.
>>>>>
>>>>> Like for example "Comb filter 1.0???
>>>>
>>>> ah yes, *that* use-case.
>>>>
>>>> if you want to do versioning of patches, you probably should look into a
>>>> proper version-control-system, like 'git'.
>>>> seriously.
>>>> the days of "Copy of Copy of Kopie von Comb filter 1.2 (17.12.1997)
>>>> final copy.pd" ought to be gone for good.
>>>>
>>>>
>>>> and while i still don't have much of an opinion about the suggested
>>>> filename, i think that the suggestion shouldn't contain spaces at all
>>>> (alternatively you find a simple way to load abstractions with spaces in
>>>> their name).
>>>>
>>>> gmasdr
>>>> IOhannes
>>>>
>>>> _______________________________________________
>>>> Pd-dev mailing list
>>>> Pd-dev(a)lists.iem.at<mailto:Pd-dev@lists.iem.at>
>>>> https://lists.puredata.info/listinfo/pd-dev
>>>
>>> _______________________________________________
>>> Pd-dev mailing list
>>> Pd-dev(a)lists.iem.at<mailto:Pd-dev@lists.iem.at>
>>> https://lists.puredata.info/listinfo/pd-dev
>>>
>>
>>
>>
>> _______________________________________________
>> Pd-list(a)lists.iem.at<mailto:Pd-list@lists.iem.at> mailing list
>> UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
_______________________________________________
Pd-dev mailing list
Pd-dev(a)lists.iem.at<mailto:Pd-dev@lists.iem.at>
https://lists.puredata.info/listinfo/pd-dev