Pedro Santos

Yeah, as the title says, I know it's not a big thing, it doesn't even take much time, but it also wouldn't be hard to implement and would save everyone who uses patches from the forums some repetive procedures:

The "New from Clipboard" functionality could, after opening a new patcher window and pasting the code, automatically resize the window to fit its contents. Who agrees?

Now, in my defense, I think I'm not really lazy, I just hate doing the same thing over and over again knowing that there could be a better way... like... oh! Always having to move the patcher window around to reveal that jit.window on the top left corner of the screen... ;-)

I'm sure that there are other little details that could make your patching quicker/easier and your lifer much more fruitful and awesome... care to share some of your own somewhat "frivolous" wishes that shouldn't be so hard for Cycling to turn into reality?

feature-requests-of-a-lazy-guy

 , and you would be allowed to use it only 3 times . then u loose and you can give up the patching :)

i would love to have a command like . resolve problem or a hint , and you would be allowed to use it only 3 times . then u loose and you can give up the patching :)


I've always wanted the functionality you want for new-from-clipboard as a general mechanism:

2) auto adjust window so that just that group is visible

Clearly if you have that, then first selecting all objects immediately gives you the functionally you want for new-from-clipboard

1) select some group of objects
2) auto adjust window so that just that group is visible

Clearly if you have that, then first selecting all objects immediately gives you the functionally you want for new-from-clipboard


i personnally prefer DO...WHILE's idea.
there should be cheatcodes too


Humour aside, I'm sure many are definitely keen to see a paste-at-mouse-position functionality implemented. Not sure why it functions the way it does at the moment.

Example: copy an object or group of objects from one patch, open another patch and paste.... The object/s get pasted in a useless and seemingly random position in the new patch.

I've mentioned this before on forum. Obviously didn't eventuate into anything though.

[resolve_a_problem], [phone_a_friend], [50-50]... all good ideas.

In dense patches I often end up searching for where the hell my pasted objects ended up.

The current paste position isn't anything like random. It appears to be the position "Duplicate" uses by default (a few pixels down and to the right from the original position).

It's logical enough (particularly given that Duplicate is a short cut for Copy-&-Paste without messing up the Clipboard), if a little surprising when applied in a different window from the source. Note that when this behavior was originally developed, making anything dependent on current mouse position was not a thing. I'm still not really convinced that paste-at-current-mouse-position (which often can be really random) is brilliant UI, but it's become much more widely used in the last few years.

i disagree, because sizing windows should be left to the patchers max code.

Why? For the most part this would be a usability feature for developers at edit time. It has nothing to do with "running" patchers.

I'll stand corrected by Raja—it's a long time since I've looked carefully at this, and a difference of maybe a half-dozen pixels one way or the other is easy to miss or forget. But nevertheless, the Paste position isn't "random." Rather the reverse!

The position of my mouse at any point in time does tend to be random, however, which is why I'm not a big fan of making paste position depend on it.

Paste at mouse position can be achieved by right clicking (control-click on Mac) into the destination patcher and selecting "paste" from the contextual menu.

While I understand Roman Thilenius' position ("sizing windows should be left to the patchers max code"), I also think that "New from Clipboard" is a special functionality, more similar in nature to a File than to a traditional Paste process. The proof of that is its positioning resides in the File menu instead of in the Edit menu. And, I cannot imagine any of us including a thispatcher, window positioning message and some sort of initialization process everytime we paste a simple example patch in the forums to help someone.

On a related note, and given the conceptual similarities between opening a file and the "New from Clipboard" functionality, +1 for the automatic loadbang activation (not on regular paste though!).

+ 1 for "Paste at mouse cursor".Independently of the current "Paste" position being random or not, the question is "Is it useful?" I often find it confusing and, particularly in crowded patches, find myself looking around for the pasted object (normally, I move the object with the keyboard cursor keys to detect the object positioning through the movement...). Jesse, I haven't notice that before! Thanks.

One last suggestion: a sort of connection snap. How many times we want to add an object between two other vertically aligned objects and have to manually reconnect the output of the 1st one to the new object and make a new connection from this one to the 2nd. I think that draging an object between two vertically aligned objects with a key modifier (ex: shift or alt) should result in the connection being automatically made; if you release the modifier key before releasing the mouse, the connections would return to normal. This could even be easily applied to all situations: whenever an object passes above a cable, with a certain modifier key, the object is inserted (first input and output). Thinking about it, this could be a nice addition to the patching mechanics feature...

Hi, I've stumbled in this topic from 2015 and reading it again I noticed that both suggestions I made, the "loadbang initialization when using New from Clipboard" and the "connection snap of the leftmost inlets/outlets when dragging/inserting objects" were in fact implemented.

So, I'd like to take the opportunity to thank the Cycling74 team for listening and keep refining Max.

Hi, I've stumbled in this topic from 2015 and reading it again I noticed that both suggestions I made, the "loadbang initialization when using New from Clipboard" and the "connection snap of the leftmost inlets/outlets when dragging/inserting objects" were in fact implemented.
So, I'd like to take the opportunity to thank the Cycling74 team for listening and keep refining Max.

Feature requests of a lazy guy ;-)