Yes, this is a bug. This is fixed now - you need 2 corrected ccp4i
files. See
http://www.ccp4.ac.uk/problems.php#6.1.0-sftools-interface
which has links to the fixed files.

Cheers
Martyn

On Thu, 2008-12-18 at 08:32 +0000, Winter, G (Graeme) wrote:
> Dear Engin,
> 
> Yep, I can reproduce this using a binary installation myself - that
> would be a bug. We (CCP4) will look into it and get a fix to you as soon
> as possible.
> 
> Thanks for the report,
> 
> Graeme
> 
> CCP4 Support Team 
> 
> -----Original Message-----
> From: CCP4 bulletin board [mailto:ccp...@jiscmail.ac.uk] On Behalf Of
> Engin Ozkan
> Sent: 18 December 2008 06:10
> To: CCP4BB@JISCMAIL.AC.UK
> Subject: Re: [ccp4bb] iMosflm in 6.1 under OS X
> 
> Now that everything with coot and imosflm has been settled, how about
> sftools?  I am getting errors when I try to open an sftools window with
> ccp4i, with 6.1.0.  I get the same error with a fink-installed mac
> version, and a linux installation.  Here is the error:
> 
> bad window path name ".main.canvas.contents.param_1.body"
> bad window path name ".main.canvas.contents.param_1.body"
>     while executing
> "pack $wframe.body  -side top -fill x"
>     (procedure "update_folder_display" line 23)
>     invoked from within
> "update_folder_display 1 sftools_PROJECT view"
>     invoked from within
> ".w_sftools_PROJECT.main.canvas.contents.param_1.top.but invoke"
>     (command bound to event)
> 
> Any ideas?
> 
> Engin

-- 
***********************************************************************
*                                                                     *
*               Dr. Martyn Winn                                       *
*                                                                     *
*   STFC Daresbury Laboratory, Daresbury, Warrington, WA4 4AD, U.K.   *
*   Tel: +44 1925 603455    E-mail: martyn.w...@stfc.ac.uk            *
*   Fax: +44 1925 603825    Skype name: martyn.winn                   * 
*             URL: http://www.ccp4.ac.uk/martyn/                      *
***********************************************************************

Reply via email to