Form initialisation bug.

  • Thread starter Thread starter Bob Clegg
  • Start date Start date
B

Bob Clegg

Hi,
I have a form that has a telephony control and its event handler.
If a msgbox is put into Public Sub New() after initialisecomponent
or it is put in any subroutine that is called in Sub New() after
initialisecomponent.
Then the eventhandler is shutout. ie It will not trigger on an incoming
call.
It appears that it is not totally safe after InitializeComponent().
Further evidence of this is while investigating the above I attempted to
invoke a delegate in the same spot.
This errored with 'cannot call invoke until windows handle has been created'
So just a warning to anyone who is interested.
It is an evil little bug as the last thing you would expect to be causing
trouble is a msgbox that executes OK within its context.
Whether it is specific to this component or not I haven't had time to
investigate.
regards
Bob
 
Hi Bob,

Is this problem only specific to the telephony control? Can you reprodue
the behavior with other controls? It would be great if you could show us a
sample that could reproduce the problem.

Thanks,

Felix Wu
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
 
-----Original Message-----
Hello,



Which telephony control do you use?
Click to expand...
Hi,
Parity Voicebox 5.2 talking to a dialogic board d/41epci
I tried generalising the problem with an interrupt raised
by a push button but this did not fail. It looks like it
is something esoteric with the Telephony component.
From my point of view it is not worth pursuing further, I
just thought I would make others aware.
Thanks to you and Felix for your efforts on this.
regards
Bob
 
Back
Top