<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "> <br><div><div>On Nov 28, 2006, at 7:37 PM, Jacob Rus wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><blockquote type="cite"><p style="margin: 0.0px 0.0px 0.0px 10.0px"><font face="Lucida Grande" size="2" style="font: 10.0px Lucida Grande">�</font><font face="Monaco" size="2" style="font: 10.0px Monaco"> There's a possibility that windows not attached to a process could be orphaned, which would require users to kill the window on the command line (if the window doesn't have a close box).</font></p> </blockquote><p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 10.0px Monaco; min-height: 14.0px"><br></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Monaco" size="2" style="font: 10.0px Monaco">Hmm, there's no way to remedy this?<span class="Apple-converted-space"> </span>It seems like the window could do some error checking itself to avoid this case.</font></p> </blockquote></div><div><br class="webkit-block-placeholder"></div><div>I didn't mean to forget about this question, sorry. To be clear, the problem I'm thinking of is that the script controlling the window has failed in some way, and the author has forgotten to make sure the window is closed on failure. A fully debugged script should catch this case and close the window on exceptions. Many scripts are not fully debugged. :) There is also the possibility of the script being terminated via kill.</div><div><br class="webkit-block-placeholder"></div><div>This probably won't be an issue for most people, because most scripts will likely use wrapper code in TM_SUPPORT that will take care of closing the window as needed.</div><div><br></div><div>Chris</div></body></html>