As to catch return of oActiveX:Do

[vilian]

Antonio,

I verified the topic that you he suggested, I identified some functions for the treatment of messages, but I did not understand as they can help me !

[Antonio Linares]

Vilian,

Do you always get 1242696 no matter what key you press ?

[vilian]

Antonio,

any one.

[Antonio Linares]

Do you get that value without pressing a key ?

What documentation about such event does your activex provides ?

[vilian]

Antonio,

On these specific events the following text only exists:

Code: Select all

Standard events: 

The control supports these standard events: Click, Double click, Got Focus, and Lost Focus, KeyDown, KeyPress, KeyUp. The KeyDown, KeyPress and KeyUp event take one integer parameter which passes the value of the key code.

The support technician of them returned me the following one:

Code: Select all

 KeyPress event is not an internal TE message (it is only an ActiveX message), it would not be routed to the callback message.  The KeyPress event takes only one parameter which is the keyvalue for the keystroke.  So nKey1 should be the numeric key values.

I tested this event in Visual Basic and it seems to work properly. However, VB shows only one parameter, which is nKey.

[Antonio Linares]

Vilian,

You may need to modify these methods in Class TActiveX:

METHOD KeyChar() VIRTUAL
METHOD KeyDown() VIRTUAL

[vilian]

Antonio,

I made the modification, but nothing he modified in the result.

[Antonio Linares]

Vilian,

I don't know, don't have more ideas

Thats the problem with ActiveX (same as old Microsoft VBXs). We don't have their source code and we don't have full control over them

[vilian]

Antonio,

If you to install the control in its computer help to decide the problem?

[vilian]

Antonio,

I asked to the support of them - Exists some another way to implement what necessary?

The support technician of them returned me the following one:

Code: Select all

    If your application lets you define callback function, then you can use the TerRegisterMsgCallback function to register your callback function.  TE would then route the internal TE messages to the callback function.  The callback function should have the following prototypes:

LRESULT WINAPI _export TerCallback(HWND hWnd, UINT message, WPARAM wParam, LPARAM lParam)

   Also, since KeyPress event is not an internal TE message (it is only an ActiveX message), it would not be routed to the callback message.  You can instead use the PreProcess event for this purpose.

Aid?

[Antonio Linares]

Vilian,

> You can instead use the PreProcess event for this purpose.

Whats that ? Tell him to explain you whats the PreProcess event and a sample of its use