Normally, we add a control to a .bas file and get the handle of a combobox for instance. Then we can handle the control like an object, for example with Control Add ComboBox, hDlg, id& ....
But what is when a DLL function wants to use the content of a Combo which is placed inside the code of the running EXE?
I never needed or tried it until now, it's just a thought in this moment.
So, when I have the handle of the combo inside the running exe. Can I use the combo with PB like it were implemented inside the DLL to avoid using the WinApi?, such like: COMBOBOX SELECT hDlg, id&, pos& - where hDlg could be the dialog handle in the EXE, id& the ID of the combo.
Please notice that - in my case - the DLL is one of many invoked by event or by function directly or indirectly via another DLL from the main EXE, but all of them are using the same mem space.
But what is when a DLL function wants to use the content of a Combo which is placed inside the code of the running EXE?
I never needed or tried it until now, it's just a thought in this moment.
So, when I have the handle of the combo inside the running exe. Can I use the combo with PB like it were implemented inside the DLL to avoid using the WinApi?, such like: COMBOBOX SELECT hDlg, id&, pos& - where hDlg could be the dialog handle in the EXE, id& the ID of the combo.
Please notice that - in my case - the DLL is one of many invoked by event or by function directly or indirectly via another DLL from the main EXE, but all of them are using the same mem space.
Comment