Double Click "Jump to source" about vbccr

[Kr00l]

Yes, your understanding is correct.

An additional condition with "And CommandButtonTopDesignMode = False" might fix it. So in IDE design mode it would get WM_LBUTTONDBLCLK (unchanged) and for IDE run mode or exe it would replace to WM_LBUTTONDOWN.

[NBechtloff]

I tried to analyze the problem further. It seems the relevant message for the designers "Jump to source" is WM_MOUSEACTIVATE. There already is a check for CommandButtonTopDesignMode = False in the WindowProcControl.
BUT for reasons beyond my comprehension the GetTopUserControl(Me).Ambient.UserMode call in UserControl_ReadProperties reports the wrong value (i.e. false). If i make the same assignment (CommandButtonTopDesignMode = Not GetTopUserControl(Me).Ambient.UserMode) in UserControl_Show again everything works just fine!
Now I dont know if that has any consequences for the compiled application. I feel a little bit unwary. Especially because I do not understand completely why this is working for the TextBoxW.
I have the feeling that Ambient.UserMode is fundamentally flawed somehow.

[Kr00l]

GetTopUserControl(Me).Ambient.UserMode call in UserControl_ReadProperties can only be flawed when your outer (host) UserControl do something stupid within UserControl_Initialize, because then the inner (child) UserControls may fire ReadProperties when in fact it's too early. So are you interacting with the childs within the host's UserControl_Initialize?

[NBechtloff]

You are correct. I am stupid.
Of course I interact with the child in the host's UserControl_Initialize.
Thanks a lot for your help, I would have never found that.