Re: [phenixbb] [COOT] CCP4 - Coot in Applications
Ok - annoying thing…. 1) using /Applications/coot.app/Contents/Resources/script to launch Coot from the command line (terminal window) works IF you don't have X11 open already. 2) if you DO have X11 open, coot pretty much always crashes with the aforementioned "invalid window errors".
Nov 23 12:17:02 coot-real[80005] <Error>: kCGErrorIllegalArgument: CGSGetSurfaceBounds Nov 23 12:17:02 coot-real[80005] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged. Nov 23 12:17:02 coot-real[80005] <Error>: kCGErrorIllegalArgument: CGSBindSurface: Invalid window 0x8da Nov 23 12:17:02 coot-real[80005] <Error>: kCGErrorIllegalArgument: CGSBindSurface: Invalid window 0x8da Nov 23 12:17:02 coot-real[80005] <Error>: kCGErrorIllegalArgument: CGSBindSurface: Invalid window 0x8da
Ideas and suggestions welcome. I guess I could make sure that X11 is not running each time I invoke a script or run coot from the command line - but it's not exactly ideal. --> NB: Running Mac OS X, 10.7.5 - Lion. Please excuse the cross bulletin board posting, but I really do use quite a range of software across all program suites - and this method of delivering coot causes problems for many of the plugins/scripts (phenix and buster for example). With thanks, Antony. --- Dr Antony W Oliver Senior Research Fellow CR-UK DNA Repair Enzymes Group Genome Damage and Stability Centre Science Park Road University of Sussex Falmer, Brighton, BN1 9RQ email: [email protected] tel (office): +44 (0)1273 678349 tel (lab): +44 (0)1273 677512 On Nov 27, 2012, at 11:32 AM, Antony Oliver wrote:
Thanks Charles - that seems to work..!
Tony.
--- Dr Antony W Oliver Senior Research Fellow CR-UK DNA Repair Enzymes Group Genome Damage and Stability Centre Science Park Road University of Sussex Falmer, Brighton, BN1 9RQ
email: [email protected] tel (office): +44 (0)1273 678349 tel (lab): +44 (0)1273 677512
On Nov 26, 2012, at 10:19 AM, Charles Ballard wrote:
You could give
/Applications/coot.app/Contents/Resources/script
a go.
Charles
On 23 Nov 2012, at 12:20, Antony Oliver wrote:
On Wed, Nov 28, 2012 at 7:03 AM, Antony Oliver
Ok - annoying thing….
1) using /Applications/coot.app/Contents/Resources/script to launch Coot from the command line (terminal window) works IF you don't have X11 open already. 2) if you DO have X11 open, coot pretty much always crashes with the aforementioned "invalid window errors".
...
Ideas and suggestions welcome. I guess I could make sure that X11 is not running each time I invoke a script or run coot from the command line - but it's not exactly ideal.
Sorry, I don't have any bright ideas - in my experience the behavior of Coot on OS 10.7 with the current XQuartz is horrifically buggy (not Paul's fault, there is clearly something broken at a very low level in either XQuartz or GTK or both). There isn't much that can be done about it on the Phenix side. However, the current code tries to launch this: /Applications/coot.app/Contents/MacOS/coot instead of the "script" executable, which I was unaware of. I will try the latter and see if it works any better, but I suspect the bugginess is independent of how I launch Coot. The "native" OS X port of GTK appears to have made enough progress for GIMP to run independently of X11, so maybe there is still hope for a native Coot... they don't appear to have OpenGL working yet, however. -Nat
participants (2)
-
Antony Oliver -
Nathaniel Echols