Add logic to handle titles, headers, or other non-view bars Public static Rect GetAbsoluteBounds(this element) Here is an extension method that helps calculate the bounds of a view: public static class ViewHelpers PresentationSourceBounds = DeviceInfo.Platform = DevicePlatform.iOS & DeviceInfo.Idiom = DeviceIdiom.TabletĪwait Launcher.OpenAsync(new OpenFileRequestĮverything described here works equally for Share and Launcher. You can specify the location using the PresentationSourceBounds property: await Share.RequestAsync(new ShareFileRequest This location is often the control that launched the action. This specifies where the popover will appear and point an arrow directly to. When requesting a share or opening launcher on iPadOS, you can present it in a popover. System.IO.File.WriteAllText(file, "Hello World") Īwait (new OpenFileRequest(popoverTitle, new ReadOnlyFile(file))) String file = System.IO.Path.Combine(FileSystem.CacheDirectory, name) The following code example writes text to a file, and opens the text file with the launcher: string popoverTitle = "Read text file" If more than one app is registered with the file type, an app selection popover is shown to the user. The launcher can also be used to open an app with a selected file.NET MAUI automatically detects the file type (MIME), and opens the default app for that file type. The previous code example can be simplified by using the TryOpenAsync(Uri), which checks if the URI scheme can be opened, before opening it: bool launcherOpened = await ("lyft://ridetype?id=lyft_line") The following code demonstrates how to check if a URI scheme is supported or not, and then opens the URI: bool supportsUri = await ("lyft://") Īwait ("lyft://ridetype?id=lyft_line") Optionally, the ILauncher.CanOpenAsync(Uri) method can be used to check if the URI scheme can be handled by an app on the device. To use the Launcher functionality, call the ILauncher.OpenAsync method and pass in a String or Uri representing the app to open. You can't use schemes outside of this list. The elements are the URI schemes preregistered with your app. Add the LSApplicationQueriesSchemes key and schemes to the Platforms/iOS/ist and Platforms/MacCatalyst/ist files: LSApplicationQueriesSchemes Apple requires that you define the schemes you want to use.
0 kommentar(er)
