i agree with that. anyway sanch showed me the trick of organizing patches vertically, so that you only need to scroll up and down.
note that you can scroll with the mouse wheel even while drawing a connection.
the other rule of thumb i usually teach:
as soon as you start scrolling, use subpatches instead.
An integrated Snanpshot/Preset-system would be cool. something similar like in max or reaktor… all actual inlet/io boxes of a nodegroup/subpatch?? can be stored in a snapshot and can be restored by just selecting that new saved preset…
maybe a little bit difficult to implement? but sure a big and usefull advantage…?!
thx kalle for pointing me to this. i try this out and post my comments…
very often i make io boxes with exactly the same name than its inlet. why not automate this by clicking over an inlet with a special keyboard combination. this then create a new io box with the name of the inlet and connects it automatically…?
i think such a fuction could really improve the workflow. what do you mean?
different ways and different unlogical results of selecting more than one node
I am posting in this forum, because it is not really bug, but I think the different ways and results of selecting more than one node are unlogical and confusing.
selecting many IOBoxes with “leftClick and dragging a rectangle” works and Inspector offers “Multinodural selection”
selecting several nodes with “leftClick and dragging a rectangle” works and Inspector offers “Multinodural selection”
selecting many IOBoxes with “Shift and leftclick” IOBoxes does not work at all
selecting several non IOBox nodes with “Shift and leftclick” works for moving them together in a patch but Inspector does not offer " Multinodural selection"
I do not see a reason for this inconsistent behaviour … is there one ?
I think, the “windows standard - shift and leftclick - selection of more than one item” should work exactly like “leftClick and dragging a rectangle” and the inspector should always offer the same “Multinodural selection” when more than one node is selected.
this would be more cryptic maybe? just hiding the iobox and at the same time hiding the pin sounds reasonable. however we have up to now 3 pinvisibilities and 2 nodevisibilities. so we need to define a 3rd nodevisibility.
11a and b?) When you copy and paste something from a larger patch it gets pasted at it’s original coordinates, which sometimes makes it hard to find, so maybe some code to make sure it’s pasted within the bounds of the active window would be a good idea - however what I’d really like to see is a overview map, like in Bidule, for navigating your patch quickly. (A small box in the lower right corner with a smaller representation of the patch).
make somehow possible to make configuration pins accessable in the gui in general.
like the hidden/invisible feature.
per default visible ="-1".
if it only was possible to make them accessible via SetPatch i would be confident.