I tried it on one of my projects and it works as intented. There is no overlap with the hint text. However, here a solution in your case that was given not long ago by Erel:that hides the hint as soon as you start typing
B4X:
Sub B4XFloatTextField1_TextChanged (Old As String, New As String)
B4XFloatTextField1.mBase.GetView(1).Visible = New.Trim.Length = 0
End Sub
I tried it on one of my projects and it works as intented. There is no overlap with the hint text. However, here a solution in your case that was given not long ago by Erel:that hides the hint as soon as you start typing
I do not have that problem, unless you are overapping both B4XFloatText. If you suspect it is a bug as you claim, then Erel always comes to the rescue.
Your original image in post#1 was totally different from what you have now. Why did you change it and removed the 1st B4XFloatText. You initially were talking about the 2nd B4XFloatText drowning the 1st B4XFloatText.
Your original image in post#1 was totally different from what you have now. Why did you change it and removed the 1st B4XFloatText. You initially were talking about the 2nd B4XFloatText drowning the 1st B4XFloatText.
Because the 1. B4XFloatText has nothing to do with the error and is irrelevant, it is separated from the 2. B4XFloatText.
Next time I will make sure that only the affected view is visible.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.