.NET
Handling CommandWillStart event will not meet your need, as you have already found out, because no matter what you do in the event handler, it is just something you can do before the command starts, after your code runs, the command will still run.
To your need, you can handle DocumentCollection.DocumentLockModeChanged event and DocumentCollection.DocumentLockModeChangeVetoed event. That is, in the DocumentLockModeChanged event handler, if a certain condition is met, you can then veto the command, which will result in the DocumentLockModeChangeVetoed event being fired. Then in DocumentLockModeChangeVetoed event handler, you can start your own process/custom command.
Some psuedo code:
private static bool runAlternativeCmd=false;
public void Initialize()
{
DocumentCollection docs=Application.DocumentManager;
docs.DocumentLockModeChanged+=new DocumentLockModeChangedEventHandler(DocLockChanged
docs.DocumentLockModeChangeVetoed+=new DocumentLockModeChangeVetoedEventHandler(DocLockCh
}
void DocLockChanged(object sender, DocumentLockModeChangedEventArgs e)
{
if (e.GlobalCommandName.ToUpper()=="XXXXXXX")
{
//Test if the entity in the implied selectionset is the targeting block. If it is, veto the command
runAlternativeCmd=true;
}
else
{
runAlternativeCmd=false;
}
}
void DocLockChaneVetoed(object sender, DocumentLockChangeVetoedEventArgs e)
{
If (runAlternativeCmd)
{
Document doc=Application.DocumentManager/MdiDocument;
doc.SendStringToExcute("MyAttrEdit ",true, false, false);
}
}
[CoommandMethod["MyAttrEdit")]
public static void EditMyAttribute()
{
Do my own editing process
}
HTH
Well, carefully looking into the compiling error would reveal something obviously.
1. You added event handler to handle DocumentLockModeChanged event, but you remove a handler on DocumentActivated event, which is never been added in the first place.
2. The event handler docColDocAct() cannot be used to handle DocumentLockModeChanged event, because the handler's signature is wrong. Event handler for DocumentLockModeChanged requires the second argumnet of the handler to be type of DocumentLockModeChangedEventArgs, not DocumentCollectionEventArgs.
