On Thu, Jul 29, 2010 at 1:26 PM, Joseph Noel <span dir="ltr"><<a href="mailto:noel@salk.edu">noel@salk.edu</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word"><div>I noticed that coot behaves unusually on the MacOS version of phenix. It will open when you hit the button in the GUI but it will not open any of the files you specify. Just the main coot window which you then have to load everything as you would normally if running coot stand alone.</div>
</div></blockquote><div><br></div><div>This usually means that the Python embedded in Coot isn't linked correctly (on Linux, it usually means Python wasn't even included). �One way to tell is to look on the toolbar in Coot - if it doesn't have a button that says "Connected to PHENIX" (or something like that), my extension module failed. � Which version are you using? �I believe the most recent binary on Bill Scott's page may have this problem, but I'll double-check. �I use Fink (<a href="http://www.finkproject.org/">http://www.finkproject.org/</a>) to install and update Coot, and this has always worked quite well as long as Fink doesn't crash on me.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word"><div>Also, I noticed that when you run coot from the gui link on MacOS that after manipulating the structure for rebuilding, etc it will freeze requiring a force quit of x-windows to recover. However, if I open coot directly from my xterm on MacOS it works fine and no freezes. �Just a note. Love the program!</div>
</div></blockquote><div><br></div><div>This I haven't heard before. �We have to tamper with the environment variables to get Coot to launch from inside Phenix, at least on Linux, and this may have side effects. �Where does the console output from Coot end?</div>
<div><br></div><div>thanks,</div><div>Nat</div></div>