Also at bugzilla
The problem seems to have arisen from some changes made during the port
to QT4. I've re-instated some of what was removed---basically, a
timer---and cleaned up a few things as well. In particular, it seems to
me it's not work tracking the location of the original double
Richard Heck wrote:
Also at bugzilla
Erm, I just fixed that (r17588).
Jürgen
Whoops. Well, do you want to have a quick look at the attached patch
anyway? (This supersedes the previous one.) I made some slightly more
extensive changes than you did and did it in a slightly different way.
Much of that was motivated by some trouble I had with the /1.5 setting
on my machine.
Richard Heck wrote:
Whoops. Well, do you want to have a quick look at the attached patch
anyway? (This supersedes the previous one.) I made some slightly more
extensive changes than you did and did it in a slightly different way.
I looks good and behaves significantly better than what we had,
Also at bugzilla
The problem seems to have arisen from some changes made during the port
to QT4. I've re-instated some of what was removed---basically, a
timer---and cleaned up a few things as well. In particular, it seems to
me it's not work tracking the location of the original double
Richard Heck wrote:
> Also at bugzilla
Erm, I just fixed that (r17588).
Jürgen
Whoops. Well, do you want to have a quick look at the attached patch
anyway? (This supersedes the previous one.) I made some slightly more
extensive changes than you did and did it in a slightly different way.
Much of that was motivated by some trouble I had with the "/1.5" setting
on my machine.
Richard Heck wrote:
> Whoops. Well, do you want to have a quick look at the attached patch
> anyway? (This supersedes the previous one.) I made some slightly more
> extensive changes than you did and did it in a slightly different way.
I looks good and behaves significantly better than what we
