menuet is kinda copying synergy advance

I didn't know about the app, but if it is copying my products then that's really nothing new. There are about 20 Synergy clones out there, as far as I know.

Although you only hint at it, Krypton, I presume you mean that the clones exist because the features are too slow to come to Synergy.

Hate to be cynical, but I don't agree. Having started this back in November 2002, I watched clone after clone mindlessly copy features as soon as I added them into Synergy. This wasn't a case of other developers "innovating" to fill a gap; it was straightforward copying. And worse still, it wasn't free software advocates thinking "this sort of functionality should be available in a program licensed under the GPL!"; it was shareware developers seeking to make a buck off the ideas of others!

Nevertheless, point taken. I do agree that the is build up of requested features that needs to be addressed. I just don't agree that the speed with which I implement features has anything to do with the number of clones.

For what it's worth for the last month or so I've been devoting a good 8 to 10 hours a day to Synergy Advance exclusively. It's low-level stuff, but it will pay off in the end because I'm laying a good foundation.

Today, for example:

- wrote a new class WOArgumentArray, for processing arguments, along with a suite of unit tests

- spent a fair bit of time trying to improve my stack trace generation but unfortunately turned out to be a dead end so trying another tack

- renamed WOKernelEventQueue to WOKernelQueue and moved it from WOBase into WODebug so that it can be used by the Wincent Crash Reporter

- other refactoring such as moving methods from my NSArray category in WOBase to WODebug so that it can be used in the debug framework

And during this last month:

- wrote the WOEnumerate family of macros to speed up enumeration and make code easier to write, read and maintain

- WOMemoryBarrier family of macros for better thread safety

- huge amounts of work on WOTest and hundreds of new unit tests; I am extremely pleased with the results already as this has lead to numerous bugs being caught and fixed already; I've been using WOTest "in house" for some time now but with the recent work I now feel it's "1.0-ready" and would be happy enough with the code to release it once I'd fleshed out the tests a bit more

- malloc wrappers for simulating out-of-memory errors during testing

- improvements to build process to reduce unnecessary building of dependencies (which means a faster turnaround time and more builds per day) as well as more pervasive embedding of build information in executables

- writing more documentation for Synergy Advance

- and believe it or not, miscellaneous bits and pieces in the Synergy Advance code base itself (ie. not the foundation)

I haven't been very active on the forums but if you keep an eye on the news page, the knowledge base, and my personal weblog you do get bits an pieces of news about this kind of progress. I've preferred to get as much work done as possible rather than flooding the site with "news-bites", but occasionally I've made weblog posts when I've needed to clear my head.

Don't worry, zerock. I don't let things get me down because I enjoy what I do (programming) even when there's negative feedback.