Feedback wanted: Should preflight be a command instead of always on?

Retrobatch
#1

I’m thinking of ways to speed up preflighting, especially for folks who have 2k+ images. And I’m wondering if maybe preflight should be something that’s done on command instead of an always on thing?

The advantage of this is that the CPU would no longer burn cycles just loading up images when they are going to have to be thrown out in a few seconds anyway, since you’re messing around with nodes.

Does anyone have an opinion one way or another? Do you like the always on preflight or not?

#2

For me pre-flight should be an option.

#3

I’d also go with option.

Maybe right next to the info-area at the top as a button that can quickly be toggled on and off. If it was in the preferences it would be more effort if you just wanted to en- or disable it briefly (I could image this to be a fairly common usecase).