hard to tell without the patch, ... can u send it? usually if you close the subpatch and then save, it should be saved as "closed"... maybe just copy and paste it (?), ... maybe not the right solution... marius.

----- Original Message ----- From: "Maurizio Umberto Puxeddu" umbpux@tin.it To: PD-list@iem.kug.ac.at Sent: Monday, September 09, 2002 10:50 AM Subject: [PD] subpatch always open

Hello.

I got a subpatch that is always open when I open the parent patch. Also if I edit the subpatch I get messages like

bad window path name ".x81656e8"

on the console.

This happens even if it the patch is nested more deeply. For example if I create (by adding a new object or using ctrl-d or editing the object) an instance of an abstraction containing that subpatch, it opens.

Any hint?

Thanks, Maurizio Umberto Puxeddu.

---

PD-list mailing list PD-list@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list

hi Maurizio,

the ``bad window...'' warning is caused by Pd trying to add a dirty-flag mark ('*') to the title bar of the _main_ window of an abstraction, while it is invisible, i.e. tk/tcl window does not exist. It is a (harmless) bug...

What might be confusing, though, is this --

each subpatch is being saved with a property of having its window open (being 'visible') or closed preserved. Otoh, the main window of an abstraction is never open after creating its object box.

Perhaps, there could be a less confusing way of handling it --

an abstraction (its main window) could be made visible after loading, iff any of its subpatches had the 'vis' property set? Or the opposite way: ignoring the 'vis' property of subpatches, if created from within an abstraction?

Krzysztof

Maurizio Umberto Puxeddu wrote: ...

I got a subpatch that is always open when I open the parent patch. Also if I edit the subpatch I get messages like

bad window path name ".x81656e8"