Niels Rademaker

I was able to solve that repeat click issue easily. I also got a hard crash when I tried to reproduce the situation in Steve's vid by adding the Discount variable and connecting the wiring from a lock element... Error log shows: electron: ravelState.cc:114: vector<civita::tensorptr> ravel::createRavelChain(const ravel::RavelState &, const civita::TensorPtr &): Assertion `i.order==ravel::HandleSort::none' failed.</civita::tensorptr> ps. it's concerning to me that the application crashes completely...

I was able to solve that repeat click issue easily. I also got a hard crash when I tried to reproduce the situation in Steve's vid by adding the Discount variable and connecting the wiring from a lock element... Error log shows: electron: ravelState.cc:114: vector<civita::tensorptr> ravel::createRavelChain(const ravel::RavelState &, const civita::TensorPtr &): Assertion `i.order==ravel::HandleSort::none' failed.</civita::tensorptr>

Having trouble reproducing this with the .rvl file provided... I did notice there's some ugly repeat draw behavior when clicking the equations tab several times and then trying to go back to wiring...

Is it an idea to disable input to the main window while the CSV import dialog is open? I've always considered that a bit dodgy in the first place.

I've created a PR for Russell to review with only the extra input fields and no changes to the layout of the dialog yet. Please let me know if I should spend time on the rest... I think it would just be an hour of work or so.

There are currently already a lot of input fields in the header and this adds three more to the score... From a UX point of view, I would recommend refactoring this into a tabs-based arrangement, with the last tab reserving all space for the preview grid. We would probably only need one tab for the input fields, but we could also reserve a whole tab for the selection of a file, to create more of a wizard-like experience where the user's attention is directed to one step at a time.

There are currently already a lot of input fields in the header and this adds three more to the score... From a UX point of view, I would recommend refactoring this into a tabs-based arrangement, with the last tab reserving all space for the preview grid. We would probably only need one tab for the input fields.

I'll pick this up if Russell hasn't started on it yet.