-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Quick calculation bar causes QGIS crash when updating fields with aliases. #24212
Comments
Author Name: Giovanni Manghi (@gioman) sorry to ask, what do you mean with "quick calculator"?
|
Author Name: Saber Razmjooei (@saberraz) Hi Gio, It is top of the attribute table.
|
Author Name: Giovanni Manghi (@gioman) Saber Razmjooei wrote:
then I cannot confirm.
|
Author Name: Lukasz Debek (Lukasz Debek) Giovanni Manghi wrote:
I mean bar that shows up in attribute table when you start edit session.
|
Author Name: Giovanni Manghi (@gioman) Lukasz Debek wrote:
right, then is confirmed.
|
Author Name: Saber Razmjooei (@saberraz) Here is an example file:
Segmentation fault in terminal. I can also confirm it in master.
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Matthias Kuhn (@m-kuhn) Pull request open #4543
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Anónimo (Anónimo) Applied in changeset a0c6872.
|
Author Name: Matthias Kuhn (@m-kuhn) Only applied to master yet
|
Author Name: Anónimo (Anónimo) Applied in changeset 477d1bd.
|
Author Name: Lukasz Debek (Lukasz Debek)
Original Redmine Issue: 16302
Affected QGIS version: 2.18.4
Redmine category:attribute_table
Using quick calculation bar for updating fields with aliases causes QGIS crash.
To reproduce the problem add a layer (checked with shapefiles and postgis layers), set an alias for any field and try to update values inside this field using the quick calculation bar.
Checked on QGIS 2.18.4 and 2.18.3 from OSGeo4W 64bit installer.
Related issue(s): #24097 (relates)
Redmine related issue(s): 16187
The text was updated successfully, but these errors were encountered: