Hi IOhannes,
Le 20/08/2019 à 15:24, IOhannes m zmölnig a écrit :
On 8/20/19 3:11 PM, Jack wrote:
Hi Miller,
The shortcut (CTRL+K) still doesn't work to "Disconnect Selection" (in the menu Edit). Maybe I missed something ?
- Selecting 2 connected [t b] => "Disconnect Selection" doesn't work
- Selecting the thread of 2 connected [t b] => "Disconnect Selection"
doesn't work
this never worked (that is: 0.50 has the same behaviour as 0.49, so there is no regression)
Currently the <kbd>Ctrl</kbd>+<kbd>k</kbd> shortcut should disconnect all connections of a single selected object. This it does.
OK, i got it !
Selecting a single patchcord and disconnecting the two objects can be simply done with the <kbd>Del</kbd> key.
Sure.
But there is probably little harm done, if <kbd>Ctrl</kbd>+<kbd>k</kbd> would *also* handle this case.
Yes.
Selecting two connected objects is a bit more tricky: what would you expect the shortcut to do?
something as simple as
[t f] -> [t f]is *probably* easy: remove connection between the two objects. (so you get[t f] [t f])
Yes, it is what I expected.
But what if you have:
[f]->[t f]->[t f]->[print]and you select the two[t f]objects. The current behaviour (when only a single object is selected), would suggest to remove any connection going in/out of the selection (rather than inside the selection), so you end up with:[f] [t f]->[t f] [print]other people might expect[f]->[t f] [t f]->[print]
and you can also expect :
[f] [t f] [t f] [print]
and what if you have a loop?
+>[t f]-+ | | +-[t f]<+
But yes, these cases are good examples to prove that the usage is not easy to handle.
so the current behaviour is intentional. unless/until you can come up with a convincingly consistent behaviour, that is easy to remember :-)
Maybe, by using 2 shortcuts : CTRL+K : Connect two objects CTRL+SHIFT+K : Disconnect object ++
Jack
gfamrds IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list