What qmake command line did you use?
Did you try a "make distclean && make" ?
- Chris -
On Thu, Mar 4, 2010 at 01:04, Fernando Toledo wrote:
> ragnarok /usr/local/src/merkaartor $ make
> cd src/ && make -f Makefile
> make[1]: se ingresa al directorio `/usr/local/src/merkaartor/src'
> g++ -c -pi
Hi All,
I really have a hard time reproducing this, although I'm totally convinced
there is a problem for some users.
I just downloaded ~20.000 items in ~10 "download more" and do not notice
even a slowdown at "Parsing XML" time (on xp2 PIV 2Gb).
Could those affected:
1) Provide me with their com
Hi All,
Some users have reported the fact that they have to click some (20?) pixels
(right/left/up/down?) from an actual feature to select it.
Could those affected:
1) Provide me with their computer/OS specs
2) Try to create a reproducible, step-by-step test case, please...
Also, could those NOT
Please also report your RAM, please
- Chris -
On Thu, Mar 4, 2010 at 10:44, Chris Browet wrote:
> Hi All,
>
> I really have a hard time reproducing this, although I'm totally convinced
> there is a problem for some users.
> I just downloaded ~20.000 items in ~10 "download more" and do not notice
I'm using Windows Vista 32 bit 4GB RAM, AMD Athlon X2 QL-64
(it only has 2GB RAM available).
It looks like a memory problem,
because it happens often when I editted a lot of roads and maybe
relations are involved in it too, because I noticed some crashes
when I was working on relations. Virtual n
On Thursday 04 March 2010 10:52:31 Chris Browet wrote:
> Please also report your RAM, please
> - Chris -
>
> On Thu, Mar 4, 2010 at 10:44, Chris Browet wrote:
> > Hi All,
> >
> > I really have a hard time reproducing this, although I'm totally
> > convinced there is a problem for some users.
> > I
Thanks, that eliminates the "os only, Qt version only" possibility.
Could you also check:
1) at what point (in number of features) does it start becoming slow. To
check the number of features in a layer, just click on a layer and the
number of features will be displayed in the info dock.
2) if the
Tested it now without editing (no features in the dirty layer) and
already after two downloads ( I tried to download a big area of 10k x 10k:
http://www.openstreetmap.org/?lat=52.2335&lon=5.3239&zoom=14&layers=B000FTF )
the parsing already freezes (about 100 ways in the features list)
On Jue 04 Mar 2010 06:20:51 Chris Browet escribió:
> What qmake command line did you use?
>
> Did you try a "make distclean && make" ?
>
> - Chris -
qmake was symlink to qt3
i now fixed to qt4 as default:
ragnarok /usr/local/src/merkaartor $ ll /usr/bin/qmake
lrwxrwxrwx 1 root root 23 nov 30 2
I was able to reproduce it.
Windows 7, 4GB RAM.
At the second download more, XML parsing takes a much, much longer time than
usual and maxes out one of my CPU cores.
On Thu, Mar 4, 2010 at 5:44 PM, Chris Browet wrote:
> Hi All,
>
> I really have a hard time reproducing this, although I'm tot
The original problem was not caused by qt3 versus qt4 issue but was a small
error in the source code. I committed a correction so it should compile now.
Richard
> From: ftol...@docksud.com.ar
> To: merkaartor@openstreetmap.org
> Date: Thu, 4 Mar 2010 12:06:16 -0300
> Subject: Re: [Merkaartor]
I can *seem* to reproduce this.
When I am zoomed in enough such that nodes and virtual nodes are visible and
selectable, selecting works smoothly.
But when I am zoomed out, trying to select a few ways becomes annoying.
Sometimes I can hover over ways easily and sometimes I have to move the
mouse
Indeed. Shame on me for not reading the log in details.
Thanks Richard.
- Chris -
On Thu, Mar 4, 2010 at 16:54, Richard Brinkman
wrote:
>
> The original problem was not caused by qt3 versus qt4 issue but was a small
> error in the source code. I committed a correction so it should compile now.
Thanks for all your valuable input.
I have pinpointed the problem and will commit a fix soon.
Note that using virtual node will still have an impact on download, though,
but Merkaartor shouldn't freeze anymore.
- Chris -
___
Merkaartor mailing list
Merk
On Jue 04 Mar 2010 12:54:46 Richard Brinkman escribió:
> The original problem was not caused by qt3 versus qt4 issue but was a small
> error in the source code. I committed a correction so it should compile
> now.
good, i update between my test and i thought that the qt was the problem.
thanks fo
On Thu, 4 Mar 2010 10:47:11 +0100
Chris Browet wrote:
> Some users have reported the fact that they have to click some (20?) pixels
> (right/left/up/down?) from an actual feature to select it.
>
> Could those affected:
> 1) Provide me with their computer/OS specs
NetBSD/i386 (i.e. 32 bit) 5.0_ST
I'm just in the middle of a long (several minutes) freeze in the
"Parsing XML" stage, with one CPU (of four) maxed out. [P.S. just
finished after about five minutes - rough estimate]
Hardware:
Intel Q6600 (Core 2 Quad) @ 2.40GHz
6.0GB RAM (2.0GB still free, almost no swap in use)
Software:
De
All, (or at least the ones on SVN), I've just committed a patch regarding
this issue.
As Toby noticed, it is related to large ways, which explains why I couldn't
reproduce at first Deletion/Recreation of the virtual nodes was done for
every node.
The problem seems (again) to come from Qt object de
18 matches
Mail list logo