Bug report #16882
feature count refreshed after each edit and in the form view of the attribute table
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Attribute table | ||
| Affected QGIS version: | 2.18.11 | Regression?: | No |
| Operating System: | Windows 7 x64 SP1 | Easy fix?: | No |
| Pull Request or Patch supplied: | No | Resolution: | fixed/implemented |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 24781 |
Description
Actually, qgis 2.18.9 and higher refresh the entity count after each edit and in the form view of the attribute table, this is really annoying.
Actual workaround : deactivate entity count for the edited layer.
#16659 (Linked)
History
#1
Updated by Giovanni Manghi over 7 years ago
- Subject changed from Refresh feature count is a bit too aggressive to feature count refreshed after each edit and in the form view of the attribute table
- Status changed from Open to Feedback
- Assignee deleted (
Regis Haubourg) - Affected QGIS version changed from 2.18.9 to 2.18.10
Why regression? was not the case in older QGIS releases?
#2
Updated by Giovanni Manghi over 7 years ago
- Affected QGIS version changed from 2.18.10 to 2.18.11
#3
Updated by Jürgen Fischer over 7 years ago
- Description updated (diff)
#4
Updated by Giovanni Manghi about 7 years ago
- Status changed from Feedback to Open
- Regression? changed from Yes to No
#5
Updated by Arnaud Poncet-Montanges about 7 years ago
Actually, the annoying thing is not that the entity count is updated but the fact that the attribute table goes into background.
#6
Updated by salvatore fiandaca almost 6 years ago
- Status changed from Open to Closed
I just did a test with a shapefile with 20k points, I can not reproduce the problem described in both the 2.18.28, 3.4.4 and master
therefore closed issues
#7
Updated by Giovanni Manghi almost 6 years ago
- Resolution set to fixed/implemented
salvatore fiandaca wrote:
I just did a test with a shapefile with 20k points, I can not reproduce the problem described in both the 2.18.28, 3.4.4 and master
therefore closed issues
please set the resolution of tickets.