Crise

It's not possible at present... well not without recompiling, there is something to fix around that (nothing too major) but none has ever fixed it... so homemade icons are used for folders instead.

You have a point I guess Well I guess the biggest difference is that you don't need wine installed... some users prefer not to use wine because in theory it can make your system open to windows viruses etc. (I have no idea how true this statement is, but it's what I have heard/read). Then there are just simply things that refuse to work well under wine, but still with Wine there is an extra layer to give birth to more bugs. Well in the case of DC I think it's also because there aren't many up to date native options to choose from for linux... and linuxdcpp keeps very close to vanilla DC++ in terms of features. I hope someone who has used linux and/or wine, more than I have, can provide some better answers.

Well GTK or wxWidgets are the candidates if we end up taking that path.

It's not mingw I hate... it's DWT.

Well the specifics are still unclear but you know SDC is ultimately based on DC++ core which compiles under linux, so to get the SDC core compiling under linux should be very much possible without any insane amounts of work. This is ofcourse only the core part... but it would be a start and in the worst case scenario we can always derive from clean linuxdcpp and add our stuff on top of it. The mention about other platforms was not so much about the who and when... but more that we still have the intention of eventually making it happen.

Well strictly speaking "An existing connection was forcibly closed by the remote host" would indicate that the problem is on hub side... since it's the hub dropping the connection, not Apex. As for the nick taken issue... that might sometimes be caused by ghost users on a hub (there are number of reasons why such users may be left lingering on a hub for a while), but once again this is server side phenomenon. While it is odd that such problems would be caused by a client upgrade... and I'll have a look into it, however, since both problems can also be "legit" network related issues rather than application problems it's not going to be easy with just this info.

In all honesty since the detection profiles are no longer actively updated by anyone (well nothing that's widely available anyways) and since the CDM itself has it's own limitations the real world usefulness of an OP client has dropped significantly since the start of ApexDC. Of course there are still things that are useful for OP's like checking users shares for certain kind of files but this ApexDC can do at present anyways. In short the market for OP clients just isn't what it used to be. Well to be more precise the number of people that would want to use an OP client probably still is high, but with the situation the way it is the number of people who actually can use the OP features and not do more harm than good with them has gone down greatly.

The feature already exists (although it's in a need of an update) it has just been turned off for the time being... whether that feature will be re-enabled in the future we do not know yet.

Latest WTL (8.0 is the version, I think) and STLPort 6 from their git repository (if you have problems compiling stlport 6 under msvc, use google).

We do get ~3000 or more downloads a day (we used to get ~5000 a day, but things have slowed down a bit) you know, and that is normal day (ie. not after a release when it usually spikes), of that the installer package is majority... Lee might post some more specific stats to OpenCandy a bit later. As for who chooses the software recommended... ultimately we do the choosing, OpenCandy has picked some for us to start off with but we already excluded those that we thought were not appropriate for our target audience. Lee can give you more details on the process, but remember that since money is involved we do have some boundaries... like we can only choose from those software that are part of the OpenCandy network.

Don't forget to update your plugins for 1.3.2 :unsure:

The installer and the install process is pretty much the same for all scenarios so OpenCandy would display the recommendation in all cases. Also for people who have not watched the video, please do so... it will so how the recommendation looks and works, very close to how it will on our installer.

OpenCandy should not even make a recommendation for crapware, like toolbars etc. all the recommendations coming through it should be proper useful software, and nothing is selected by default like Lee said in his above post.

I'll look into it but honestly I don't recall anything changing around those parts....

Well Win7 certainly performs far better than Vista but I won't say anything in relation to XP. One thing you can try, if only to test it is to turn off Aero and possibly other visual goodies in Win7 and Vista and see how that affects things. Edit: about being connected to 100 or more hubs... although possible it isn't necessary practical. What I mean by this is that DC has for more additional traffic than most other forms of p2p... like chats and the info updates for user connected to the hubs you connect to, these all being traffic that has no strict relation to the file sharing aspect.

You do understand that these differences, as you said yourself, are caused by the switch from XP to Win7. While I can't say that all of them are necessarily issues we can't do anything about, you have to understand that these differences do originate from the underlying OS and not from the program itself (apart from minimize to tray, but that has been sorted in next version).

Let's put it this way, it's not impossible but because it's a plugin it's not worth all the trouble required either (in other words adding a toolbar button is easy under normal circumstances but the way the plugin would have to do it, especially for this button, is not exactly normal).

Since this has ended it two place for some reason here is a link to my reply on the other topic.

put the network location as shared folder manually (ie. by editing dcplusplus.xml, you might need to make the file read-only if it doesn't seem to stick). as for the way of adding stuff manually, add some local folders to share first then look how they are in the xml and edit them (ApexDC needs to be closed when editing the xml files manually).

He might be talking moving it off of his system drive (ie. AppData). If that is the case it can be done by removing dcppboot.xml from your installation folder and moving your settings manually to a subdirectory named "Settings" in your installation folder. Alternatively you can also use dcppboot.xml (by editing it) to place the settings pretty much anywhere.

Because of the dependencies gettext requires I think... besides why fix something that was never particularly broken. I don't really care either way, we'll use what BM uses at least as long as we keep merging with SDC periodically.

Yeah, you are not supposed to point them to the same file... status logging logs the statusbar (of a hub window) and the main chat logging logs the main chat (including status messages printed to/in main chat), Hence the double logging in your scenario

Sorry to disappoint you but I can't reproduce the above issue...

One option I would imagine could work with Aero is white on black (not that I am very fond of such color scheme myself) although there would still probably be some problem spots...

For starters ADC has no default port so trying port 1511 would be just luck if it happened to connect (what I mean to say is that the protocol does not specify default port, I have no clue how common port 1511 is as default on hubsofts).