So I know the map control has a problem with TFrames, so I've put a Map Control on a TForm. I dynamically create the TForm and reparent the Map into a TabItem of a TabControl on my Frame. This works the first time.
But if I destroy the Frame and thus, the TForm and the MapControl and instantiate the Frame (and form and Map) again, when ever I try to view the tabitem which contains the Map it is either not visible, or comes up with the default design time long/lat coordinates and it doesn't respond to code.
Are you aware of any issue with recreating the map control and not having it work the second time?
I can probably create a project which demonstrates this if I need to.
Would you first give man idea of what is supposed to work in the Deinitialize/Initialize sequence.
My issue too is that I have one map I'm sharing between frames. Whenever one of the frames is active it reparents the map. I didn't want to have to have 2 instances of the map in my app. I may try that. But I really need to know what is supposed to work.
We have investigated frames, and applied improvements for frame reparenting in the past versions, but some conditions haven't been checked so it's important to know what exactly you are doing to reparent. The browser is attached to a window handle, which is the parent control, so when reparenting it should attach to the new handle, yet when reparenting from a TFrame to a new TForm is something new. It would be good to know the flow so we can investigate a solution.