-
Content count
139 -
Joined
-
Last visited
Posts posted by RoLex
-
-
I corrent myself.. It does send search results, but not all. For some reason it skips some (whis ones exaclty?).
Satan, and this is normal?
-
Hi.
It looks like ApexDC++ doesn't answer on any search requests from the hub. I have not noticed it until today when a person was searching for a song title I gave him. He should have found it in my share.
I'm sure that I have 9 of 9 slots free, so there is no "Only users with free slots" issue.
I'm sure that my connection settings are correct, I can search and download, upload by myself. (this has nothing to do with search results sent by client tho)
I'm sure that a person who is trying to search has correct connection settings, he can search and find other stuff without problems. (I tested this using 2 clients aswell, ApexDC++ does'n respond to "existing" requests made by client 2)
I'm sure the file is shared, it has been hashed and filelist refreshed. It exists when user looks in my manually downloaded filelist.
I've also beed using CMD debug messages window for about half a hour and didn't see any $SR sent by client. (on 10 pretty active hubs)
I take this as a bug. Please correct me and give more suggestions on other ways to prove that issue. Thank you.
-
Good news, atleast they sounds good. =)
I like new design, and I like how you guys keep everything clean. Keep it on.
-
I've heared that DC++ stops reconnecting when it finds word "banned" before connection close. It's an alternative, but maybe not that useful in hubs with non-english languages.
-
..and modifying it does not change the line that the client throws outAs I said, those are either translatable or can be modified. They are predefined in socket library of your OS.
They are still in DC++ stringdefs because they had own translations once, and has not been removed after changing to default system messages.
-
You cant modify those strings. They are created by your operating system.
It is ofcourse possible to to read ErrorNumber being returned from socket, but it requires some extra implementation.
No.
No.
Why no? Message is written in the same language as your OS, could be easier to understand. Simply provides more information.
-
i would support a fixed with font as default...makes it easyer to make an ascii motd
And what does this have to do with my feature request?
-
ApexDC++ freezes
I would like to tell you that my client froze yesterday. It happened when I tried to close About window. (it happened only once, usually everything is ok)
Absolutely no idea what happened. But one thing is for sure -- version.xml was already downloaded.
I guess it's something with uptime thingie.
Thank you.
-
Being noob in this case is not about knowledge of what "Program Files" is, or whatever. It's about legality of shared files, the way it can turn back on you.
-
noobs that dont know what "Program Files" isNoobs should not use DC anyway.
-
What is the problem? Download archive, shutdown ApexDC++, extract EXE and PDB file to Apex directory - overwrite the files. 10 seconds of work.
-
I have few things that you might like adding to/changing in ApexDC++;
1. Adding queue size in status bar, along share size. (fulDC feature)
2. Timer command. You simply type something like "/timer 35:0 Time to go to work", after 35 minutes a small windows pops-up together with the message you wrote. "/untimer" could be used to reset it. (fulDC feature)
I've submitted a patch for this feature to Big Muscle once, but he does not seems to like it much (or forgot).
3. Changing entire application fonts to Tahoma. I don't mean the chat or userlist fonts, but component/forms fonts. Search frame, public hubs frame for example, they are still using MS Sans, which is the ugliest font I've ever seen (even more ugly with ClearType enabled). =)
4. Centering settings window on open. On computers with high resolution you have to manually move the window to the middle every time, it's not that comfortable having it in top-left corner while working with it. Same thing with indexing progress window maybe?
That's all for me. Thank you.
-
Haha, that was really fast. Anyway, I would like to thank you for great client. 1.x is completely outstanding, comparing to previous releases.
Good work. :P
[1.0.1] Client doesn't send search results
in 1.0.x
Posted
Yes, I know that kind of behaviour in for example Verlihub, antiflood feature. But it has nothing to do with the client search request responce, that user should have got the result when he made his first search. He didn't get it.