 Thread: A New Version..... |
|
|
I know that a new Neo would be good, but, as far as I see it the new eMule still didn't brought relevant improvements, while changing a lot stuff.
So merging the Neo to the new code base wouldn't brought many new possibilities, but it would took a lot of time.
It you manage the Official dev team to implement something new that is relay an improvement, like for example Nat Traversal or IPv6 support.
That it would be a good reason to update the Neo, but as long as they don't innovate merging would be just a waste of time.
|
|
| Thread: New version |
|
|
Well, I don't really see a need for an update at this time, I'm waiting currently for some new eMule release with relevant improvements.
|
|
| Thread: NeoMule Entwicklung |
|
|
Naja, etwas zeit werde ich in so 3 monaten haben wen alles so funtzt wie geplant.
Aber ich denke unabhängig von meiner freizeit werde ich die aktuelle Version 0.49c vom offi überspringen.
Da sind kaum nennenswerte Verbesserungen drin, dafür haben die einpaar listen von der GUI massiv überschrieben und das ist ewig viel arbeit das zu mergen.
Bals sollte e'h ne nächste offi version kommen, ist ja schon mahr als ein halbes jahr vergangen 
|
|
| Thread: emule 0.49c |
|
|
I took a look on the code and the wast majority of the changes is trivial, in some files there are really extensive changes mainly in *listctrl.*
its not to much work to update the when excluding the listctrl's and this should have no impact on the functionality at all (except some minor gui improvements form the offi c will be missing).
|
|
| Thread: emule 0.49c |
|
|
Well the eMule _team_ needed over a half a year or so if I remember right to make the c version,
I'm 99% sure I'll need les time to update neo most important including the time I'll need to find the time to do it, because once I found it a week or even only a week end will suffice I presume.
PS: But if there is someone out there willing to do it for me I would be very happy
|
|
| Thread: upload bonus bug |
|
|
The best practice is to have a 1 copys of the source 1 for compiling and releaseing and one for testing and coding new stuff, after a new version is ready delete the old copy and copy the new one, it may also be a good idea to keep the old copys 1 or 2 revisions back in time in case a new bug gets in and so you can see what you'v changed and find it easyer.
|
|
| Thread: upload bonus bug |
|
|
Dimpfiles are quite simple, you just put the dump file in the build direcotry where the released exe ended up together with tzje *.pdb file than you doubleclick on the dump file and click projectmap-explorer tree on the new project and use the submenu obtion "jump into the instance" (translated form german the actual menu entry may be calles a bit different in the englich version)
Then VS should take you directly to the place in the source where the crash happend, very much like if youd run the app localy and got the crash with a debugger attached.
Best Regards
David X.
|
|
| Thread: TCP-Z, V2.3.1, Build 20081229 Release |
|
|
You can not hack the driver offlien on vista,
but you can install a driver patcher that removes the limitation using a memory patch on system startup.
|
|
| Thread: "FORCE" function |
|
|
The force obtion bypasses the standby/suspend features, that can be automaticaly triggered by ""Download only complete files" and/or "Soft Lock"
|
|
| Thread: Mule oder Usnet? |
|
|
Once upon a time I downloaded 1,4 TB in only one month with my NeoMule, and its 100% free.
|
|
| Thread: Connect 2 server |
|
|
1. its not alowed by the official devs
2. servers are to 90% fakes
3. it does not brig any advantage
4. use kad and forget servers
|
|
| Thread: Complete sources... |
|
|
The problem with this value is that it relays on datas send by other clients, and there are some bad lcients out there that sands imaginery values and this screws up the localy displayed value, and unfortunatly this can not be simply fixed that.
|
|
|
