V
v.bodurski
The application I'm working on is:
using Visio 2003 ActiveX control embedded within .NET program (written
in C#).
Currently I'm using EnterScope to detect the occurence of the following
events:
visCmdUFEditCopy
visCmdUFEditCut
visCmdUFEditDuplicate
visCmdDragDuplicate
But the problem which hinders my usage of this method is that
EnterScope
event is raised when the operation has already been completed.
The reason for my need to intervene before the shape is
copied/duplicated/cut
is:
For all shapes (which are not 1D) I have a separate DataSet with some
info. That info is available to the user for editing, this info is
stored within the corresponding shape, as XML, so that the created
configuration
can be saved just as a .vsd file and later restored by the program.
So when a user makes a change to the DataSet I'm trying to determine
the events which
require that the DataSet to be written into the shape. My other option
is to
actually synchronize the DataSet to the shape's XML after each
modification
done by the user, but this is something I'd prefer to leave as a last
resort.
using Visio 2003 ActiveX control embedded within .NET program (written
in C#).
Currently I'm using EnterScope to detect the occurence of the following
events:
visCmdUFEditCopy
visCmdUFEditCut
visCmdUFEditDuplicate
visCmdDragDuplicate
But the problem which hinders my usage of this method is that
EnterScope
event is raised when the operation has already been completed.
The reason for my need to intervene before the shape is
copied/duplicated/cut
is:
For all shapes (which are not 1D) I have a separate DataSet with some
info. That info is available to the user for editing, this info is
stored within the corresponding shape, as XML, so that the created
configuration
can be saved just as a .vsd file and later restored by the program.
So when a user makes a change to the DataSet I'm trying to determine
the events which
require that the DataSet to be written into the shape. My other option
is to
actually synchronize the DataSet to the shape's XML after each
modification
done by the user, but this is something I'd prefer to leave as a last
resort.