Btw why make an x64 version of Circle Dock, except for "because we can"? Doesn't strike me as an app that would benefit from it.
The most I can say is that a 64 bit version helps over come issues that have been discovered in the Windows 7 OS.
If I run the 32 bit Circle Dock from teh Program Files (x86), I run into a lot of issues where some settings and mouse controls do not operate reliably.
At this time: I will say that the 64 bit has corrected this.
I am unsure of all teh nuances that MS included into windows 7 64, but it seems to be more 64bit dependent. That being teh case, my personal experience to date with the CD 64 bit has been stable.
That being said:
I also have CD 32bit installed into an alternative folder...for the most part it works like a champ, but loses mouse communication.
Since this does not seem to widely affect XP or Vista....I am left with the conclusion that it is something that S changed to direct applications towards the 64bit future, or it may be something as simple as tighter UAC controls in Windows 7, or any number of things that I am unaware of.
Ultimately this is not the way we wished to go, but with out a ground up re-write of the entire code under a new language, we do not see an alternative. Understand this is going to bite us in teh rear for making CD compatible with the current Docklet set as all docklets are currently 32 bit, and will not be compatible with CD 64bit.
So we are stuck in an interesting dilemma.
Ultimately the removal of SS2 as being integrated is not a bad thing....The capability will be available, but will be listed as an addon.
As such I am making a tut to explain the what, why's and how to get it back, and the apparent limitations
But for stability, getting back on track, was to accommodate the 64bit environment. CD 64bit is faster and more reliable on my windows 7 64 than the CD 32bit.
As I mentioned, we are not thrilled with it, but at the moment it is what we got.
I am praying that I have spoken well, and not missed anything on this, but I would let Markham be the judge in all this, and comment further if needed.
Eóin hit it right on the nose with the ini file, the problem being faced is that SS2 is integrate, but we are not utilizing a source code, so we can not redirect the ini to an AppData file to handle the R/W that SS2 requires.