Forum Widgets
Latest Discussions
Default behavior for Dual Screen Seem (Hinge GAP)
When an app is spanned across two screens, there is going to be aseam— the space between the two screens. This is a byproduct of making a dual-screen device. This section talks about some of the ideas and techniques you might consider to make your app work with the seam. By default Display driver must skip (should not render behind seem) the content behind the hinge GAP. It should be continuous across screens. In fact the app developer should not be even aware of the seem. It should see as one continuous screen. It enables all web sites and apps usable by default. If any app or site wants to do differently to take advantage of dual screens then they use your API to handle it. This is a very simple approach and I think somebody at Microsoft screwed it up up by opting to ask every developer in the world to optimize their content. This will never happen. Duo will fail if not fixed. If I don't get this behavior in the next DUO update I will return my DUO and start a campaign to return all duo owners. I'm Software Architect love this duo and don't want it to fail. This is the only feature missing in this duo. I use only 3 apps on this. Edge, Chrome and Remote Desktop. All three are hiding content behind seem. This default behavior would have made made all these three apps usable.
is TwoPaneBackStackEntry composable list of routes incompatible with arguments / URI Routes?
Hello, I am doing some tests on the SDK and have encountered a roadblock. Currently, my application uses route arguments to find item details. However, upon navigating to them, the following exception is returned: java.lang.IllegalArgumentException: Invalid route item/4, not present in list of routes [home?, items?, item/{itemId}, ...] I am unsure if this is a problem stemming from the fact that listOf[Routes] cannot take into account those values or if it is an error on my end. Could you please clarify? Thank you for all your hard work!How to start the SurfaceDuo 2 emulator on an Apple M1 device?
Hi team, I know I had the same questions a few month ago, but I want to bring it up again. Currently I'm using an Apple M1 Mac as my development machine. Everything works expect of the Surface Duo 2 emulator. In short: I cannot find where I can change it from trying to use qemu-system-x86_64 instead of the installed qemu-system-aarch64 one. Facts: M1 Mac MacOS Monterey Android Studio installed AS emulators starts as expected `run.sh` fails because of x86 linked emulator Thanks for any helpful tip!Looking for MVP 22/23 recommendations (who to follow)
Hi team, the new MVP year started and I just wanted to ask if someone of you has recommendation who to follow on Twitch, GitHub, Twitter, etc. I know there is no MVP program related to the Surface Duo community, but maybe there are some Xamarin or other MVPs that are also covering this topic 🙂 Thanks a lot in advance and let's grow this community!
