-
-
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
Attempt to display more columns in the "Export Project to Dxf" dialog #57155
Conversation
No more artifact generation for Windows? |
It looks like they are created https://github.com/qgis/QGIS/actions/runs/8685776406?pr=57155 but the automatic comment is no longer added. |
I think there's a bug in GitHub itself. The workflows no longer trigger, and there's not even any record of them attempting to run. I was going to give it a couple of weeks and see if it resolves itself... 🤷♂️ |
The QGIS project highly values your contribution and would love to see this work merged! Unfortunately this PR has not had any activity in the last 14 days and is being automatically marked as "stale". If you think this pull request should be merged, please check
|
While we hate to see this happen, this PR has been automatically closed because it has not had any activity in the last 21 days. If this pull request should be reconsidered, please follow the guidelines in the previous comment and reopen this pull request. Or, if you have any further questions, just ask! We love to help, and if there's anything the QGIS project can do to help push this PR forward please let us know how we can assist. |
Replying to self: the widgets in the ui file of these dialogs DO NOT use QgsLayerTreeView; they use QTreeView. And investigating further, QgsLayerTreeView seems to appear only in "layout legend widget" and "embed layers and groups" ui files. And the particularity of these dialogs is that they show a SINGLE column that takes all the available width. |
I don't think this is the most sustainable fix (being able to automatically pass the number of expected columns may be) but it should help fix resurrection of #45441, and avoid hiding the data-defined blocks columns.
That said, I fail to understand why this widget behaves differently to the other ones in which a treeview is involved (let's say the "layer capabilities" or "QGIS Server --> WMTS" in the project properties dialog, ...)