John van de Waeter

Yes, it looks somewhat in that direction, given the fact that another keyboard (GBoard) does not have the problem. Yes, I made something similar. Not using the events ,nor a timer, but polling the text from the editbox in the app's OnIdle event. Kinda dirty, but it works :)

Nope. Platform style doesn't fire the OnTyping event.

The problem is that the events OnTyping , OnValidating , OnChangeTracking, OnKeyUp, OnKeydown ALL are fired as many times as there are characters in the EditBox. That is, on my Galaxy 21, Android 15. I could work around it if I would know how many characters are in the EditBox, like length(editbox.text), but inside the eventhandler, that number gives me 0,1,2,3,4,.. NOT the actual length of the contents of the editbox. Is there a way to access the underlying editbox, in which on screen I can clearly see e.g. 6 characters, that gives me a "6"? In that case I could count the number of events and know which one is the last one and act upon it.

Yes, I know... thanks for thinking with me 🙂

Hmm... It's one of the most used android phones... anyway, I noticed on a friends' Galaxy/Android 13 the TEdit with the OnTyping event has issues as well... Time to figure out just another workaround...

So you told them to buy another phone?

I just did, and another keyboard like this GBoard seems to work okay... However, it would be strange to tell my users to install another keyboard...

Hi All, Just noticed. The OnTyping event is fired differently depending on the Android version. I have a TEdit that is used for incremental text searching. The user types, I use the OnTyping event to read the text from the TEdit and use this text to scan a table for keywords. Works okay on Windows, Mac, iOS and Android 12 (Samsung Galaxy Tablet). On all targets, the Ontyping event is fired once for every typed character. On my Galaxy S21, Android 15, however, the event is fired again and again for the length of the typed text. So if I type 'tha' I should have 3 events. Edit.text = 't', edit.text='th' edit.text='tha'. On my Galaxy S21, Android 15, I get 6 events: type the t: 1 event fired: edit.text ='t' type the h: 2 events fired: edit.text='t', immeditaely followed by edit.text='th' type the a: 3 events fired: edit.text='t', edit.text='th', edit.text='tha'. So as many events as the length of the typed text. This continues until the user types a space. In that case only one event is fired and inside this event, edit.text equals the contents of the Tedit. As expected. My dev: Delphi 12.3, Android 25.2.5 both 32 and 64 bit Unfortunately I don't have more Android devices to test... Is this a problem in Android 15? tia, John

Hi All, Delphi 12.2, iOS Using a TMemo for user input did NOT show the word suggestions on the virtual keyboard. (predictive suggestions says Apple). Using Controltype PLATFORM instead of STYLED for the TMemo solved the issue. Just in case you have complaints from users, like I had... :) John

After hours of comparing between the debug and the release version..... I found that somehow 3 files in the deployment table got unchecked. No idea how that happened, but it did. After checking those files again, everything worked as expected.

This error when deploying for Android64, Delphi 12.2.1. [PAClient Error] Error: E8712 Picked up JAVA_TOOL_OPTIONS: The is no system variabele like JAVA_TOOL_OPTION Strange thing is: building and deploying a debug-version works ok... Anyone have an idea?

Thanks Vinícius 🙂 BTW I noticed that the OnPaint event of the image is fired continuously as the image is scrolled in the visible part of the Listbox. I would have thought that if the size of the image is unaltered, the showing bitmap should not need to be repainted, only moved. But I'm not an expert on this....

I used WinZip to unzip the archive, which allowed me to skip files with bad filenames. I figured if those filenames are not allowed in Windows, these files are probably not used anyway. It worked. ps, Dave, if I have questions about Kastri, should I ask them here?

Lol.... I too had a hard fight to send those notifications to the v1-google fcm server.... I never realized that the converting part (apns->fcm) also required this new approach... Having apps online that suddenly don't receive pn's anymore forces one to be creative.... I'm now trying the Kastri-path.

Yep, lots of other code in this file. But it contains the original firebase.zip, which in turn has the same problem....