Thanks Paul, For now I will grin and bear it since I dont see myself reverting to an older gtk.
> I guess it's easier to just move your mouse back over that window (to refocus it). I guess another painful thing in Ubuntu 12.04 with Unity is that "Focus follows mouse" requires a gconf setting ..somehow in my case I cannot get focus follows mouse to work.. Regardless even if I did setup "focus follows mouse"..once I click on the Ubuntu model..in this new GTK the molprobity window would lose the blue/orange ring indicating which button was last active/clicked. On an unrelated note...I am also seeing random slowdowns If I have a few more opengl applications running with one or two java sessions going with Ubuntu 12.04 and the 310.14 nvidia driver....despite having a $2000 graphics card...never was a problem with the 10.04 and non-compiz Ubuntu.. Serves me right for upgrading to 12.04... Thanks for your help Hari On Fri, Apr 5, 2013 at 8:29 AM, Paul Emsley <[email protected]>wrote: > On 04/02/2013 09:04 PM, hari jayaram wrote: > >> Hello, >> I auto-upgraded my system to Ubuntu 12,04 and my old coot setup ( from >> 10.04) works just fine on the new system . >> >> There is just one problem in that the coot multicriterion charts >> generated by Molrpobity no longer behave the same way . >> >> When I read in a scheme or python based Molprobity multi-chart..clicking >> on a button does take me to the relevant section of the model..The button >> does have an orange ring indicating it was pressed..but the moment I click >> the mouse on the coot model graphics window ..the orange ring dissapears >> and so I dont know which button I had pressed last >> > > OK, I just tried this and it works the same for me (except I have a blue > highlighting). > > > and conseqeuntly it is very hard to know which ones done and which ones >> are yet to do. >> > > Yes. > > > >> This seems like a new gtk version >> > > Yes, it does. > > > or something else thats causing this behavior. >> > > I would guess not. > > > >> Should I just re-compile coot or is there an OS or coot setting that will >> fix the "issue" >> > > I doubt very much that that would fix things (except if you used an old > version of gtk+ (and that brings its own can of worms). I don't know if > it's possible to "fix" - it may well be that the authors of gtk+ think this > is an improvement. > > I guess it's easier to just move your mouse back over that window (to > refocus it). > > Paul > >
