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 a seam — 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.[Thread] Showcase your Surface Duo apps!
This thread is meant to be a showcase of your awesome apps that are based on thr Surface Duo SDK. Share your hard work and ideas on how the unique features of this dual screen device could be used. ---------- Name #rTsd (Road to Surface Duo) Genre News Development ecosystem Xamarin.Forms Abstract This is a work in progress https://dotnet.microsoft.com/apps/xamarin Android project which is intended to feature most of the new features that makes the upcoming https://www.microsoft.com/en-us/surface/devices/surface-duo phone unique. It will use the awesome German https://www.drwindows.de/ as data source for its articles. Screenshots Links The source is open source on a https://github.com/tscholze/xamarin-road-to-surface-duo. This app will not be released in the Google Play Store.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!Thank you MSFT folks! My very first Android app (w/ Duo SDK) is now available in the Play Store
Hi team, I know that for many of you that's not something to be happy and proud about it. Last week I published my very first Android app to the Play Store. Of course, it uses the great Surface Duo SDK for Xamarin. The app is content-related German only. I just wanna say thank you to guymerin , Hakon_Strande, and all of your team mates for your great work and encouraging new Android developers to give it a try. Links: https://play.google.com/store/apps/details?id=io.github.tscholze.rtsd https://github.com/tscholze/xamarin-road-to-surface-duoFirst update to the Surface Duo SDK Preview Release is live!
The update aims to improve appcompat on the Duo when apps are running on a single screen. Read about it in the devblog: https://devblogs.microsoft.com/surface-duo/the-surface-duo-sdk-preview-is-getting-an-update-feb-202020/ You can download the updated SDK images for Mac, Windows and Ubuntu using this https://www.microsoft.com/en-us/download/details.aspx?id=100847. We are also in the news! 🙂 There is an article about this update here: https://www.windowscentral.com/surface-duo-preview-sdk-has-its-first-update Keep the feedback coming!Lessons learned: Updating an app from copied Duo lib files to Xamarin.Forms.DualScreen NuGet package
I just updated my https://github.com/tscholze/xamarin-road-to-surface-duo to use the freshly released https://www.nuget.org/packages/Xamarin.Forms.DualScreen/4.5.0.282-pre4. That's why I wanna share my lessons learned, maybe some will be for others obvious, maybe not. Do not forget Update Xamarin.Forms package, to the latest pre-release (don't forget to mark the checkbox) Install the Xamarin.Forms.DualScreen package, it's a pre-release (don't forget to mark the checkbox) Delete all old copy-and-pasted "Duo Lib" that you copy pasted from the very first sample project Embed new namespace in duo-specific (e.g. master/detail pages) files xmlns:dualScreen="clr-namespace:Xamarin.Forms.DualScreen;assembly=Xamarin.Forms.DualScreen" Update, usage of TwoPaneView to new syntax with child elements <dualScreen:TwoPaneView> <dualScreen:TwoPaneView.Pane1> <views:ItemsView x:Name="MasterPane" /> </dualScreen:TwoPaneView.Pane1> <dualScreen:TwoPaneView.Pane2> <views:ItemView x:Name="DetailPane" /> </dualScreen:TwoPaneView.Pane2> </dualScreen:TwoPaneView> Check if you set the config values correct in the MainActivity.cs to listen on Duo-specific changes ConfigurationChanges = ConfigChanges.ScreenSize | ConfigChanges.Orientation | ConfigChanges.ScreenLayout | ConfigChanges.SmallestScreenSize Conclusion It's great to see that you do not longer need copy & (w/p)asted files in your library. There are not really breaking changes. It took me max. an hour to update my app.
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!Display/Screen/Fold info from (accessibility) service
I'm trying to adapt my accessibility service app (https://play.google.com/store/apps/details?id=com.quickcursor to Surface Duo foldable screens and found some inconveniences and issues: https://developer.android.com/reference/android/accessibilityservice/AccessibilityService#dispatchGesture(android.accessibilityservice.GestureDescription,%20android.accessibilityservice.AccessibilityService.GestureResultCallback,%20android.os.Handler) doesn't respect the screen coordinates when the device is using the right screen on single screen mode. Sample code: https://github.com/micku7zu/SurfaceDuoDispathGestureBug Sample video: https://streamable.com/z7cgub In the video there are 2 buttons that dispatch click at (300,300) and (1350+300, 300) coordinates. As you can see, the buttons are positioned at (400,100) and (800,100) and when only the right screen is used, the buttons are positioned correctly on the screen, but the click dispatch coordinates are not correct, clicking on (300, 300) clicks on the left screen (which is turned off). If this is not a bug, and in fact this is intended, than there should be a way to detect the screen which is used from an (accessibility) service context in order to adjust the coordinates from the app. All the SDK libraries for display/fold info are based on Activities, and no info from a service. The other inconvenience is that there is currently no way to detect the current state of the fold/display from an (accessibility) service (or I didn't find any) straight forward. All the SDK Duo libraries are based on UI Activities. I understand that the helper libraries are focused on UI Activities, but accessibility services shouldn't be left out, there are users that needs this services for easier use of the device. A solution that works on most foldable devices (from my app user feedback): WindowManager windowManager = (WindowManager) context.getSystemService(Context.WINDOW_SERVICE); Display display = windowManager.getDefaultDisplay(); Point displaySize = new Point(); display.getRealSize(displaySize); Doesn't work on Surface Duo as it should (in my opinion). The display returned by DisplayManager or WindowManager is not updated. There is only one display with the same values on all possible fold states. On other foldable devices this display values are updated/a list of displays. Some practical examples that are really hard to do in an accessibility service without an UI activity: How to get the current resolution (1350x1800 or 2700x1800)? How to get the hinge rect? How to get which part of the display is active (left or right)? I've made some ugly hacks for Surface Duo for the above problems, but this shouldn't be the case. I've not tested on all foldable devices, but currently from my app user feedback the issues are only on Surface Duo, other foldable devices are running ok without any special needs. I didn't fixed yet the left/right screen detection to adjust the coordinates for the right screen because I'm tired of looking for hacks. Probably there is a sketchy way to detect this, but I'm out of ideas for the moment. Any idea how I could get over these issues more easily? Thanks!
Trouble creating webapp for dual-screen
Hello, I wanted to create an webapp/website that is aware that the browser is spanned. While my webapp works with the experimental web platform features on Edge on the surface duo emulator and the browser's devtools. I can't get it to work on the actual surface duo device. I tried on both edge canary and chrome canary latest builds but to no avail. I'm using the css media spanning queries and the react package described in a surface duo blog post here to easily detect for a dual-screen: https://devblogs.microsoft.com/surface-duo/dual-screen-react-web/ Spanned browser on the emulator edge: Spanned browser on the surface duo (edge canary): Is this experimental feature not yet available on the canary builds of the 2 chromium browsers, or am I missing something?
