There are still some occasional issues with loading cross-sections.
It seems that when loading a cross-section from the User Defined Channel tab the cross-section display is refreshed the first time, but if you load another cross-section you sometimes need to adjust slope or roughness coefficient or units to force it to refresh.
This is very confusing for the user
Without looking at the code it seems strange that the issue does not always occur, but maybe there is a simple fix.
I think the issue is that we support either increasing or decreasing chainages, but if the first two chainages are equal it assumes chainages are increasing, and in this case they are decreasing.
Presumably this will be a fairly easy fix (e.g. comparing the first and last chainage), but we should look at adding a different error message if there is a chainage which increases when the rest are decreasing, or vice versa.
There are still some occasional issues with loading cross-sections.
It seems that when loading a cross-section from the User Defined Channel tab the cross-section display is refreshed the first time, but if you load another cross-section you sometimes need to adjust slope or roughness coefficient or units to force it to refresh. This is very confusing for the user Without looking at the code it seems strange that the issue does not always occur, but maybe there is a simple fix.
This fails to load, with "channel not found":
I think the issue is that we support either increasing or decreasing chainages, but if the first two chainages are equal it assumes chainages are increasing, and in this case they are decreasing. Presumably this will be a fairly easy fix (e.g. comparing the first and last chainage), but we should look at adding a different error message if there is a chainage which increases when the rest are decreasing, or vice versa.