Testing Companion or APK? I'm just going to try it here on Android 11.
Companion, but did build the APK and tested on my phone with the AfterPicking version.
Even thought of setting up a global boolean, but the trouble is that there is no event for no Activity response.
Yep, looks like the LostFocus event fails in this release. AfterPicking works, but we have already established it is not the event we need.
A work around would possibly be using the Activity Starter, but let's see if MIT are already aware of the bug tomorrow.
OK...not sure I'd call it a bug, but perhaps a feature request?
Apparently the programmers made the assumption that the user WILL select an item from a list, and didn't account for the user simply hitting the back button.
In this case, the user looks for the contact, doesn't find it in the list, so has to add a new one.
It's simpler to use the contact list as the add/modify/delete feature so you don't have to bloat your app with that code yourself. Same for a phone number or email address.
Thanks for giving it a shot...you're right, let's see what MIT comes up with.
probably has never worked like for buttons. However, there might be an extension that gives focus to components, I seem to remember Ken doing something. Just had a look, yes he did, but it looks like it was only for buttons....
If the app is only for you, you could workaround by creating a dummy contact,. e.g. A. Aardvark
, which you could select when not wanting to pick one of your actual contacts. If this is returned in the AfterPicking event, you can then Do Something Else
Agreed that that's a possible kludge workaround, but I tend to not like kludges because they tend to bite you down the road when you're trying to do something else.
@TIMAI2 Marked yours as the solution.
For my implementation, I created a user #ZZZ and starred it so that it would conveniently appear at the top of the contact list and is easy to test for.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.