Are there any downsides to adding OleInitialization calls to the main form of a project? eg:
initialization
OleInitialize(nil);
finalization
oleuninitialize;
(added to the main form of the application) appears to be a necessary addition to allow copying selected text from a TWebBrowser (on another form) to the clipboard. But I'm wondering if there are any unexpected consequences I might face in my program based on whether or not I add those lines? MSDN's description of OleInitialize indicates there are effects on the threading/concurrency model, but I don't totally understand the significance of those differences.
Here's an article from Embarcadero that confirms that you do need to call OleInitialize: http://edn.embarcadero.com/article/20468
There's no problem calling it the way you do. That is how it is meant to be done.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With