Conversation
Allow long verifier validation messages to wrap within the asset creation form instead of being clipped horizontally. Refs RavenProject#981
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Issue #981 reports that long asset-creation validation warnings are clipped on Ubuntu. The screenshots show the red verifier warning rendered as one horizontal line, with the valid-character explanation or invalid-address details extending beyond the visible form.
Change
Enable
wordWraponlabelVerifierStringErrorMessage, the existing QLabel used byCreateAssetDialog::showInvalidVerifierStringMessage(). Long verifier validation messages now wrap within the form's available width.Test plan
git diff --checksrc/qt/forms/createassetdialog.uiwith Python's XML parser.labelVerifierStringErrorMessagewidget haswordWrap=true.No executable code or consensus behavior was changed. A full Qt build was not run on the unconfigured ARM64 checkout; the authorized PC should run the Qt build/test gate.
Refs #981