Closed as not planned
Description
Feature description
When you create a container in drag-and-drop mode. The dialog allows you to select whether it should be a tab or a group. A group can be created only if there's already a container (tab or group).
You can then assume that a group can not be a top level item in a form. But this is plainly wrong, because in the form attributes dialog, you can later drag and drop the group at the top level, i.e. not within any container. So why obliging people to select a group box at the beginning?
IMHO The restriction in the creation dialog is unnecessary and, it's just complicating the process and misleading people.
I would suggest that either:
- there's a new
top level group boxitem next to the existing two, - or there's a
None(or whatever obvious label) row in the combobox. If selected, the new group is added at the top level, otherwise it is added under the selected container. my preference goes here
Additional context
<style type="text/css"> p, li { white-space: pre-wrap; } </style>| QGIS version | 3.27.0-Master | QGIS code revision | 8cb7f22 |
|---|---|---|---|
| Qt version | 5.15.3 | ||
| Python version | 3.10.4 | ||
| GDAL/OGR version | 3.4.1 | ||
| PROJ version | 8.2.1 | ||
| EPSG Registry database version | v10.041 (2021-12-03) | ||
| GEOS version | 3.10.2-CAPI-1.16.0 | ||
| SQLite version | 3.37.2 | ||
| PostgreSQL client version | unknown | ||
| SpatiaLite version | 5.0.1 | ||
| QWT version | 6.1.4 | ||
| QScintilla2 version | 2.11.6 | ||
| OS version | Ubuntu 22.04 LTS | ||
| This copy of QGIS writes debugging output. | |||
| Active Python plugins | |||
| db_manager | 0.1.20 | ||
| grassprovider | 2.12.99 | ||
| MetaSearch | 0.3.6 | ||
| processing | 2.12.99 | ||
| sagaprovider | 2.12.99 |
<
55E9
/div>