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" <[email protected]> > > An: "IOhannes m zmoelnig" <[email protected]> > > Cc: "[email protected]" <[email protected]> > > 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 <[email protected]> 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 > > > [email protected] > > > https://lists.puredata.info/listinfo/pd-dev > > > > _______________________________________________ > > Pd-dev mailing list > > [email protected] > > https://lists.puredata.info/listinfo/pd-dev > > > > > > _______________________________________________ > [email protected] mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
