[PD] Tcl/Tk error

[Max]

I have these errors on different platforms at the most inconvenient 
moments, but I also struggle to make it reproducible, hence no issue 
filed yet.

On 02.04.19 11:37, oliver wrote:
> Hi,
> 
> sorry for a not so precise bug-report, but it's all i can offer:
> 
> recently i discovered a strange behaviour in Windows PD 0.49 (32bit) 
> when the closing of a patch window (or even the closing of a subpatch 
> window) would result in a Tcl/Tk error that i have not excperienced up 
> until PD 0.49.
> 
> so, i close a window (main or subpatch - mostly with STRG+w), the patch 
> window turns white with some inlet relics still being displayed and the 
> console prints out a Tcl/TK error message in red colour.
> 
> the console says for example this:
> 
> (Tcl) UNHANDLED ERROR: bad window path name ".x3b212c8"
>      while executing
> "wm title $mytoplevel "$name$dirtychar$arguments - $path""
>      (procedure "pdtk_canvas_reflecttitle" line 15)
>      invoked from within
> "pdtk_canvas_reflecttitle .x3b212c8 {D:/pd_0.49/_MYPATCHES_/MFPOW} 
> {metronome} { [edit]} 0"
>      ("uplevel" body line 718)
>      invoked from within
> "uplevel #0 $docmds".x2596028: no such object
> .x2596028: no such object
> .x2596028: no such object
> .x2596028: no such object
> 
> 
> from this point on nothing can be done in PD anymore, the only way to 
> get out of this is to kill the PD process from the outside.
> 
> the patch contains several GOP subpatches and also some of my own GUI 
> abstractions, that contain GOPs.
> 
> (the patch is very involved so i couldn't really check what would 
> happen, if i replaced all of my abstractions with something else ...)
> 
> any ideas ? ...
> 
> best
> 
> oliver
> 
>