Opened 21 years ago

Closed 20 years ago

Last modified 20 years ago

#360 closed defect (wontfix)

Label Ghost

Reported by: jorodrig@… Owned by: sdlime
Priority: high Milestone:
Component: MapServer CGI Version: 3.6
Severity: normal Keywords:
Cc:

Description

When Label position is set to AUTO in the MAP FILe, upon clicking of a POINT on 
a layer with TYPE 'POINT', the template file renders another exact label in the 
UR corner of the POINT, however, it does not remove the original label, 
therefore 2 labels are shown.  To solve this, I set the Label Position to UR, 
it solves the problem if this label position is desired, in that it lays the 
second label on top of the original.  In other words, if your default Label 
position is UR, the ghost appears on top of it in position UR, so it is not 
seen.

Any other original position renders two labels.

Change History (6)

comment:1 by sdlime, 21 years ago

Status: newassigned
Joseph: Have you tried the same operation in 4.0? If not we may let this slide
(probably not major enough to fix in 3.6.x) unless it can be confirmed the error
still persists in 4.0. Do you have an example image and mapfile, perhaps even a
dataset?

Steve

comment:2 by jorodrig@…, 21 years ago

No Steve, I have not tried it in 4.0 as my configuration may not support 4.0 at 
this time.(see my email directly to you on this later).  You are correct that 
it is not a big issue and could be resolved later, hopefully it is an easy fix.
Also, there is always a possibility that the ghost label is a result of my php 
code, so I have some checking to do.
I have images and a dataset, I could send but I would hold out on sending it as 
I need to clean them up.  I would send you an image of the problem today 
Thanks 
Joseph

comment:3 by sdlime, 21 years ago

Joseph: Is this happening with query maps or just regular maps? Steve

comment:4 by jorodrig@…, 21 years ago

Hi Steve,
It appears on query maps.  Initially, the labels look fine but on query, a 
duplicate 'ghost' appears.
Thanks
Joseph

comment:5 by sdlime, 20 years ago

Resolution: wontfix
Status: assignedclosed
This is long since fixed I believe...

comment:6 by jorodrig@…, 20 years ago

You may close this and I would resubmit if I notice the problem again.  I am 
trying to migrate to 4.* and would let you know if this is a problem
Thanks
Joseph
Note: See TracTickets for help on using tickets.