At this time I am not familiar with Speedikon (product and code) to be able to provide an indication of what is available. At a higher and more common level I can make 2 suggestions.
1. Try recording a MicroStation VBA macro to see if it can trap Speedikon's File Save dialog. Recording the macro has the potential of providing you with template code you may be able to use/reuse to resolve your file save concern. The recorded macro may provide you with stub code showing how to create event interests in MicroStation-based (MicroStation and other MDL in-process application) dialog box open events and taking action on those dialog boxes based on their title bar text. If Speedikon File Save functionality is implemented via an in-process MDL application this may help of the dialog text (and active command) is unique enough to react to.
2. Whether #1 is of help (and even if not), I agree with Jon's statement that you should consider placing an enhancement request with Speedikon's support group to provide a configuration option that allows users/administrators to override the current default behavior requiring users (in all cases) to manually save Speedikon objects having the option to override that behavior.
[quote user="Jon Summers"] A long-term solution would be to persuade Speedikon to follow MicroStation's idiom of saving all graphic elements automatically.[/quote]
HTH,
Bob