openfedem / fedem-gui

Graphical user interface for FEDEM
https://openfedem.org
Apache License 2.0
0 stars 1 forks source link

Creating function "Polyline from file" not working properly with 1 data column #25

Closed kristsaet closed 3 days ago

kristsaet commented 4 days ago

As pr. topic.

If one import a poly-line from file with only 1 data-channel you are not able to really select which of the data columns to use. Ideally it should just auto-select the only one actually available in the input-file, or at least let you select it manually.

kmokstad commented 4 days ago

Didn't quite get this one either. A single-column file will not work, of course. As it needs the first column for the X-axis values (always) and then the 2nd column for the Y-axis values. Only if there are more than two columns in the file it makes sense with some user interaction to choose which column/channel (this has to be column 2 or higher, never column 1 which is reserved for the X-axis).

kristsaet commented 4 days ago

Once again not very precise explanation. But I ment 1 data column in addition to the time column. I.e. 1 time dependent data channel.

kristsaet commented 4 days ago

Select button is greyed out: image

kmokstad commented 4 days ago

Yes, and in this case the second column in the file is auto-selected as the data channel (Y-axis values when plotting it). Maybe the confusion is the "Not set" label in the Channel field. It would be better perhaps to actually display the label of that column in the file here (if the file contains one which is not required for two-column files). But the function will/should work as it is now also, at least I could not reproduce any error.

kristsaet commented 4 days ago

At least it is not possible to get a preview of the file, it shows blank time-axis in this case. image

kmokstad commented 4 days ago

This is probably due to the same error that was fixed in openfedem/fedem-foundation#11. But I'll fix the Channel field such that it will show the label of the data column, if present, and close this issue. Please reopen with more details if the problem persists in the new version.