Our most concerned details in ATL (1)

xiaoxiao2021-03-06  102

Our most concerned details in ATL (1)

1. No "Running is not visible" when creating a control, what do I want to join this feature?

Find in the engineering catalog, ***. RGS, open with Notepad, find:

'MiscStatus' = s '0'

{

'1' = s '131473'

}

change into:

'MiscStatus' = s '0'

{

'1' = s '132497'

}

Reconstruct it to have an invisible feature when running

2. If you create a control, you didn't select "Window Only". I found no window handle when using it. What should I do?

Open the control class constructor, join: m_bwindowonly = true; you can have a handle

3. What should I do if I set an incoming parameter in the connection point?

When the parameter is set to [OUT], open the flival_xxx function generated by the wizard.

Will see similar code:

For example, fli_xxx (long * val):

PVARS [0] = VAL;

Compiling will have a warning, you need to modify the following:

PVARS [0] .vt = vt_i8 | vt_byref;

PVARS [0] .plval = val;

The party can successfully pass the parameters, where vt_byref indicates the transmission reference method.

转载请注明原文地址:https://www.9cbs.com/read-104190.html

New Post(0)