Hi all,
I'm developing a c# excel addin and in order to make it work I have added a
new handler for the SheetChange event.
This handler modifies some global (addin scope) variables in order to
determine if some row/columns have been deleted and uses the UsedRange
attribute.
After that it become impossible to UNDO the modification.

Could anyone help finding out the reason and fixing it?

Thanks a lot for the help,

faffo1980

This is not surprising. I think it's actually designed this way. I have
seen some code somewhere that allows for undo when an event is fired, but I'm
not sure where to find it.
--
HTH,

Barb Reinhardt



"faffo1980" wrote:

Hi all,
I'm developing a c# excel addin and in order to make it work I have added a
new handler for the SheetChange event.
This handler modifies some global (addin scope) variables in order to
determine if some row/columns have been deleted and uses the UsedRange
attribute.
After that it become impossible to UNDO the modification.

Could anyone help finding out the reason and fixing it?

Thanks a lot for the help,

faffo1980

I believe it's done that way by design. I know I've seen something around
that will undo programmatically, but can't seem to find it now.
--
HTH,

Barb Reinhardt



"faffo1980" wrote:

Hi all,
I'm developing a c# excel addin and in order to make it work I have added a
new handler for the SheetChange event.
This handler modifies some global (addin scope) variables in order to
determine if some row/columns have been deleted and uses the UsedRange
attribute.
After that it become impossible to UNDO the modification.

Could anyone help finding out the reason and fixing it?

Thanks a lot for the help,

faffo1980

Hi faffo
After running any macro the undo feature is gone until you do some other
manual changes in the sheet (just as it is when you Save or Autosave runs.

Hope this helps
Regards, Brett

"faffo1980" wrote:

Hi all,
I'm developing a c# excel addin and in order to make it work I have added a
new handler for the SheetChange event.
This handler modifies some global (addin scope) variables in order to
determine if some row/columns have been deleted and uses the UsedRange
attribute.
After that it become impossible to UNDO the modification.

Could anyone help finding out the reason and fixing it?

Thanks a lot for the help,

faffo1980