Problem

I discovered that the minTextAdapt property in ScreenUtilInit is ignored in the library's current version.

This happens because ScreenUtilInit initializes with a default fontSizeResolver of FontSizeResolvers.width:

this.fontSizeResolver = FontSizeResolvers.width,

Because setSp prioritizes the resolver if it is not null, the logic delegates to setWidth. This completely bypasses the internal scaleText getter where the minTextAdapt logic is being used. Because of this, text always scales based on width, even when the user explicitly sets minTextAdapt: true.

Solution

I have introduced a new resolver method and updated the default behavior:

Added FontSizeResolvers.auto: This new static method calculates font size using instance.scaleText. This ensures that the minTextAdapt logic (which chooses the minimum between width and height scaling) is respected.

static double auto(num fontSize, ScreenUtil instance) {
 return fontSize * instance.scaleText;
}

Updated Default in ScreenUtilInit: Changed the default fontSizeResolver from .width to .auto.

Technical Note

In FontSizeResolvers.auto, I am performing the math directly (fontSize * instance.scaleText) rather than calling instance.setSp(fontSize). This is intentional to prevent an infinite recursion loop, as setSp internally calls the resolver.

Impact

• For users with minTextAdapt: false (Default): No change in behavior. scaleText falls back to scaleWidth, so it matches the previous .width behavior.
• For users with minTextAdapt: true: The feature will now work as intended, preventing text from becoming excessively large on wide screens (like tablets or web).

Checklist

• The code compiles correctly.
• Tested with minTextAdapt: true (verified text scales using the smaller factor).
• Tested with minTextAdapt: false (verified text scales using width).