Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

all features disappear when editing layer feature(s) under {categorized,graduated,rule-based} symbology #16580

Closed
qgib opened this issue Apr 19, 2013 · 5 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Apr 19, 2013

Author Name: Mathieu Pellerin - nIRV (Mathieu Pellerin - nIRV)
Original Redmine Issue: 7660
Affected QGIS version: master

Assignee: Martin Dobias


That should be fixed prior to 2.0, pretty scary behavior. When a layer symbology is set to categorized, graduated, or rule-based, all features will disappear when editing feature(s) on that layer. If the user then leave the edit mode (saving changes or not), all features will reappear.

Steps to reproduce:

  1. Load the attached shapefile (featuresgone.shp) into a new project
  2. Open the featuresgone layer property window, switch style to categorized (using 'blah' column), and apply
  3. Toggle edit mode on for the featuresgone layer
  4. Move a feature with the node tool

At that stage, only the feature moved will remain visible, all the other features are gone. The features are still there, simply not drawn. Saving the layer by leaving the edit mode will re-draw all features.

Data stays, but it's super scary behavior :)



Related issue(s): #16425 (duplicates)
Redmine related issue(s): 7472


@qgib
Copy link
Contributor Author

qgib commented Apr 19, 2013

Author Name: Giovanni Manghi (@gioman)


confirmed here.

@qgib
Copy link
Contributor Author

qgib commented Apr 19, 2013

Author Name: Mathieu Pellerin - nIRV (Mathieu Pellerin - nIRV)


Forgot to mention that there is an error that shows up in the log window when going through the steps above which says: "Already active iterator on this provider was closed".

@qgib
Copy link
Contributor Author

qgib commented Apr 23, 2013

Author Name: Olivier Dalang (@olivierdalang)


It seems this was already reported twice :
#16310
#16425

@qgib
Copy link
Contributor Author

qgib commented May 28, 2013

Author Name: Nathan Woodrow (@NathanW2)


  • assigned_to_id was configured as Martin Dobias

@qgib
Copy link
Contributor Author

qgib commented May 28, 2013

Author Name: Mathieu Pellerin - nIRV (Mathieu Pellerin - nIRV)


Closing as this is reported already in other bugs, main one being #16425.


  • resolution was changed from to duplicate
  • status_id was changed from Open to Closed

@qgib qgib added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label May 24, 2019
@qgib qgib added this to the Version 2.0.0 milestone May 24, 2019
@qgib qgib closed this as completed May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant