I have posted on Jose Roca's forums asking this question.
The Windows Common Controls used in DDT don't expose the correct interfaces to allow a script host to sink events and respond to property changes. Same goes with MFC applications, which use the same DDT technology.
I have read that if you write a COM wrapper for the control, you can use that to be the middle man between the actual control and the host.
My problem is, I need to convert some VB6 code to work with PowerBasic. I need to use standards, so I won't have any ActiveX controls to distribute.
I need to get the iActiveScript interfaces working in PowerBasic, and then I need to figure out a way that the script executed can change visual properties of controls on the window.
The Windows Common Controls used in DDT don't expose the correct interfaces to allow a script host to sink events and respond to property changes. Same goes with MFC applications, which use the same DDT technology.
I have read that if you write a COM wrapper for the control, you can use that to be the middle man between the actual control and the host.
My problem is, I need to convert some VB6 code to work with PowerBasic. I need to use standards, so I won't have any ActiveX controls to distribute.
I need to get the iActiveScript interfaces working in PowerBasic, and then I need to figure out a way that the script executed can change visual properties of controls on the window.
Comment