AX Quirks
Brought to you by:
juradoz
Menu
▾
▴
#1 AX Quirks
Using the CSTADelivered event trigger I have noticed that feeding back the event data to the form that has the AX CtConector component embedded in it doesn't seem to work as expected. For example if I try to read the calling device string I can present it in a separate MessageBox. But if I take that same calling device string and update it in a TextBox control on the form that has the AX CtConector component the CSTADelivered event handler method is totally bypassed. Any statements in the method after updating the TextBox component are ignored. I can perform other actions such as changing the color of a form button, assigning variables based on the calling device string and whatnot. I just can't perform something like setting a TextBox.Text value to the calling device string.
Other event triggers don't seem to be working as expected either. For example, I want to take an outgoing call and update control on the form that contains the AX CtConector component. If I try to use the CSTANetworkReached or CSTAMakeCallConf event trigger these aren't being fired. I have tried placing breakpoints in my code to stop things when these event handlers are being accessed. But nothing happens. Checking my T-Server log files I see the events being passed back to the telephony services client, however. I have an active monitor on the device since I can check other events like the CSTADelivered event described above.
Logged In: YES
user_id=812727
Originator: YES
I am referencing the AX CtConector control in Visual Studio 2005 (C#) by the way...
Logged In: YES
user_id=812727
Originator: YES
The scenario above was referencing the ActiveX component in Visual Studio 2005. When I tried to use the component in Dolphin Smalltalk X6 I also found that the events weren't being captured consistently. I could invoke methods and check properties, however. But when I tested out even simple events like OnClick() they weren't being passed out to my development environment.