I am assuming it acts like partdoc.UserSelectionPostNotify, which only fires when an individual makes a selection with the mouse, vs Partdoc.NewSelectionNotify which fires whenever a selection is made in the apI or user interface.
To fix this, just call the event
Depending on if you want to fire the event before or after you save determines where you call the event.
To call the event just call the events function like
Eventhandler.FileSaveAs2 ( fill in the arguments here) if you are using the api, I wouldn't want solidworks to break into pause my application to notify me of something I know that im doing, like calling saveAs. You know your calling save as so just call the function that the event calls. This way if your application calls the event vs the user, you get the same outcome, which is what you are looking to get here I believe.
thx for the response. The original event i have to trigger is not in my code it is part of a 3d party module (Windchill/Solidworks Plugin) and so i have no idea how to fire this event because there is no object or code available. I found no method in the general API like fireEvent(SaveAsNotify).
I think that IModelDoc2::SaveAs4 would not trigger FileSaveAsNotify2 since that could call SetSaveAsFileName, overriding the filename you specified in SaveAs4.
Does it trigger FileSavePostNotify though? That would be more logical.