[Merkaartor] Merkaartor freezes (since 0.13/svn)

Jens Fendler jfendler at polytechnic.edu.na
Sun Feb 22 10:00:03 GMT 2009


Hi Chris,

"Lost in the Thread" is nice - might be the title for the next "Lost in
Translation" movie :-)

The problem I was referring to is that (previous to the last patch) it
took merkaartor forever to work on the map in high zoom levels - with
you mentioning it was due to QT not performing a proper clipping to the
area, thus requiring lots of memory if a relation member is among the
things in the map section currently being viewed. The "relations" part
of the problem seems solved, but the very same effect is still present
for border-type ways. Those are usually not part of a relation, but are
also quite large (might also apply to any other "big" map feature). My
guess is that there's more things in the map currently not being
properly clipped away.

Hope this helps,
Jens
 
On Feb 21, 2009 05:23 PM, Chris Browet <cbro at semperpax.com> wrote:

> >
> > Same here, but I noticed (probably) the same problem still occurs
> > with
> > state borders (border_type=nation, boundary=administrative,
> > admin_level=2). For example here: 19.9929, -22.2834, 20.0010,
> > -22.2793.
> >
> > I haven't tested it with other (long) borders yet, but would expect
> > it
> > to be the same.
> 
> 
> I'm lost in the thread... What problem is it? Long download time?
> 
> >
> >
> > One other issue I noticed with the latest patch only is a way
> > artifact
> > being rendered after a "split" on a way: Select a road and one or
> > two
> > nodes on it, split the way, and try to select either of the (new)
> > segments. It will still highlight the whole way unless I change the
> > zoom
> > level (in or out doesn't matter) once. Selecting a segment after
> > changing the zoom level works fine again.
> >
> 
> I was wondering why I was rebuilding the road on each hover/select.
> Now I
> know... Solved.
> 
> - Chris -







More information about the Merkaartor mailing list