-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Merge features: immediately update widgets for attributes with a provider default value #59960
base: master
Are you sure you want to change the base?
Conversation
- Apply for widgets which show a key/description instead of the actual value
🪟 Windows buildsDownload Windows builds of this PR for testing. 🪟 Windows Qt6 buildsDownload Windows Qt6 builds of this PR for testing. |
@@ -267,6 +267,15 @@ void QgsMergeAttributesDialog::createTableWidgetContents() | |||
currentComboBox->setCurrentIndex( currentComboBox->findData( QStringLiteral( "manual" ) ) ); | |||
currentComboBox->blockSignals( false ); | |||
} | |||
|
|||
const QString widgetType = QgsGui::editorWidgetRegistry()->findBest( mVectorLayer, mFields.at( idx ).name() ).type(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be field.editorWidgetSetup().type()
instead? Iirc findBest is using some heuristics while we can use a configuration here.
|
||
const QString widgetType = QgsGui::editorWidgetRegistry()->findBest( mVectorLayer, mFields.at( idx ).name() ).type(); | ||
|
||
const QStringList updateWidgetFor = QStringList() << QStringLiteral( "ValueMap" ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the reason for this hardcoded list of widget types?
Apply for widgets which show a key/description instead of the actual values. Addresses part of #59494 (the additional context part, the main part AFAIK is the intended behavior and is meant to be addressed with a "merge policy" feature)
Backport to 3.40 requested.
before:
after: