Yes I think you are right @iCFO. I think the current way it works is sufficient. I have sometimes included in the component description that it needs to be executed if the dialog isn’t displaying properly, and just occasionally even include something to that effect in one of the field labels on the component itself, because otherwise a casual user thinks something is broken, but apart from that I don’t think it causes too many problems.
@Meline_dng , I’m glad to hear that you can work with the way the components work. Thanks for the feedback!
Incidentally, I had to modify my demo component, as I hadn’t realised that on sharing the component it does not take data files with it, (plus I had actually coded it incorrectly even if it did, lol !) so I’ve had to replace the CSV Reader with a Table Creator. I don’t really imagine anybody will be using the International Dialling Code Picker but I have corrected it so that at least it now works in case anybody wants to experiment with the “dynamic” component.
This specific issue is mentioned here:
This is now going slightly off-topic although a continuation of my earlier post, but anyway anybody wondering how I managed to get a CSV file to work inside the component will realise that actually I didn’t… and I’m all ears if something has changed and there is now a way of sharing data files inside a “shared” component. (Always something new to learn! 
)