[GRASS5] 100% cpu mouse bug

[Michael Barton]

Maciek,

I'm mainly on a Mac and so haven't had nearly as much problem with this as
others--especially those on Cygwin where it was so bad as to make things
unusable. I'm also exclusively using the new GIS Manager where this is a
moot issue. 

So I really can't evaluate it. But I'm glad that it IS working better. I
haven't had time to seek out a Cygwin user and ask if it's better for them
too.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton



> From: Maciek Sieczka <werchowyna at epf.pl>
> Date: Sun, 23 Apr 2006 20:05:57 +0200
> To: Glynn Clements <glynn at gclements.plus.com>
> Cc: <hamish_nospam at yahoo.com>, <grass5 at grass.itc.it>, <neteler at itc.it>
> Subject: Re: [GRASS5] 100% cpu mouse bug
> 
> On Sun, 23 Apr 2006 15:39:32 +0100
> Glynn Clements <glynn at gclements.plus.com> wrote:
> 
>> 
>> Hamish wrote:
>> 
>>> A plea:
>>> 
>>> It's probably about time to get some closure on the long-standing
>>> GRASS 6 uses 100% cpu during mouse ops. issue.
>>> 
>>> My feeling: Rip. Shred. Tear. Do what needs to be done. Do it now.
>> 
>> My feelings are similar.
> 
> Gentlemen,
> 
> Are you reffering to the bug
> http://intevation.de/rt/webrt?serial_num=3087?
> 
> I'm asking because the discussion is going on in this thread like if
> nobody read my post from yesterday, in which I said that d.* modules
> that use mouse (d.zoom, d.what.vext -x, d.measure) no longer utilize
> 100% CPU. Although they used to, only few weeks ago. Looks like the bug
> is solved, though I can't find any relevant entry in the commit list,
> and even Hamish seems to still have this bug (as he started the
> thread).
> 
> Only v.digit and d.what.vect in FORM mode still load CPU significantly,
> yet even with them the situation is _a_lot_better_ - now it is
> possible to normally enter and edit attributes, not having to pray
> for the form to cooperate - even though the CPU is hot.
> 
> As nobody comments on my observations, I'm wondering if I'm the only
> one to notice the change for better. I think it isn't about my
> particular setup, nothing special has changed in my system for over
> half a year, I guess.
> 
> May I ask you for any feedback on this? How do the d.zoom and
> d.what.vect work for you now?
> 
> Maciek
> 
> --------------------
> W polskim Internecie s? setki milion?w stron. My przekazujemy Tobie tylko
> najlepsze z nich!
> http://katalog.panoramainternetu.pl/
>