Sorry for my english...

When you select a lot of objects if GROUP option exist and apply it, when you click on one object of the group, all objetcs are selected.
Is it a good idea ?

@Jefijef As this is not possible in Pd at the moment, what you can do is putting the objects you want to group inside a subpatch...

Thank you Ingox, i know "as is not possible in Pd at the moment" but i imagine GROUP option with possibility to hide / see objetcs of your choise, more faster and easier than subpatch...

(or canvas)

@Jefijef Surely you can get a discussion here on the forum, but feature requests are probably better placed on the mailing list or directly on Github.

My personal expectation would be that it could be a nice feature, but we would not see it in a foreseeable future, as there are other priorities...

Oh i'm sorry !
Thank you !

There's the patcherize plugin which you can find on deken. With this plugin you can select any number of objects and with Shift+Ctl+p they are placed in a subpatch. It's not exactly what you're looking for, but it's a nice and fast way to "hide" objects.

The patcherize plugin is wonderfully useful... But there is a huge bug: any message or GUI need to be cut-pasted again before clicking on any of them otherwise ALL SYSTEM CRASH INSTANTLY.

So during a workshop with students, its is so dangerous, I had to remove it ;/

Another simple pd issue that would be nice to have fixed 10 years ago.

@60hz a bug report should be done about this. Ι'm pretty sure IOhannes will take care of it.

@alexandros
Actually this is described in the readme file...

## Pd crashes when clicking on a patcherized msgbox
Yes.
Patcherization does not re-instantiate any object (or msgbox).
Instead it just "moves" the selection to the new window, basically leaving
the object unaware that it's context has changed.

When clicking on the 'msgbox', the "flashing effect" will try to talk to the
wrong window, resulting in a crash.

This could be fixed by doing a Cut-n-Paste instead of sleekily migrating the
objects, but this would result in objects losing their inner state (not a
problem for a msgbox, that doesn't have any hidden inner state)

## GUI objects do not respond after being patcherized
See above: the reason for this behaviour is the same (albeit less drastic) than
the crashing msgbox.
Unfortunately, generic GUI objects might (and most probably) will have a hidden
inner st

@60hz oops, caught off guard...