Device.GetNamedSize obsolete. Alternative?

[hbraasch]

What is the alternative to [Device.GetNamedSize], which is now marked as obsolete?
Thanks

[Kapusch]

As per this comment from Gerald:

NamedSize should not be used nor needed anymore. All the fontsizes now automatically scale as per the OS settings. This improves accessibility overall.

[JohnHDev]

Which is a nonsense answer, and typical of the direction that Maui is being taken in. Deprecate something and don't inform us what we should to do instead. What should we do when we want different known sizes? We can create our own enum, but wait surely that should exist in Maui...

[Ghostbird]

Yup, stuck with this as well. I understand perfectly well that I can now use device independent units as float, and that those are much better. But what value do I have to use? I have to migrate something from NamedSize.Medium to ???

UPDATE: I checked the Android specific implementation of the deprecated logic. If I understood it correctly:

// as decreed by the android docs, ALL HAIL THE ANDROID DOCS, ALL GLORY TO THE DOCS, PRAISE HYPNOTOAD

NamedSize.Medium is probably 14

[mdelgadov]

On this topic, a good replacement would be Fluent 2 table that has equivalencies for different environments:

https://fluent2.microsoft.design/typography

As you can see, one set of strings and bob's your uncle...

I have that in my project already but I don't know how to express it in Styles

[Ghostbird]

I think that when you take this approach, you're going to duplicate stuff that doesn't need duplication. When you create a new MAUI program, you already get such definitions in Styles.xaml, where e.g. it is defined that Buttons have FontSize 14. I think the crux of this discussion is that if I previously used the Xamarin definition NamedSize.Medium in a custom control, I need to know what value to choose for FontSize when I add my own style, to have it work well with the rest of the UI. Once I have a good value locked in, I'm migrated, and unless I overhaul the styles, I do not need to ever change it.

As I mentioned above, I found that in my migration using FontSize 14 where I previously used NamedSize.Medium gave a good result. However it would have been nice if MAUI had published a recommended mapping to ease this process. Of course the entire reason, the change was necessary, is that the old NamedSize mechanism was so terrible, that it was in fact impossible to publish a complete and correct mapping. The meaning of the NamedSizes varied wildly, between platforms, but even between different controls on the same screen.

[hbraasch]

Thanks.

[ouijahija]

[rant]
JFC... This is such a joke. Either make sure that basic functions that replace those of Xamarin are implemented or don't deprecate Xamarin Forms! How can you force the userbase to use the "new and improved" Maui when it's clearly still lacking in so many places?
[/rant]

[Ghostbird]

You misunderstand. It was perfectly implemented. It's just that when migrating, we now don't know what values to choose. It would have been nice if there'd been some guidelines on this.

The reason why this stuff is deprecated, is that there was no correct and complete mapping. The actual sizes associated with the named sizes varied wildly depending on the platform, and the control they were applied to.

The new implementation is much better. If you use 12, it should be similar on each device, and identical in all controls on the same device. 14 is a proportionate amount larger on all devices and controls. Previously it was very much possible that NamedSize.Medium was actually larger than NamedSize.Large in some situation, and NamedSize.Default was often a different size than NamedSize.Default in a different control on the same screen.