-
Notifications
You must be signed in to change notification settings - Fork 1.8k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
[Spec] Deconstruct DualScreen Nuget into Essentials and Maui.Core (Investigating) #1164
Comments
The Xamarin.AndroidX.Window binding has been updated to match latest Google (details here), and the Xamarin Surface Duo samples are updated to use it. For .NET MAUI, the ideal situation would be:
The first two bullets are probably the minimum we need to to ensure customers can continue to build dual-screen apps. The third bullet (and the topic of this issue) is a desirable update which would bring compatibility to a wider variety of devices such as foldables from other manufacturers. |
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
Can this be reconsidered before year's end? |
@DamianSuess the NuGet should be available now, released as part of .NET 7. @logikonline why is it of particular interest to you? The functionality is available in a NuGet right now, this only speaks of refactoring some code basically. |
@jfversluis you're the man! I'll be sure we'll get it into our next sprint for validation w/ our project. |
For the same reason @DamianSuess outlined, I moved a large project to Maui, but I am one of the outliers that have a Duo 2 and like to offer a better experience for those devices too. If in your refactoring, can you also provide an option on the Shell to recognize the control being used on the page. The reason for this, if a Duo is in full-screen mode (across both screens), the tabbar will try to center, and the middle tab is unusable. I resolved this with a custom renderer on the old MasterDetail to change the gravity of the menu to favor a right or left align. The Shell really should offer this to make the Duo usable imo. |
Gotcha! But then, if I understand correctly @logikonline you're more interested in this functionality being available (which it is now) than this code being in a different place (what this issue is technically about)? As for features, it's probably best to open something new if you want to see things added/changed. You already did mention though yourself that you are probably one of the outliers so I'm not sure how high it would rank in terms of priority. If this is something you'd really like, maybe it would be best to see if you can help us (and thus yourself) out by making one or more contributions. |
No. I'll continue to write the custom renderer for the Shell, but I can't offer the functionality for the Duo since it is only available for XF. But if the individual brings the code to refactor to Maui does the work, it would be nice if they provided the addition since it isn't in XF & is a known limitation. I view Maui as an improvement in the experience, not merely a translation. An outlier is that I have a Duo, although that is exclusively a Microsoft product which other vendors will show bias to their platforms. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Merge DualScreen nuget into Maui.Controls and Maui.Essentials
The text was updated successfully, but these errors were encountered: