Opened 14 years ago
Closed 14 years ago
#2391 closed bug (worksforme)
Layer properties dialog and Unique Value: cannot see which bitmap is used
Reported by: | trapanator | Owned by: | jef |
---|---|---|---|
Priority: | major: does not work as expected | Milestone: | Version 1.5.0 |
Component: | Symbology | Version: | Trunk |
Keywords: | Cc: | ||
Must Fix for Release: | Yes | Platform: | All |
Platform Version: | Awaiting user input: | no |
Description
If you have a point layer and you use Unique value with different bitmap, you cannot see which bitmap is used to each value (in the "Point Symbol" list area).
Attachments (2)
Change History (10)
comment:1 by , 14 years ago
Priority: | critical: causes crash or data corruption → major: does not work as expected |
---|
comment:2 by , 14 years ago
Owner: | removed |
---|
comment:3 by , 14 years ago
comment:4 by , 14 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Closing it because of missing user feedback. Please reopen it if necessary.
follow-up: 7 comment:5 by , 14 years ago
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
Sorry for my late response.
It still doesn't work in latest trunk:
- load a point shapefile
- open the layer properties and open symbology (use the old symbology)
- select "Unique values"
- get two values and assign different symbol to them
close the dialog box and reopen the layer properties. When you select the two values on the list, the corresponding symbol on "Point Symbol" box is not selected.
For me it is a usability bug, you can fix it in 1.6.0 if you want.
See the attachments.
by , 14 years ago
Attachment: | qgis-symbol-1.JPG added |
---|
by , 14 years ago
Attachment: | qgis-symbol-2.JPG added |
---|
comment:6 by , 14 years ago
Owner: | set to |
---|---|
Status: | reopened → new |
comment:7 by , 14 years ago
Replying to trapanator:
Sorry for my late response.
It still doesn't work in latest trunk:
I tried the airports.shp
from the qgis sample data set with classification on {{USE}}}.
Works fine for me.
comment:8 by , 14 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
strange... you are right.
It does work with a new project, using an old imported from 1.4.0 does not...
closing this bug.
(If I get it right) I cannot replicate the problem under linux/qgis trunk. Can you explain the issue in a more detailed way?