adrian_007

Member
  • Content count

    86
  • Joined

  • Last visited

Posts posted by adrian_007


  1. Ieshmas: do you use NOD32?

    if you are interesed, i use eset smart security and with my mod i also have this crash from time to time.

    but it's pretty random... maybe it's a nod32 problem... but afaik only with sdc++/mods based on.


  2. you need a professional edition of visual studio, express edition lacks mfc/atl support.

    (but it could be used to compile dc++ when it was using vs ^^, you can always play with 0.699)

    and you need at least stlport 5.2.x afaik (which is still only at svn repo)


  3. FreeLibrary just simply would not work properly

    + we can pass it - just don't use it, app will release handlers on close

    - we can't reload dll at runtime

    i suppose it's because we don't use mscrt dll, it's compiled, or sth else - i haven't investigated it a lot :)


  4. belive it or not but i'll give a chance for ReactOS to take a nice piece of m$ cake in future. afaik it's the only one os developed in this way - to be compatibile with NT, and it's open sauce :D

    and by react os, linux will be a huge step closer to support winapi (which sux imo, we need sometimes to use really dirty hacks to make sth working)


  5. on big hubs, only hubsofts written in c++ will stay on stage - performance is most important thing... how you can imagine server with a couple adc hubs on i.ex soft in java (dchub - yes, it's great hubsoft, but it's still java...).

    and about c++ soft, there is adch++ afaik and... ?


  6. someone can make adc version of verlihub, imo then owners will merge easily.

    or adch++ should be more extended.

    anyway, from my experience verli is the best hub software. but it's only my opinion.


  7. you didn't catch irony in my post :)

    also, dc++ is op client too, because via this client we can check connection to user and also his filelist [manually, but who cares?] and even send raw command! [uc for lazy users :)].

    of course, in my opinion, apex isn't an op client, project is aimed to normal users, but have extended features already implemented in strongdc [with isn't op client, either]... + one new - [from this important] threaded check. however it don't make apex an op client at all.

    and as i said, ops are normal users too, so why we have to make them life harder and force them to use second client to prevent banning?

    you can use Apex as a user client just fine

    i'm using my own op client as op and regular client and it works fine :)


  8. i can say there was mem leaks in raw manager [occur on exit :crying:; look and compare destructors to see difference] and in favorite manager [same one presented in raw manager], also some minor things like warnings that not all controlls return a value or so.