You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I set IsEnabled=false by default for SplitButton, then I enabled it e.g. by binding, the control is rendered wrong until I hover over the control. After the hover over the control, it is drawn correctly. (See attached pictures)
There is workaround but ofc it's not ideal. The workaround is to have IsEnabled = enable at the start and switch false to on loaded event. Then it looks like it works fine.
Steps to reproduce the bug
I attached an app sample but short the steps are following:
Create simple xaml with SplitButton control:
Enable split button
2. Create Enabled property that has "False" value
3. Change the Enabled property to True when the item is rendered.
4.
[sample.zip](https://github.com/microsoft/WindowsAppSDK/files/15308750/sample.zip)
Expected behavior
The SplitButton should be rendered in the same way as it is when the SplitButton is enabled by default from the app start.
Screenshots
After start
After enabling the SplitButton
After hovering over the control and put mouse control out of the control rectangle
NuGet package version
Windows App SDK 1.5.3: 1.5.240428000
Packaging type
Unpackaged
Windows version
Windows 10 version 22H2 (19045, 2022 Update)
IDE
Visual Studio 2022-preview
Additional context
No response
The text was updated successfully, but these errors were encountered:
Prochy
changed the title
SplitButton is drawed incorrectly when IsEnabled=false by default and then enabled
SplitButton is drawed incorrectly when IsEnabled=false by default and then enabled back
May 14, 2024
Describe the bug
If I set IsEnabled=false by default for SplitButton, then I enabled it e.g. by binding, the control is rendered wrong until I hover over the control. After the hover over the control, it is drawn correctly. (See attached pictures)
There is workaround but ofc it's not ideal. The workaround is to have IsEnabled = enable at the start and switch false to on loaded event. Then it looks like it works fine.
Steps to reproduce the bug
I attached an app sample but short the steps are following:
Enable split button
Expected behavior
The SplitButton should be rendered in the same way as it is when the SplitButton is enabled by default from the app start.
Screenshots
After start
After enabling the SplitButton
After hovering over the control and put mouse control out of the control rectangle
NuGet package version
Windows App SDK 1.5.3: 1.5.240428000
Packaging type
Unpackaged
Windows version
Windows 10 version 22H2 (19045, 2022 Update)
IDE
Visual Studio 2022-preview
Additional context
No response
The text was updated successfully, but these errors were encountered: