Hi,
just tested latest beta, I confirm the disappearing text issue is fixed.
This means I no longer have no major blocks for my app to be accepted.
THANK YOU (1)!
At this point my last issue is the crash that occurs when trying to edit text fields inline. As I said, presently I'm working around the issue by avoiding inline editing (I trigger AlertDialogs to edit fields), but I would rather do the editing inline, if it is possible (2).
Regards,
Michele
(1) You will soon get a more tangible thank you, as we should now no longer have blocking issues that prevent us from purchasing the library.
Quick question: I assume that if I purchase the library now, the licence will work with the current 3.0 betas, correct? Also, when do you think final version 3.0 will be released?
(2) In my experience, tapping on a text field which already contains a value will crash the application.
You already dismissed this report as 'I cannot reproduce it', but I have more information for you.
I discovered it happens under a particular case.
As you probably know, EditText behaviour can be different on different devices, or different screen orientations on the same device, depending on screen height:
1) if enough space is present, keyboard will appear and editing will be performed inline within the EditText
2) if not enough space is present, a full screen editing widget will appear (with a done button on the right) and editing will take place there
This crash only happens in scenario 1.
To see the full description of this issue (including stack traces), please visit page 7 of this forum thread.
