QGIS 3.28.1 Bug on inserting manually altitude to reach points about qgep HOT 15 CLOSED

QGIS Minimal version for this seems to be 3.30.0. This really needs a backport.

from qgep.

@PeterZamudio please check on your side if this works properly! ;)

from qgep.

Hello everyone
I did the test and I must say I do not have the same problem. I did the test first with QGIS 3.28.1 and QGEP-Plugin 1.5.5. It worked perfectly. I then updated the QGEP-Plugin to version 1.5.6-b9 and tested again. The tests were first 2 wastewater structures and then a reach digitized. I encounted no problems and the start and end heights were entered and saved.
The SQL Topology button worked fine too.

from qgep.

When I look closely at your video, I notice you have altered the configuration of the field. When I enter the height I have that problem with the point and have to press arrow right instead of decimal. We have discussed this in the group. I see you have changed the configuration and your problem might be there too.

from qgep.

When changing the rp_from_level and rp_to_level widget to text, this is not the same but different issue :

from qgep.

Thank you, I am just saying your problem might be because you have apparently changed the standard settings.
I haven't changed anything and it still seems to be working as it was before 3.28.1. I am talking about the problem you have and not the decimal problem.

from qgep.

The decimal problem is present in qgep project when changing from range to text widget. (QGIS 3.22->3.28.2)

This is due to the fact that the co_level or rp_from_level and rp_to_level are displayed at multiple places in the form (general + specific tab)

Removing one of the occurences solves the decimal problem.

from qgep.

Yes I noticed that displaying a field in multiple places in the form (general + specific tab) does cause problems. I checked through all mine as I had problems with multi edit. With multiple fields they block each other intermittently in multi edit. Also I found in multi edit that fields with database relations do not work right either. When I changed the field to Getvalue/Wertbeziehen and removed the second field, then multi edit worked as it should.

from qgep.

I think that the second part (about the decimals) is the same as #749, which we reported upstream already.

@ponceta is the first part of the issue (about altitude being set to NULL) still relevant ? If no, we can close this, if yes, could you edit/remove your comments about the second part just so that it's clear what this is about ?

from qgep.

@olivierdalang this is a critical issue for us in Pully and we have to look at it and solve this before QGIS 3.28.4 release.

from qgep.

@ponceta Not sure I get this right. Here I'm not able to reproduce the issue with the QGEP project (neither with the digitize tool nor with the wizard). As pointed out by Peter, it seems you're not using the standard form ?

Can you provide steps on the demo data/project to reproduce ?

If not in the demo project, but indeed on customizations of yours, can you provide a reproduceable case (a QGIS project, ideally with data), including full info on QGIS version ? (but in that case, should we really track that issue here in the QGEP tracker ?)

It's not really possible otherwise to work on this, because there could be many things involved (once again the the input being present multiple times in the form, some QGIS bug in one of the functions used in your python expression, the python expression themselves, etc.)

from qgep.

Here's the qgep project with updated fields and type as it will be in qgep future .qgs project :

qgep.zip

I will list modifications in the right issue.

There is a QGIS issue with python default values for fields :

Python actions are called on every field update instead of only at the opening of the form even if the update default is not checked :

There's a problem hidden in QGIS that will break many .qgs projects using default "editable" values.

from qgep.

QGIS upstream issue.
qgis/QGIS#51543

from qgep.

fixed by qgis/QGIS#51836

from qgep.

Integrated in QGIS 3.28.4-2! Installed and tested with osgeo4w, work as expected!

from qgep.