So... I have a number of questions on the subject of the OD SDK.
First, let me say I have had fun using the OD SDK, and have had no real trouble (aside from the data typing issue mentioned below) with it for years now!
Currently, I am using the "ObjectDock Docklet SDK v1.0" available from the link http://storage.stardock.com/files/ObjectDock_Docklet_SDK_v1.0.zip
Note that I consider it to have a bug in the definition of the final function in the DockletSDK.cpp file [WritePrivateProfileInt(...)] - the problem has to do with the inability to compile with the "wide char" aka "UNICODE" character set option, and the internal hard-coded dependence on the "itoa(...)" function - which expects and returns a pointer to a narrow char.
In any case, the fix that allows working with either char type is trivial, and I will make it available to anyone that wants it - but please read the bulk of my post before asking for it.
I am about to release an open source "docklet" that is based on this version of the OD SDK - but note that I have only used my docklet with a "one dock to rule them all" product that is no longer being developed... I expect it to work with OD itself, but that depends on things like "are OD SDK v1" docklets compatible with OD 2? Is OD 1 still a product, or has it been replaced with OD 2.x? Does the answer to either of these questions depend on "Win 10 -ness" or "64-bit-ness"? Note that while my docklet is a 32-bit DLL, I have been using it with 64-bit versions of Windows for years, including 7, 8.x, and 10.
Other issues include "when I release my open source project, may I include the OD SDK v1.0 zip file (with my above-mentioned fix)?", or would Stardock prefer/insist that I only provide the above link to the SDK, and then tell people how to fix the problem with wide chars, since my project uses them? I might mention that the downloaded SDK has no copyright or licensing information, which is part of why I am making this post... perhaps the idea was to place the SDK into the public domain, or instead to rely on some sort of "implied copyright"? Whatever the case, some explicit statement would probably be good.
Thanks for taking the time and expending the effort to create "the standard" in Windows "dock technology", with its quite usable API and functionality.