Breaking Polefigure by Userinput

I've noticed that it is possible to break the Polefigure by user input to a point where the program is massively slowed down and even can crash.

How to reproduce:

• Follow the workflow normally
• Change pixel dx/dy settings in the Detector tab
• Change the pixel offset dx and/or dy setting in the Detector tab

Those three items correspond to these three screenshots:

Though it is a good thing that a programs allows as much freedom to the user as possible, I think it should not go that far.

I suggest to either limit the values which are accepted to the input elements from the user or to reset other values when they are incompatible and would lead to such output. I personally would prefer the first strategy since it would be rather easy to overlook and confusing to the user when the programs starts to change input values which are not in the focus of the user. I also think the program should communicate incompatible input values or a wrong workflow process to the user to prevent outputs like this.