I am not the one who knows, but if such a thing exists (to modify standard behavior of objects without questions), it should be disabled by autodesk immediately.
Security alone is a problem, but also - it would create too mouch of a user confusion if objects start to act unfamiliar to them.
This.
Custom Objects, embedding data in NOD/XRecord is one thing, but to be capable of embedding executable code in a Drawing that someone _
not_ part of your internal, or contract-required user group (
parties that are aware of this custom functionality), should not be allowed, if it does.
Anyone could open a drawing, and be exposed to (
malicious?) .NET level APIs... Hackers would love something like this... And I thought it was bad enough with Acad.lsp virus/worms using ActiveX. :ugly: