Open haalasz opened 2 months ago
1/ Row numbers:
* Display row numbers alongside the table to help users easily identify and reference the row they are working on. This number should be visible only within the app and not saved with the table data. These row numbers should scroll vertically with the table.
I was thinking about fixing the sample id on the left edge of each row. Should we add that, or is row number enough?
1/ Row numbers:
* Display row numbers alongside the table to help users easily identify and reference the row they are working on. This number should be visible only within the app and not saved with the table data. These row numbers should scroll vertically with the table.
I was thinking about fixing the sample id on the left edge of each row. Should we add that, or is row number enough?
I would like to see the row numbers instead of fixed sample ids, since the app finds errors and prints out the message based on row numbers. It should be easier for the users to match the error messages to the fixed row numbers to correct or add required data.
since the app finds errors and prints out the message based on row numbers
You're absolutely right, I didn't think about that.
@iwmstjp Something odd happened when I tried the application. After I had imported the sample file (99 rows), in the table view two empty input fields appeared instead of the duplicate and delete buttons (the columns' names were still Duplicate and Delete). Then I'm not sure what I did, but the browser displayed a "connection was reset" error screen. Then I think I pushed Back, got back to the opening screen where the file was still shown as selected. When I pushed the import button again, the table was displayed correctly with delete and duplicate buttons. I don't know whether Flask has a log that could help resolve this, but please check if you find anything. The error occurred around 14:00, just now. I'm not sure whether this was a problem with my browser or with the application, but I suspect the application since everything else seems to work correctly with my browser.
I tried to check log files like syslog, syslog.1, cloud-init-output.log and so on which LLM recommeded to check but I do not have permissions.
I tried to check log files like syslog, syslog.1, cloud-init-output.log and so on which LLM recommeded to check but I do not have permissions.
You do, you just need to add sudo
to the command as always. The ubuntu user that you are logging in with is a sudoer. You don't even need to enter a password.
1/ Row numbers:
2/ Always visible action buttons (low priority)
Old layout:
Proposed new layout: