[GRASS5] 100% cpu mouse bug
radim.blazek at gmail.com
Wed Apr 26 05:07:13 EDT 2006
On 4/23/06, Maciek Sieczka <werchowyna at epf.pl> wrote:
> 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.
> Are you reffering to the bug
> 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
> 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?
Yes, I fixed first the modules which dont need to update TclTk GUI
(d.zoom, d.what.rast,d.what.vect -x) and I thought that I fixed
also the v.digit and d.what.vect. Now I see that there is still problem with
the form. Note however that R_get_location_* are fixed and the only problem
is in form.
> W polskim Internecie s? setki milion?w stron. My przekazujemy Tobie tylko najlepsze z nich!
> grass5 mailing list
> grass5 at grass.itc.it
More information about the grass-dev