Hi
@Erel
Picking up from
this wish I further explain the possible usage and why it should have already be implemented...
A custom view is, most of the times, a mix of functionalities from several other views, like the some text input fields mixed up with buttons, or combo views...
In some more complex cases, a custom view is a set of inter connected views used to achieve a simpler result than it would if coded all views seperatly...
But, in some cases, visualy we are left a bit impaired by the lack of a filename type of designer property...
The base panel can hold & image, but when we create a CV with cascading views, sometimes 2 or more images are needed to achieve a coherent look through out the view.
Of course, You know all this, and although we have come a long way, sometimes I see "smaller" improvements being left behind so that the "bigger" ones are implemented...
I really think the next update should be about the "smaller" features that are long overdue, and would defenetly bring a more professional coherent vibe to the B4X Suite.