Dave Nottage

You could use this as a starting point, or to learn from: https://github.com/DelphiWorlds/MiscStuff/blob/master/Test/RDSTwainTestCase.zip Though the code is pretty messy. I had a plan to re-organise it - maybe some day 🙂

You may also need to delete any cache-xxxxxx folders under PAServer/scratch-dir on the Mac, then import

As you discovered, it is being added during the build process. The value for exported is not in any configuration files so presumably it is hard-coded. The "easiest" way to fix this is to edit the generated AndroidManifest.xml, add it to the deployment and disable the one that Delphi would normally deploy. Of course this means having to repeat the process if you make any changes that affect the manifest. ..or you could use Delphi 11, where the problem has been fixed.

If you imported the iOS SDK before you installed the patches, you will need to re-import the SDK

If you haven't installed either the November or January patch, install that, then re-import the iOS SDK.

This answer has served me well for some time now: https://stackoverflow.com/a/13835244/3164070 however it does not work for when a user drags an attachment from Outlook (it works when dragging the entire email). Does anyone know if an object of a different name is created, or perhaps some other "event" occurs? I'm otherwise looking at installing a global mouse hook as @Remy Lebeau suggests in one of the other answers in the same SO post.

I'd like to know how it is the likely solution. Please refer to the original question. The problem I am trying to solve is in the original question. The "why" is that a WVD app is on the receiving end of the drag operation, and the virtual channel needs to register the WVD app window for drag/drop. The best time to do this is at the start of the operation. As I say, this has been working famously for standard drag/drop, but it does not work for dragging attachments out of Outlook

As promising as that looked, it didn't help 🙂

If you're using the original project, follow the steps here to ensure that it has references to the correct Android libraries: https://github.com/DelphiWorlds/HowTo/tree/main/Solutions/AndroidLibraries Delete the original AndroidManifest.template.xml, making sure you note any customizations you added yourself. Recompiling the project should recreate the AndroidManifest.template.xml file and you can add any customizations back in. I suspect the error messages you were seeing when you tried compiling with Delphi 10.4 may have been related to having an older AndroidManifest.template.xml. Assuming that you had not changed the %targetSdkVersion% part of AndroidManifest.template.xml, you will find that your app will now need to request permissions for "dangerous" permissions at runtime, so you will need to modify your code to suit. There's examples of how to do this in demos like in the camera component demo: https://github.com/Embarcadero/RADStudio11Demos/tree/main/Object Pascal/Mobile Snippets/CameraComponent and the location demo: https://github.com/Embarcadero/RADStudio11Demos/tree/main/Object Pascal/Mobile Snippets/Location If you opted to install the Android SDK/NDK files when you installed Delphi 11, when you add an SDK, it should default to the compatible values anyway.

I can understand that async dialogs are a concept that can be a challenge to embrace. Some time in the future we'll all be wondering why 😉

There's a good reason for that - implementing modal dialogs on Android the same way as on Windows is practically impossible. The workaround is to use async dialogs. Developers do this on Windows all the time - from one form, show another. When the user takes some action on the secondary form, do something based on that action, and close the form. The primary form will still be there when they get back 🙂 If the primary form needs to "know" what happened on the secondary form, you could expose a property or event handler on the secondary form which the primary form can examine, or handle.

For Android, this is the only way I've found that will quit completely and remove the task from the "recent items" list: https://github.com/DelphiWorlds/Kastri/blob/64a5600e0845862f3e3991cd1708dee82a65ff45/Core/DW.Android.Helpers.pas#L561 For iOS, it's bound to have your app rejected if it is on the App Store, otherwise: https://developer.apple.com/library/archive/qa/qa1561/_index.html

This might apply to you: https://github.com/DelphiWorlds/HowTo/tree/main/Solutions/AndroidLibraries

Please see: https://github.com/DelphiWorlds/HowTo/tree/main/Solutions/AndroidLibraries

I've just added a new demo: https://github.com/DelphiWorlds/Playground/tree/main/Demos/Advertising to the Playground repo

On Android, it's not meant to be written to by the app. What is the reason why you're using that folder to write to?

I don't know of any option for df that means it needs to wait for input

You said you are running apps that result in: Process terminated with exit code: 0. Stockfish just locked up on me - regardless of whether or not it's waiting for input, that's not what you described

Which libraries are they? Have you read their documentation to see if they actually wait for input while they're running?

https://www.google.com/search?q=movie+format+compatible+across+platforms

Use the IsRunning property

I had originally planned on having a commercial version, however those plans changed. Now Kastri is driven mostly by sponsorship and one-off donations. Kastri Free is deprecated and developers should use Kastri instead.

if you're planning on deploying to the Play Store, staying current is a better option.

It runs on my Android 11 device when I build it with Delphi 11. If you're using 10.4.1, you should go to the Libraries node under the Android platform in Project Manager, right click it and click Revert System Files To Default. Like this, but you're going back a version: https://github.com/DelphiWorlds/HowTo/tree/main/Solutions/AndroidLibraries

There may not be one, although this link (from the one you gave) might help: https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Mobile_Tutorials:_Mobile_Application_Development_(iOS_and_Android) It might be easier to ask here if there is an implementation of what you want to use, or scan the Delphi source.