The disclaimer's non-GPL compatibility is what I'm concerned about. Without the disclaimer, TransX would still have to be GPL'ed (GPL compatibility means that a work under a given license can be relicensed under the GPL when it incorporates GPL code without causing legal issues, see
http://www.gnu.org/licenses/gpl-faq.html#WhatDoesCompatMean), but it could be GPL'ed without trouble.
Key point here. Thanks.
However I'm not so sure if it can be GPLed without problems, as all of the previous authors and contributors would have to agree on it. As GPL means that you can sell the product for even beyond the costs of distribution, I doubt that Duncan would agree, as he's put the disclaimer there, which basically prohibits the whole freedom which GPL gives except code sharing, ie. monetizing and reuse outside Orbiter.
Why I prefer GPL over LGPL for my libraries:
It's mostly because I'd like to see more code sharing from the community, friendly or not. And that's because it helps everybody in the long run. TransX, and BTC are perfect examples how projects can grow in the right direction, thanks to their openness.
I have nothing against using my GPL/BSD-licensed stuff outside Orbiter and selling it, as long as the code is shared and copyrights are preserved.
To sum up:
I think that in this case, I will cease and re-release the SDK under LGPL, as I don't want to spend too much time on PR, trying to convince other authors how great it would be if they agreed on GPLing their old code. My hobby is programming, not lobbying.
Thanks again for bringing all these points.
---------- Post added at 08:34 AM ---------- Previous post was at 08:24 AM ----------
Blixel:
Thanks for experimenting with this bug. Let me guess: this happens on DX9 client but on inline client not? If so, then I had the same problem. It was hanging on DX9, then I launched the same scenario on DX7, which worked. Then I switched to DX9 and the same scenario worked again. Very weird.
The good thing is that since your PC has the same behavior as mine, then if I fix it at my end, it will work at yours. I think that it has to do with static initialization of the ModuleMessaging library. If this is the case, then I'll simply initialize it just like HUDDrawer, which so far exposed no such problems, but this will require enabling the MM in Modules tab, which I tried to avoid.
I'll get back to you during the coming weekend, when I find some time.