(Un)force hide form in relation widget

[karl-magnus]

What is the bug or the crash?

When the option to force hide form in the relation widget is selected, you can't unselect it to get the form to open in a new window again.

Steps to reproduce the issue

1. In an new project add two tables that could be related to each other 1:N. I have no geometry.
   

2. Add the relation in project properties. The form for new child features opens as a new window as default.
   

3. Edit the Layer Properties -> Attributes Form for the parent table to use Drag and Drop Designer, add the Related child form to the parent form layout and select to Force hide form on add features. The form form for new child features opens in same parent form as expected.
   

4. Edit the Layer Properties -> Attributes Form again and unselect to Force hide form on add features.

5. I get a warning : Deprecation Warning: Trying to set a relation config directly on the relation best_9a4a9b84_a270_4078_bad7_4b1a8102db16_plan_uuid_plan_c595510d_0873_4fd5_b7a1_add047b954fc_plan_uuid. Relation settings should be done for the specific widget instance instead. Use attributeEditorRelation->setNmRelationId() or attributeEditorRelation->setForceSuppressFormPopup() instead.

6. And the form still doesn't open in a new window

Versions

<style type="text/css"> p, li { white-space: pre-wrap; } </style>

QGIS version	3.22.3-Białowieża	QGIS code revision	1628765
Qt version	5.15.2
Python version	3.9.5
GDAL/OGR version	3.4.1
PROJ version	8.2.1
EPSG Registry database version	v10.041 (2021-12-03)
GEOS version	3.10.0-CAPI-1.16.0
SQLite version	3.35.2
PDAL version	2.3.0
PostgreSQL client version	13.0
SpatiaLite version	5.0.1
QWT version	6.1.3
QScintilla2 version	2.11.5
OS version	Windows 10 Version 2009
Active Python plugins
DigitizingTools	1.5.1
Discovery	2.5.7
FilterLayersAtOnce-master	1.0
Qaava	0.1.0
Qgis2threejs	2.6
qgis_resource_sharing	0.16.0
db_manager	0.1.20
grassprovider	2.12.99
MetaSearch	0.3.5
processing	2.12.99
sagaprovider	2.12.99

QGIS version 3.22.3-Białowieża QGIS code revision [1628765](https://github.com/qgis/QGIS/commit/1628765ec7) Qt version 5.15.2 Python version 3.9.5 GDAL/OGR version 3.4.1 PROJ version 8.2.1 EPSG Registry database version v10.041 (2021-12-03) GEOS version 3.10.0-CAPI-1.16.0 SQLite version 3.35.2 PDAL version 2.3.0 PostgreSQL client version 13.0 SpatiaLite version 5.0.1 QWT version 6.1.3 QScintilla2 version 2.11.5 OS version Windows 10 Version 2009

Active Python plugins
DigitizingTools
1.5.1
Discovery
2.5.7
FilterLayersAtOnce-master
1.0
Qaava
0.1.0
Qgis2threejs
2.6
qgis_resource_sharing
0.16.0
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.5
processing
2.12.99
sagaprovider
2.12.99

Supported QGIS version

• I'm running a supported QGIS version according to the roadmap.

New profile

• I tried with a new QGIS profile

Additional context

I have Postgresql tables and automatic transaction groups enabled. Since I have "NOT NULL" constraints without any default values in the child table I get errors from the database and can not insert any new features in the child table. A new project with repeated steps without checking (Force hide...) doesn't solve the problem. A restart of QGIS (or new profile) solves the problem. It seems that the setting gets global in the current session and can't get unset.

[elpaso]

Cannot reproduce on current master/linux.

[karl-magnus]

I can try to find out more. Any suggestions? But This is what it looks like. Clean new profile now. Also tried with just scratch layers.
Setting 1:

Result 1:

Setting 2:

Result 2:

Setting 1 again:

Result as 2 but expected 1:

Same result with just temporary scratch layers:


2022-02-07T17:11:39 WARNING Deprecation Warning: Trying to set a relation config directly on the relation New_child__parent_id_New_parent_id. Relation settings should be done for the specific widget instance instead. Use attributeEditorRelation->setNmRelationId() or attributeEditorRelation->setForceSuppressFormPopup() instead.

[elpaso]

I tested the standalone form from identify and not from the attribute table, this might explain why I couldn't reproduce, I can reproduce it from the attr table.

[karl-magnus]

Yes, forgot that important detail. Good with a lot of screenshots. Since I have no geometry I have to go through the attribute table.