-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Label Shadow not working correctly on Windows #6150
Comments
@pierre01 , could you share the style of FoodCategoriesLabel which can help us to reproduce this issue? |
@shimingsg
|
@pierre01 , sorry I don't have windows 11. here is my demo project for your reference, I'd like to suggest to verify if the latest VS has the same issue on your environment. |
Compiling your code I get an error: 1>C:\Program Files\dotnet\packs\Microsoft.Maui.Resizetizer.Sdk\6.0.300-rc.1.5355\targets\Microsoft.Maui.Resizetizer.targets(571,9): error : ApplicationId 'com.companyname.mauiapp99875' was not a valid GUID. Windows apps use a GUID for an application ID instead of the reverse domain used by Android and/or iOS apps.
|
@shimingsg Thanks for taking the time to reproduce the issue... Your code works But the example I used does not work on windows (it does work on android). Now, I wonder if the issue is caused by the images in the background of the CollectionView Items. |
@shimingsg |
Putting an image in the background of the CollectionView ItemTemplate causes the bug. |
Description
The label shadow does not render at the location of the label neither does it render in the right size
Steps to Reproduce
Create a label : the example in the image above is in a template for a collectionView
Expected :The Shadow should appear underneath the label with the same character size
Result: see image above
Version with bug
Release Candidate 1 (current)
Last version that worked well
Works on Android not windows.
Affected platforms
Windows
Affected platform versions
Windows 11 Pro 22000.408
Did you find any workaround?
No
Relevant log output
No response
The text was updated successfully, but these errors were encountered: