Skip to content
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

GridSplitter not working #18215

Closed
MartinZikmund opened this issue Sep 16, 2024 · 9 comments
Closed

GridSplitter not working #18215

MartinZikmund opened this issue Sep 16, 2024 · 9 comments
Assignees
Labels
area/windows-community-toolkit 🎚️ Categorizes an issue or PR as relevant to the Windows Community Toolkit kind/regression Something was working, now it isn't project/third-party 3️⃣ Categorizes an issue or PR as relevant to 3rd party libraries

Comments

@MartinZikmund
Copy link
Member

Greatly appreciated the quick response! I did just that and conclude that is too simple, once you create a new project just replace the MainPage with a grid (3 columns) and try to put the GridSplitter in the middle column. I did found that the current version (8.1.240821) you will not be able to find the expected splitters in the namespace, but as soon as you change to the previous version (8.0.240109) you will be able to see the expected splitters... Can you please take a look on why the "current version" is not surfacing the Sizer controls?

Originally posted by @datovy-edam in #18151 (comment)

@MartinZikmund MartinZikmund added project/third-party 3️⃣ Categorizes an issue or PR as relevant to 3rd party libraries kind/regression Something was working, now it isn't area/windows-community-toolkit 🎚️ Categorizes an issue or PR as relevant to the Windows Community Toolkit labels Sep 17, 2024
@agneszitte
Copy link
Contributor

@MartinZikmund I will take a quick look as I am testing WCT samples at the moment while adjusting the documentation

@agneszitte agneszitte self-assigned this Oct 21, 2024
@datovy-edam
Copy link

Note that in version (8.0.240109) the splitter works as expected under the Windows platform but not under the WebAssembly platform! Still, all other rendered components (not the splitters) work as expected and look identical to each other... very nice.

On another subject:
Also, the DockPanel works on the Windows platform and not under WebAssembly. I already switch and use a StackPanel in place of the DockPanel, but it does not provide the visual I like... But works fine in both platforms.

Hope to see the splitters issues resolved soon...

@MartinZikmund
Copy link
Member Author

@datovy-edam thank you for the information, we will investigate this and let you know ASAP.

@MartinZikmund
Copy link
Member Author

MartinZikmund commented Oct 28, 2024

@morning4coffe-dev can you please validate DockPanel and GridSplitter on WASM in version 8.0.240109?

@morning4coffe-dev
Copy link
Member

morning4coffe-dev commented Oct 29, 2024

@MartinZikmund, @datovy-edam
I have tested this with 8.0.240109, where the controls don't render at all on any Uno targets, and with the latest stable version, 8.1.240916, where everything works as expected across all platforms.

image

@datovy-edam
Are you able to use the latest stable version? There are some requirements to make this work with Windows as well. If you need help, feel free to check out my sample (WCTControlsSample.zip) and compare the .csproj file with your project.

@jeromelaban
Copy link
Member

Thanks, let's close then!

@datovy-edam
Copy link

datovy-edam commented Nov 11, 2024 via email

@jeromelaban
Copy link
Member

jeromelaban commented Nov 11, 2024

For the unpackaged not being selectable: https://aka.platform.uno/wasdk-maui-debug-profile-issue and this workaround in your project.

@datovy-edam
Copy link

datovy-edam commented Nov 11, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/windows-community-toolkit 🎚️ Categorizes an issue or PR as relevant to the Windows Community Toolkit kind/regression Something was working, now it isn't project/third-party 3️⃣ Categorizes an issue or PR as relevant to 3rd party libraries
Projects
None yet
Development

No branches or pull requests

5 participants