My memory on this isn't altogether reliable, but I believe I put in the extra deletion to fix a situation in which sometimes inlets and outlets on GOPs never got erased when the object was deleted. I wasn't able to figure out at the time how to get everything reliably erased exactly one time, so I gave up and erased it all twice.
I have found the issue of when to draw and when to erase GOP stuff very hard to understand....
cheers Miller
On Thu, Mar 19, 2015 at 04:08:40PM -0400, Jonathan Wilkes via Pd-list wrote:
Hi list, I'm implementing graph-on-parent drawing in my port of the Pd-l2ork GUI to HTML5.
What I've come across is that both glist_delete and graph_vis will send a message to the GUI to erase the objects shown in the GOP window. So when you select a gop subpatch and click <BackSpace>, Pd sends two "delete" messages to the GUI for each object shown in the GOP window.
Is there an easy way to change this so that only one "delete" message gets sent to the GUI per object? It's easy enough to ignore the extra messages. But it's _way_ easier to maintain and debug when you don't have to track down and analyze two sources of GUI deletions, especially when the dataflow is obscured by function callbacks in C.
-Jonathan
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list