Sherlock

Since nothing is as volatile as a web thing, consider keeping that in a text file and load it once your application has started. This gives you the added benefit of being able to change this HTML-File without the need for an update.

Ohhh, OK. Thanks. I thought I had been sidestepping an extremely powerful library here.

Is all that part of the OTL? Then I definitely have to look into that.

Please, don't remove "old examples" validate your code against them and update the examples if needed. For me it is very hard to use anything without a near complete set of examples.

I too am a Consolas guy.

Fellas, please. If Attila thinks he gave enough information, you have two options: Either write an answer based on that, or don't write at all. This should please not escalate.

I get that, really I do, but my brain hurts...

According to the msdn, this is the meaning of the error number: This of course could mean, that your XP can't communicate with the https server you are trying to contact...or anything else that might go wrong with a severely outdated system trying to communicate within a network.

I finally got around to installing 10.3.3 and now I get this message every time I quit Delphi: --------------------------- Anwendungsfehler --------------------------- Exception EAssertionFailed in Modul GExpertsRS103.dll bei 00055131. Call DeactivateFontsInfo before calling this. (D:\source\_sourceforge\GExperts\externalsource\UniSynEdit\SynTextDrawer.pas, Zeile 475). --------------------------- OK --------------------------- I have been getting a more generic error ever since 10.2 but kind of got used to it. This now is more specific and I'll report it to the GExperts bug tracker as well.

Sorry about that, totally overlooked that report.

And what does that line look like?

That's a NASty bug. *SCNR*

The VS and the AutoCAD toolbars look self drawn, not OS drawn with some decoration glued on them. However, I don't see the Delphi issue on my 100% screen.

😱 I think we should better get back on track...

Maybe errors are the norm and what we consider to be correct is the true error.

I'd love to, but alas the Gods wont let me:

No, sorry.

Same in 10.3.2, possibly even in 10.3.1.

Sorry, but no. You very aptly described hotkeys. An example for a shortcut is Ctrl+C to cut a marked object. The corresponding Hotkey sequence could be Alt+E to enter the Edit Menu then C to copy. Or to use your screenshot: a possible hotkey sequence to close all files would be Alt+F, L. The shortcut is Shift+Ctrl+F12.

I think installation to the physical iDevice would have to be done via Testflight. Not sure if your physical iDevice can be connected to the virtual cloud Mac. @limelect How old exactly are we talking here? iOS 11 should be minimum, better 12.

Well you don't need the Mac physically. You can rent a Mac in a cloud for example here: https://www.macincloud.com/

You need a Mac. the simulator is part of XCode, which only runs on a Mac.

Guys, the german DelphiPraxis has a no-cheat-tool-policy. I'm pretty sure that applies to the english version here as well. So...sniffing is almost OK, modifying must be discussed elsewhere, please.

So I have this application, that runs smoothly on a standard PC, and does quite well on a tablet too. With one exception, the virtual keyboard causes quite the headache. Not only does Windows seem to have two different virtual keyboards, they behave quite differently too: First there is the keyboard that has to be actively opened by the user by clicking on the symbol in the tray area. This works fine, but has the disadvantage of "an additional click". (Image 1) Then there is a keyboard (image 2) that can be opened automatically when FMX.Types.VKAutoShowMode := TVKAutoShowMode.Always; is set. According to the fine manual this will cause the virtual keyboard to show even if there is a physical keyboard present. So as soon as the focus is set on an editable component like TEdit, this keyboard will popup and as soon as said component looses focus the keyboard will disappear. Now here's the tricky part: This keyboard looks different, and on some machines (HP tablets with an i5) takes ages (at least 30 seconds) to "pop up". On my VM that I'm running on a Mac with an i7, this happens instantly. Any user who knows iOS will consider option 1 to be "out of the question" so I use option 2, but for the life of me am not able to speed up the virtual keyboard popup process. This might just become a deal breaker, hence this post. TL;DR: Does anyone here have experience with virtual keyboards on Windows tablets, and knows how to open them up quickly on slower systems? Thanks, Sherlock

Great! Thank you, I'll give that a try.