Thanks Marcin,
I thought I'd patched this already some time ago (shortly after you
mentioned it to me), but now that I try to find it in the logs, it seems
to have been missed/lost.
Paul.
On 18/05/15 19:00, Marcin Wojdyr wrote:
> That problem has been discussed several times on the coot mailing list.
> Currently a workaround is to type:
>
> (set-use-stroke-characters 1)
>
> in scheme console (Calculate > Scripting > Scheme).
> (You can also add it to coot settings).
> As a side effect fonts will look worse.
>
> I've just tested a better fix (patch attached) and it seems to work,
> It requires compilation from source, so for now use the workaround
> above.
>
> Marcin
>
>
> On Sun, May 17, 2015 at 11:10:41AM -0300, Jorge Iulek wrote:
>> Thanks Carlos Contreras-Martel and Lu Zuokun for pointing me to check
>> graphic driver problems (or update them from the vendor, by the way,
>> controller model Intel HD 4000). Taking some time with this today, I still
>> feel I will have to study further before making changes.
>> This poses me yet other question, though maybe it escapes the discussion
>> list scope, that I must search further: how (and where) different are the
>> resources used by the virtual machine compared to the host machine, such
>> that this graphical behavior is different.
>> Yours,
>>
>> Jorge
>>
>> On 05/16/2015 08:39 PM, Jorge Iulek wrote:
>>> Dear all,
>>>
>>> My machine has openSuSE 12.3, a lenovo ideadpad with 8 cores (4 are
>>> virutal) and 8 GB memory.
>>> For a number of coot versions in it (including the newest one), coot
>>> answers slowly to rotating, but specially the space bar translate is even
>>> more slow (from residue x to x+1 etc.).
>>> Curiously, in either CentOS or even openSuSE in oracle virtualboxes
>>> (under this openSuSE host), to which I liberate only 1 cpu and only 1 GB
>>> memory, it goes much faster, at a very reasonable speed. How could be
>>> that? In principle I thought that the multicore configuration of the host
>>> machine might be the culprit.
>>> So, for coot tasks, I have been using the virtual machine, but that is
>>> impractical.
>>> The closest to this problem I found was
>>> [log in to unmask]" target="_blank">https:[log in to unmask] , but I
>>> could not devise any trial to solve the problem. Even trying the
>>> http://www2.mrc-lmb.cam.ac.uk/personal/pemsley/coot/web/docs/coot.html#Slow-Computer-Configuration <http://www2.mrc-lmb.cam.ac.uk/personal/pemsley/coot/web/docs/coot.html#Slow-Computer-Configuration>
>>>
>>> configuration did not solve the problem satisfactorily.
>>> I tried to search wider, but could not find other suggestions. Should you have one, I would be glad to try.
>>> Sincerely yours,
>>>
>>> Jorge
>>>
>>
|