Well, IMHO I guess making pd only open one instance at a time would be default behaviour. If a user wished to open more abstractions then they could use the 'many' library. It seems like both ways would be handled then.

I still don't know why multiple instances of a patch would be useful, or how it would differ to having multiple abstractions within a patch. Abstractions seem to be handled better when it comes to editing, saving an edited abstraction closes all other duplicate windows and re-instantiates them. Whereas sometimes I've run in problems editing a duplicate of a patch by accident and lost work because of problems with saving both patches etc...

Cheers,
Joe

On 24 November 2010 18:01, Hans-Christoph Steiner <hans@at.or.at> wrote:

Its often useful in Pd to open multiple instances of a patch.  For example, I just release the 'many' lib which lets you run many instances of a patch.  But yes, it is a bit weird when you are used to most apps where it only lets you have one instance of a file running.

Any suggestions on how to handle it both ways?

.hc


On Nov 24, 2010, at 11:01 AM, Joe White wrote:

Hi,

 I'm just wondering if there is reason behind PD opening another instance of an already running patch instead of just pointing to it (on OSX anyway).

To me there are a few undesirable consequences such as problems when editing, duplicates of global sends/tables and sometimes not knowing you have two open.

Maybe I'm missing something?

Cheers,
Joe
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list





----------------------------------------------------------------------------

'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink-collar temp pool day.  - “Hijab Scene #2", by Mohja Kahf