Hi,
sorry for calling this in late, but i only recently changed completely to PD 0.49 ...
i noticed a new patching "feature" that irritates me a lot.
if multiple objects are selected and i connect one of them with a new object (i.e. a number box), ALL of those still selected objects will create a new connection. (see attached patch)
while i guess that there must be some sort of use case for this behaviour (though none comes to my mind), still i would like to turn this feature off with a flag or something, as it messes up my workflow pretty good and results in many unnecessary extra mouse clicks.
sorry if i missed something in the discussion regarding new patching features.
any help appreciated
best
oliver
On 07.03.19 08:14, oliver wrote:
sorry if i missed something in the discussion regarding new patching features.
see https://github.com/pure-data/pure-data/issues/547
any help appreciated
Ctrl-Z
fmgasdr IOhannes
- oliver oliver@klingt.org [2019-03-07 08:15]:
Hi,
sorry for calling this in late, but i only recently changed completely to PD 0.49 ...
i noticed a new patching "feature" that irritates me a lot.
if multiple objects are selected and i connect one of them with a new object (i.e. a number box), ALL of those still selected objects will create a new connection. (see attached patch)
As you say this is considered a feature by most users. It annoys me more often than I find it useful and would have prefered to have it as an opt-in feature where, when multiple objects are selected, I would have to hold down shift while connecting patch cords to inlets to have them fanned out automatically. Right now I feel I have to more intelligent than before to avoid accidental connections. Seems to be a matter of taste to have it in and enabled without modifier keys.
Now pd has this startup flag -noautopatch though I am not sure if this applied to the newest intelligent patching™ additions.
while i guess that there must be some sort of use case for this behaviour (though none comes to my mind), still i would like to turn this feature off with a flag or something, as it messes up my workflow pretty good and results in many unnecessary extra mouse clicks.
sorry if i missed something in the discussion regarding new patching features.
Goes on from here https://lists.puredata.info/pipermail/pd-list/2018-06/122789.html
It annoys me more often than I find it useful and would > have prefered to have it as an opt-in feature
Me too!
Gesendet: Donnerstag, 07. März 2019 um 09:31 Uhr Von: "Peter P." peterparker@fastmail.com An: pd-list@lists.iem.at Betreff: Re: [PD] PD 0.49 - turn off multiple connections ? ...
- oliver oliver@klingt.org [2019-03-07 08:15]:
Hi,
sorry for calling this in late, but i only recently changed completely to PD 0.49 ...
i noticed a new patching "feature" that irritates me a lot.
if multiple objects are selected and i connect one of them with a new object (i.e. a number box), ALL of those still selected objects will create a new connection. (see attached patch)
As you say this is considered a feature by most users. It annoys me more often than I find it useful and would have prefered to have it as an opt-in feature where, when multiple objects are selected, I would have to hold down shift while connecting patch cords to inlets to have them fanned out automatically. Right now I feel I have to more intelligent than before to avoid accidental connections. Seems to be a matter of taste to have it in and enabled without modifier keys.
Now pd has this startup flag -noautopatch though I am not sure if this applied to the newest intelligent patching™ additions.
while i guess that there must be some sort of use case for this behaviour (though none comes to my mind), still i would like to turn this feature off with a flag or something, as it messes up my workflow pretty good and results in many unnecessary extra mouse clicks.
sorry if i missed something in the discussion regarding new patching features.
Goes on from here https://lists.puredata.info/pipermail/pd-list/2018-06/122789.html
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 07.03.19 09:47, Christof Ressi wrote:
It annoys me more often than I find it useful and would have prefered to have it as an opt-in feature
Me too!
how about creating a ticket on [1]? Bug #547 (which i linked earlier) is *related* but not exactly the same.
On 07.03.19 09:31, Peter P. wrote:> Now pd has this startup flag
-noautopatch though I am not sure if this applied to the newest intelligent patching™ additions.
totally not. (as in: no this flag is currently not honoured; and i'm pretty much opposed to a cmdline flag to turn any patching feature that is only sometimes useful globally on/off)
fgaskdr IOhannes
- IOhannes m zmoelnig zmoelnig@iem.at [2019-03-07 09:57]:
On 07.03.19 09:47, Christof Ressi wrote:
It annoys me more often than I find it useful and would have prefered to have it as an opt-in feature
Me too!
how about creating a ticket on [1]?
Done! Thanks IO! https://github.com/pure-data/pure-data/issues/568
I figure and assume you all know, but clicking unselects all the objects so you can make a single connection if you will. And there's always control-z until that becomes a new habit.
I personally love all the new autopatching features and I almost cry every time I use them - don't know how I ever lived without them
Em qui, 7 de mar de 2019 às 06:27, Peter P. peterparker@fastmail.com escreveu:
- IOhannes m zmoelnig zmoelnig@iem.at [2019-03-07 09:57]:
On 07.03.19 09:47, Christof Ressi wrote:
It annoys me more often than I find it useful and would have prefered
to have it as an opt-in feature
Me too!
how about creating a ticket on [1]?
Done! Thanks IO! https://github.com/pure-data/pure-data/issues/568
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
- Alexandre Torres Porres porres@gmail.com [2019-03-08 19:10]:
I figure and assume you all know, but clicking unselects all the objects so you can make a single connection if you will. And there's always control-z until that becomes a new habit.
I do think the additions are great as well. New features to software ideally should integrate into the workflow seemlessly and without disrupting the learned behavior. Having to deliberatly unselect or even employ undo to live happily with a new feature still seems to need some tailoring to make it become seemless. I argue a modifier for the multiconnections will do that.
Quoting "Peter P." peterparker@fastmail.com:
I do think the additions are great as well. New features to software ideally should integrate into the workflow seemlessly and without disrupting the learned behavior. Having to deliberatly unselect or even employ undo to live happily with a new feature still seems to need some tailoring to make it become seemless. I argue a modifier for the multiconnections will do that.
I learned to adapt my patching behavior the hard way, after
accidentally connecting multiple full blast signals to the dac.. So,
yes i agree, this feature should be optional.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
I do think the additions are great as well. New features to software ideally should integrate into the workflow seemlessly and without disrupting the learned behavior. Having to deliberatly unselect or even employ undo to live happily with a new feature still seems to need some tailoring to make it become seemless. I argue a modifier for the multiconnections will do that.
+1
best
oliver
-
Alexandre Torres Porres -
Christof Ressi -
IOhannes m zmoelnig -
oliver -
Peter P. -
Philipp Schmalfuß