With the newer changes the image resizing mode option is more of an illusion of choice than a real choice.
The option only happens to be used if all of the following conditions fails:
The image isn't set to be stretched to fit within the widget it belongs to. (Since this is now hardcoded to smooth.)
The original image size isn't bigger than the widget it belongs to. (This becomes hardcoded to smooth.)
The metadata of the image (e.g. in a char.ini) hasn't defined a specific resizing mode rule. (This rule also get ignored if the 2nd rule applies.)
Then and only then the user's option a is used ONLY if they pick smooth resizing. If anything, the user's option becomes an exception rather than the rule, which defeats the purpose of the option since it's not listened to 90% of the time. Just make the system simpler: only allow images to use pixelated resizing mode if the metadata regarding that image tells you to and if missing, just fallback on the regular deduction.
With the newer changes the image resizing mode option is more of an illusion of choice than a real choice.
The option only happens to be used if all of the following conditions fails:
Then and only then the user's option a is used ONLY if they pick smooth resizing. If anything, the user's option becomes an exception rather than the rule, which defeats the purpose of the option since it's not listened to 90% of the time. Just make the system simpler: only allow images to use pixelated resizing mode if the metadata regarding that image tells you to and if missing, just fallback on the regular deduction.