I wouldn't call it a thunk, just a class that contains
the info needed to invoke the handler.
The main thing is that I also have code that was
affected by this and worked just fine in '07, but in
'08 with the exact same code, the event continues
to fire even after its removed.
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2008
Supporting AutoCAD 2000 through 2008
http://www.acadxtabs.com
"Owen Wengerd" wrote in message news:5587382@discussion.autodesk.com...
Tony:
Ok, I see what you're saying. I wonder though if the "reference to the
handler" isn't really a thunk which simply passes control to the actual
handler. If this were the case, the 'handler' from AutoCAD's perspective
would be the instance of the thunk. That is, different instances of the
thunk would appear to AutoCAD as different event handlers, and would
presumably result in the behavior that the OP is observing.
For the record, I'm pretty much clueless when it comes to .NET, so this is
all wild speculation on my part. 🙂
--
Owen Wengerd
President, ManuSoft ==> http://www.manusoft.com
VP Americas, CADLock, Inc. ==> http://www.cadlock.com
"Tony Tanzillo" wrote in message
news:5587182@discussion.autodesk.com...
"Owen Wengerd" wrote:
>> it looks like he is creating a new handler, then
>> trying to remove the new one while leaving the
>> old one in place. No?
Yes it appears that way because the names of the
types are confusing. The 'handler' is the method of
the class that is called to handle the event. The
object he creates via 'new ObjectEventHandler()', is
actually a reference to the handler (which is passed
as the parameter).
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2008
Supporting AutoCAD 2000 through 2008
http://www.acadxtabs.com