how to handle all the data from a test protocol with nearly 80 proofing steps? For every step there are fields ok/not ok with switching to error steps if neccessary. In addition there are a lot of mandatory fields which i highlight with colors (so i need a lot of variables to handle the colors). All data are stored in 6 tables to structure the data and handle the table limitations (~80 columns).
It is not possible to use the same variables on every step, so there are a lot of them
I discussed this with my support from DMGMORI but we have no better solution to handle this.
So i think it is also very user friendly to see the same input and selection fields i see at different places inside Tulip, like windows or MacOS does: the same file dialog all over the system.
My question is also: why do you use different selection/input dialogs? One with filter one without?