![]() ![]() Things like legacy Android and Windows and macOS do actually take into account the background shape. Maybe we need resizetizer to be smarter and make the foreground bigger on the ones that don't have a safe area - Windows, macOS and Tizen. And when I say "legacy" I mean Android 7 and older. But this does not play well in the cases of the mobile needing the new way. csproj to be "if mac / windows, use the desktop-y - else use the mobile-y". Link to public reproduction project repositoryħ.0 Release Candidate 2 Last version that worked wellĪt this point, are we maybe looking for 2 styles of icons and somehow convey that in the template or extend the MauiIcon MSBuild item? Observe the generated images are not consistent.Does not allow custom shapes, will fill with black. ![]() Crops the adaptive icons by 1/6 all round.this is exactly what is happening with adaptive icons anyway.no way for the dev to provide a custom icon shape.We can copy Android Studio and totally scale up both layers and apply our own clipping and shadow.we may cover background corners/edges if the foreground gets too big.we may lose image data on the edges (but we do already in adaptive).both the background and foreground are clipped 18dp.the icons will look strange if the foreground image is not transparent during parallax.We can scale down the adaptive foreground images.But we need to ensure the final images are drawn correctly. Not sure the correct approach here as the developer may want to have cool things on those edges. The outer 18 dp on each of the four sides of the layers are reserved for masking and to create visual effects such as parallax or pulsing.In order for cool effects, the icon is actually cropped in by 18dp: This is because legacy icons are not actually displayed in a normal layered way. Ignoring the different final image sizes, we can also see the space around the legacy is larger. We generate adaptive icons and 1 legacy icon: Circle However, for adaptive icons this is not true.Īssuming the following 2 images: Background Currently we generate all the images, assuming all the image is visible on screen. ![]()
0 Comments
Leave a Reply. |