LucaMs Expert Licensed User Longtime User Aug 27, 2026 #1 Erel, please, tell me (quando, quando, quando ) why... The B4XFloatTextField must not have the Visible property. I am forced to write: B4X: Copy B4XFloatTextField1.mBase.Visible =False and the AI I use doesn't know this "weirdness", so it logically generates: B4X: Copy B4XFloatTextField1.Visible =False You know better than me that you would only need to add a few lines: B4X: Copy Public Sub setVisible(Visible As Boolean) mBase.Visible = Visible End Sub Public Sub getVisible As Boolean Return mBase.Visible End Sub so you have a valid reason not to, I suppose.
Erel, please, tell me (quando, quando, quando ) why... The B4XFloatTextField must not have the Visible property. I am forced to write: B4X: Copy B4XFloatTextField1.mBase.Visible =False and the AI I use doesn't know this "weirdness", so it logically generates: B4X: Copy B4XFloatTextField1.Visible =False You know better than me that you would only need to add a few lines: B4X: Copy Public Sub setVisible(Visible As Boolean) mBase.Visible = Visible End Sub Public Sub getVisible As Boolean Return mBase.Visible End Sub so you have a valid reason not to, I suppose.
Erel B4X founder Staff member Licensed User Longtime User Aug 27, 2026 #2 LucaMs said: so you have a valid reason not to, I suppose. Click to expand... It is a standard convention to expose mBase and let developers change whatever they like with mBase. The other way is to duplicate all methods for all custom views and it is a bit annoying to do... Upvote 0
LucaMs said: so you have a valid reason not to, I suppose. Click to expand... It is a standard convention to expose mBase and let developers change whatever they like with mBase. The other way is to duplicate all methods for all custom views and it is a bit annoying to do...
LucaMs Expert Licensed User Longtime User Aug 27, 2026 #3 Erel said: The other way is to duplicate all methods for all custom views and it is a bit annoying to do... Click to expand... It's rare that work isn't boring If you trust me, I can do it for you, but the language <should or must?> be "coherent." Upvote 0
Erel said: The other way is to duplicate all methods for all custom views and it is a bit annoying to do... Click to expand... It's rare that work isn't boring If you trust me, I can do it for you, but the language <should or must?> be "coherent."
Erel B4X founder Staff member Licensed User Longtime User Aug 27, 2026 #4 LucaMs said: If you trust me, I can do it for you, but the language <should or must?> be "coherent." Click to expand... Duplicating code is bad. Maybe "class default properties" feature should be added. Upvote 0
LucaMs said: If you trust me, I can do it for you, but the language <should or must?> be "coherent." Click to expand... Duplicating code is bad. Maybe "class default properties" feature should be added.
LucaMs Expert Licensed User Longtime User Aug 27, 2026 #5 Erel said: Duplicating code is bad. Maybe "class default properties" feature should be added. Click to expand... I'm "studying" an "extension code module" (similar to your extension classes; or my truly wonderful lmB4XTableExt ). Upvote 0
Erel said: Duplicating code is bad. Maybe "class default properties" feature should be added. Click to expand... I'm "studying" an "extension code module" (similar to your extension classes; or my truly wonderful lmB4XTableExt ).
LucaMs Expert Licensed User Longtime User Aug 27, 2026 #6 LucaMs said: I'm "studying" an "extension code module" (similar to your extension classes; or my truly wonderful lmB4XTableExt ). Click to expand... It's absolutely not worth it. It's better for someone, like Erel, to add all the missing properties Upvote 0
LucaMs said: I'm "studying" an "extension code module" (similar to your extension classes; or my truly wonderful lmB4XTableExt ). Click to expand... It's absolutely not worth it. It's better for someone, like Erel, to add all the missing properties