The API docs state:
DAssemblyDocEvents_FileDropPostNotifyEventHandler
Post-notifies user applications when a part is dropped from WindowsExplorer into an assembly
DAssemblyDocEvents_FileDropNotifyEventHandler
Fired when a part is dropped from Windows Explorer into anassembly.
The obvious question is what is the difference between these twoevents? The former takes no arguments, the latter is passed thefilename of the dropped file. Other than that they seem to notifyyou of the same thing.
My testing seems to indicate that the 'FileDropPostNotify' isn'teven wired up internally in SolidWorks. The event doesn't get firedat all.
If anyone can shed some light on this dark mushroom infested cornerof the API, it would be appreciated.SolidworksApi macros
DAssemblyDocEvents_FileDropPostNotifyEventHandler
Post-notifies user applications when a part is dropped from WindowsExplorer into an assembly
DAssemblyDocEvents_FileDropNotifyEventHandler
Fired when a part is dropped from Windows Explorer into anassembly.
The obvious question is what is the difference between these twoevents? The former takes no arguments, the latter is passed thefilename of the dropped file. Other than that they seem to notifyyou of the same thing.
My testing seems to indicate that the 'FileDropPostNotify' isn'teven wired up internally in SolidWorks. The event doesn't get firedat all.
If anyone can shed some light on this dark mushroom infested cornerof the API, it would be appreciated.SolidworksApi macros
