Big Muscle

Yes yes, I am liar and I use PPK's code against license. The only thing I am interested in is which code it is. It is following one according PPK. Although such stuff hasn't been made by him and PPK not only violates license but also violates copyright by appropriating it. Every one can check what the true is - PPK speech or my comment.

OK. I asked Free Software Foundation about this. I described all places (and attached all files) where something about license is said. And I got following response, so we both are partially right So only Jacek Sieka can decide. However, I think he had never had feeling about any "GPLv2 or later" and he only copied the license text from GNU/GPL site. My words could be confirmed by the fact that his manually written sentence is without any "or later" and also the fact that he refused to change DC++ license to GPLv3. On the other side, if you say that source code license has higher priority then you wouldn't be able to compile DC++ with OpenSSL or WTL (because this is not allowed in source code). You can select only one license and not the one what suits you. And since Jacek Sieka told me that license is "GPLv2 with the notable exception that you may compile and link it with OpenSSL and WTL.", you can't apply "or later" to that.

Where did you take "or later"? DC++ license file says: It is true that each file contains: but this text doesn't specify the license version. It is only pure copy of statement from FSF. Important thing is "or (AT YOUR OPTION) any later version", but, according to license.txt, this option hasn't been selected. to theme: how does default KDE theme look like? wxWidgets use native theme drawing - it looks normal on all Windows version. So I am interested how the app theme is different from KDE theme.

1) It looks like that EiskaltDC++ is DC++ mod. Since it is licensed under GPLv3, it violates DC++ license. 2) I have seen wxWidgets app, I already made some. And if someone says that it looks ugly, it is because his OS theme looks ugly. My app looks like any other app http://img819.imageshack.us/f/screenshotck.png/

I saw WTL->wxWidgets port guide somewhere but I'm not able to find it now. I don't know how QT code looks, but wxWidgets are very similar to WTL, so it should be much easier.

Ah, you're right. I forgot about it, because I have already fixed it in my local code. That code doesn't have to be there for Linux, because it's fix for Windows bug.

Neither DHT norr webserver code are Win32 specific and I don't see any reason why they should be. Both are platform independent.

And not only this. One version of greylink I have tried contained some trojan (file was downloaded from greylink website), so users who use this client are really silly.

Could you tell us some more information? - when this crashed? - what were you downloading in the last time? - how many files did you have in queue? I'm hunting for this bug for a very long time. I have probably fixed it but I want to be maximally sure. I guess it crashed some time after some "finished" files had been removed from queue.

Colors priority is: 1. Favorite user 2. User with reserved slot 3. User in ignore list 4. User with fireball 5. User with fileserver 6. OP 7. Passive user 8. Normal color When you are OP, then following has higher priority: - Bad client - Bad filelist - Full checked - Client checked - Filelist checked This priority is there since the version where these colors was introduced.

I recommend wxWidgets. It's good, easy and very similar to WTL so it shouldn't be hard to rewrite current code. However, I don't see any benefit in creating special Linux version when current one works fine under Wine. At least, I would do some investigation how many users really need it. I guess it's not more then 10 and it would be only lost of time unless it's the only activity you are working on and you are paid for it. Are there any big differences when running native application or Win32 application in Wine?

I guess you use Alcohol software which has bug in its own shell extension.

Which address do you use to connect to the hub? I doubt you will be able to connect from external network to some element in any local network via its local address.

I don't understand the question, because the icons show what they are intended to show.

Please, could you try this StrongDC++ test build whether it fixes your problems? Thank you. http://www.sendspace.com/file/y01sn9

Settings to something higher than 2^32 causes overflow and will set limit to negative value. Thank you for the bug report.

Read again what I wrote. --- SetWindowTheme is supported since XP, probably Explorer theme is (although it doesn't anything important), but listview/treeview selection is defined in AeroStyle.xml which is part of Windows SDK and is not support on XP. If you still say it's not supported then you could explain why it's not on my image. You copied here some StrongDC++ code but you probably don't know how it really works (but copying of unknown code is typical for you).

If you want to tell us something then firstly read what we are talking about. Nobody is talking about explorer theme as a whole piece. We are talking only about selected item areas which are NOT available on XP as you claim - How you can fix something which is not broken and works as intended? And few applications? Probably yes, if you are talking about applications which you use.

Switching to different client is not an option, because as I said every application will use it soon or later. Also, "white" is not the only option - there is a lot of other colors. I use light blue.

Connection timeout is often caused by incorrectly set TCP and TLS ports.

Previous versions did not adapted to Aero look. Every application will adapt it soon or later. To match your color scheme with Aero, just go to settings > color and change colors to something which will match.

It's new feature of Aero listviews. Aero is very primitive graphic theme and is not prepared for color change and doesn't allow color change of each item. So possible solutions are: a) use color theme which match Aero or disable Aero.

Nobody needs "Update IP on startup" option if they follow already mentioned steps. How many times does it need to be said?

DHT can't work on all hubs, because it has nothing to do with the hubs. It's like you say "Hub A doesn't work in all hubs" (a little bit illogical claim). What DHT does is taking your external IP from the network every hour and putting it into global IP settings in your client. I'm sorry, but more solutions to missing "IP update checkbox" have already been given and nobody is able to respect it and still only "I want this option back". I feel I am among dumbs.

I think that you should disable queue autoexpanding instead of waiting for fixing non-existing bug ;-)