Jump to content

Sherlock

Moderators
  • Content Count

    1198
  • Joined

  • Last visited

  • Days Won

    24

Posts posted by Sherlock


  1. 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

    Bildschirmfoto 2019-12-06 um 14.44.53.png

    Bildschirmfoto 2019-12-06 um 14.45.55.png


  2. 12 minutes ago, Anders Melander said:

    It's not silly; It's for backward compatibility.

    Which, to be honest, is silly in itself. Backward compatibility is just a means to keep the living dead creeping around longer. I kind of love Apple for their policy of cutting off old stuff when their modern replacement has proven itself (last seen with macOS 10.15 and the 32Bit cut-off). It keeps the system clean, and prevents legacy software from doing stuff in a way that used to be okay but just isn't anymore. Please remember the Gate A20 situation that lasted from the introduction of the 80286 well into the Pentium era.


  3. Every Tom, Dick and Harry can up a small "Hello World" like project in any new language to GitHub, just to test it. So whenever a groovy new language is out, people with nothing else to do will do just that, making said new language "popular".

    What bugs me most is this "big company X invented this awesome and totally new language for their project Y because they couldn't have done it without it" meme. Which is just silly. First of all that new language will be just another dialect of some existing language, and secondly in what hell is that a reasonable approach to getting things done kissed and dry?


  4. So...macOS 10.15 has been released, and with it the incapability of running 32Bit applications. Using this tool to https://www.stclairsoft.com/Go64/ check wether or not I have any crucial 32Bit applications before making the dive, I found out, that the PAServer 20.0 (11.2.13.2) is at least in part 32Bit - which gives me a minor rash. What is the verdict on this? Should I stall Catalina installation, or is it OK to go ahead?

    Bildschirmfoto 2019-10-08 um 09.20.18.png


  5. Judging from the provided link alone a webhook is a server running on the client side. The client, when initiating a connection to a "real" server will provide this address to said server. This means, the server will need a client socket itself, and has to be able to connect to that mini server on the client side. It is a nifty concept to reduce open connections on the server side. Also the clients need not ask if a time consuming task is done, they will be notified via web hook. This concept will be rendered useless by firewalls, proxies and other sane security measures. Possibly only something for a LAN application. But in that case, the server might just dump the result of aforementioned lengthy operation into a samba share and the client could poll that every so often. No webhook needed. Unless the result is not dumpable...which I highly doubt.

×