Crise

Might you like PM'ing that link to me?

Will check that :)

Happy new year guys :)

Why would it need to be like that?

The problem in adding such main chat triggers/switches is that in Apex you don't check in fav. hub properties to enable checking, but instead the check box is for excluding hub from checking... (i saw it as easier to check that option in 4 hubs, rather that checking the proposed opposite option in 10 hubs f.ex.) Of course this requires the option in fake detector page to be checked to have any effect, since it's an exclusion...

nick is userNI clienttype is userCT clientdescription would probably be userCM some of the old macros should still work in certain places however, but ofcourse it's better to use the new ones instead...

ApexDC++ 0.4.0 polish language file by Patrol attached below ApexDC_0.4.0_polish.zip

Ah, that was when i wasn't yet completely familiar with TBI's code... i don't remember what exactly i did mean there but that i can say that it wasn't anything in regards to slots...

Copy pasting? Ok will take a look...

The only problem i could find with the theme file you attached, was with coloring of hyperlinks (used black as a color for them, so thus invisible) But afaik colorization of the hyperlinks is bit problematic in XP, when it comes to using styles from settings, with Vista this however should work fine...

Mind refreshing my memory, since i can't follow here?

Zlobomir, you don't need to ask for a permission all the time, since you can move it and you think it should be moved then move it! As for the issue: So the script/hub is the faulty not ApexDC++ to get the 100% correct slot count with ApexDC emulation or no emulation all the script needs to do is check for S:x in tag, as it probably does now, but it most likely just doesn't recognize ApexDC's tag so that's why it can't parse it or treats it as "tagless".

They are configurable on fav hubs afaik If you can trace the exact problematic property or properties that would help a lot, as there are lot of style related options and for some reason i don't feel like going through them all (as i have never seen what you have described as far as i can remember)

Well in that case an exsample hub would be very useful...

is this verlihub? Edit: anyways as for the issue afaik open slots are reported correctly in all places, and client tag is always the most certain place to look for that info... Edit2: can you give me an exsample hub where this is happening?

Only thing you can do is increase the value of "Delay when sending $PSR" :)

You are quite right, however since version 0.3.0 (or was it 0.2.2) partial info (assuming you talking about $PSR here) is only sent to 20 sources and (by default) only if it has been at least 30 seconds since the last time the info was sent...

%[userCS] should give you what you want in ApexDC++ :)

Note when using DC++ emulation as far as i know loosing a slot is possible to keep the emulation working properly...

Yep, you need it ddraw.h from it...

Yeah i know, sorry

It's not that we don't care... maybe there just is nothing to say regarding these reqs, but they are still being considered. As for the bug, what bug are you talking about?

maybe this is bit rude, but are you blind? Just look at the balloon popups page... yes i have changed but it works flawlessly here, dunno why it doesn't work for everyone, but as i explained above afaik it's just the previews that don't work for everybody...

also users CID is stored as well not just nick

The preview button has been reported not to be working with certain configurations, but since i can not reproduce this on my machine it's bit hard to figure a fix for it... However the actual popups do work according to previous reports (ie. not preview but real deal), will check the freezing tho.