V
v.bodurski
The test case is quite simple, Visio 2003 Drawing control is embedded
within C#
program, when a shape is dropped on the drawing surface through the
ShapeAdded
event handler I add a registration for FormulaChanged event on the new
shape.
Then I start moving the shape arround (thus generating formula changed
events)
and after some time the debug messages I've placed within the
FormulChanged
event handler stop printing, then I place a breakpoint on the handler
to see if
its called and the breakpoint does not get activated. This test case
was reproduced several times and its typically around 3500 calls of the
event handler
that the messages stop comming out. These tests were done to check
performance/
stability of this mechanism to handle the case where a connector (1D
shape) is
disconnected from a 2D shape (i.e. through checking
BeginX/BeginY/EndX/EndY
cells' values when they change and so on), is this behavior of this
message
known issue?
within C#
program, when a shape is dropped on the drawing surface through the
ShapeAdded
event handler I add a registration for FormulaChanged event on the new
shape.
Then I start moving the shape arround (thus generating formula changed
events)
and after some time the debug messages I've placed within the
FormulChanged
event handler stop printing, then I place a breakpoint on the handler
to see if
its called and the breakpoint does not get activated. This test case
was reproduced several times and its typically around 3500 calls of the
event handler
that the messages stop comming out. These tests were done to check
performance/
stability of this mechanism to handle the case where a connector (1D
shape) is
disconnected from a 2D shape (i.e. through checking
BeginX/BeginY/EndX/EndY
cells' values when they change and so on), is this behavior of this
message
known issue?