Unique Value classification: problems with symbology of features

[pls]

Hello! In the vector layer properties dialog it is possible to change the values of the attributes I chose for a Unique Value classification; this is particularly useful if you have non-meaningful values names in the attribute field used for the classification. The problem is, when the modification is applied to the layer, all the points pertaining to the modified value's class disappear from the layer.

[lutra]

I confirm this with qgis 1.2 from trunk under both Ubuntu 9.04 and Win XP. Tested with both shapefiles and postgis layers.

To more precise:

*) with points -> the point disappear

*) with lines -> the line "loses" the style options (colour included) and in the map canvas is rendered with a standard width (0.26?) and colour (seems blue to me).

*) with polygons -> the outline and the fill colour/style "lose" the style options and in the map canvas is rendered with a standard outline width (0.26?), outline colour (black?) and fill colour (purple?).

As in the first case features are deleted from the map canvas I would say that this bug causes data corruption. Change the priority if you feel that is too exaggerated.

[jef]

Replying to pls:

In the vector layer properties dialog it is possible to change the values of the attributes I chose for a Unique Value classification; this is particularly useful if you have non-meaningful values names in the attribute field used for the classification. The problem is, when the modification is applied to the layer, all the points pertaining to the modified value's class disappear from the layer.

You probably edited the attribute values instead of adding a description on the right.

Changing the value means that you want features with the value you enter in the classification field to look like the features with the original value looked like. Moreover you don't loose the class for the original value and therefore those features won't be rendered anymore.

Editing the is meant to add classes that do not yet have features for.

BTW r10986 adds a default class that renders classless features.

I'm not sure if I understood your problem correctly. Feel free to reopen, if I didn't.

[lutra]

Replying to jef:

You probably edited the attribute values instead of adding a description on the right.

Changing the value means that you want features with the value you enter in the classification field to look like the features with the original value looked like. Moreover you don't loose the class for the original value and therefore those features won't be rendered anymore.

Editing the is meant to add classes that do not yet have features for.

BTW r10986 adds a default class that renders classless features.

I'm not sure if I understood your problem correctly. Feel free to reopen, if I didn't.

Ok I got it.

But then I have a question.

Have a look to the attached image, it is right what I'm seeing? I mean, is right to see repeated twice in the legend the value of the classification AND the description I give in the "label" field?

[jef]

Replying to lutra:

Have a look to the attached image, it is right what I'm seeing? I mean, is right to see repeated twice in the legend the value of the classification AND the description I give in the "label" field?

Right, the symbol have lower and upper bounds. Obviously that doesn't make to much sense for unique values. Fixed in r11037