tts2271

i was wondering, since there is this option not to delete the filelists when exiting, is it possible to include them when searching something so you dont have to open every single one of them manually and search then one by one. maybe as a addtional option in the search dialogue [x] search online, [x] search offline filelists only or [x] search both etc..

so whats with the pointless downloading of tth files over and over again? any solution for that?

there's definately something not right with this version, ever since the 1.2beta it sometimes startet pointless downloading of tth files over and over again. happend to me too a lot of times... wouldn't recommend updating to anybody even its now called stable it has this major issue.

can you please disable the default emulation when connecting to a hub through the quick connect option? whats the point in having this on anyway? i thought apexes policy was to proudly present the real tag of this great client and only emulating when its absolutely neccesary, not the other way around.

RTFM! ApexDC++ Windows User Guide section 'Progress Bar Tags explained'

:-( that so totally doesnt makes sense. emulation makes mulisource less effective for example. it should be off as a default setting for quick connect also, or at least as a option in the settings to enable it afterwards.

anything new on that? is it coming? is it beeing considered?

me too! woohoo! :-) just read that here about that cool idea, and i must admit that would be totally awsome having it.

any news regarding that matter?!

Code: c0000005 (Access violation) Version: 1.0.0B2 (2007-04-10) Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2007-06-19 03:06:57 TTH: CWLBR24QOCVAJHKKX2A6KQORSW4IRCWPJH36EYA ntdll!0x7C928FEA: RtlpWaitForCriticalSection ntdll!0x7C91104B: RtlEnterCriticalSection d:\cvs\apexdc++\trunk\client\user.h(114): Identity::getNick d:\cvs\apexdc++\trunk\windows\hubframe.cpp(693): HubFrame::onSpeaker d:\cvs\apexdc++\trunk\windows\hubframe.h(74): HubFrame::-ProcessWindowMessage d:\program files\microsoft visual studio 8\vc\atlmfc\include\atlwin.h(3078): ATL::CWindowImplBaseT<WTL::CMDIWindow=0x01738ED8,ATL::CWinTraits<1456406528=0x00000000,64> >::WindowProc USER32!0x7E368734: GetDC USER32!0x7E368816: GetDC USER32!0x7E3689CD: GetWindowLongW USER32!0x7E368A10: DispatchMessageW d:\cvs\apexdc++\includes\wtl\atlapp.h(584): WTL::CMessageLoop::Run d:\cvs\apexdc++\trunk\windows\main.cpp(431): Run 0x00B400E2: ? ApexDC!0x0044E2A2: MainFrame::FileListQueue::`scalar deleting destructor' ApexDC!0x00469A57: [thunk]:MainFrame::`vector deleting destructor' ole32!0x775AE818: StgIsStorageILockBytes

my beta2 crashed one single time up to now, so i just want to leave you guys the exceptioninfo.txt. maybe its of some use to the developers.. Code: c0000005 (Access violation) Version: 1.0.0B2 (2007-04-10) Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2007-05-11 21:37:58 TTH: CWLBR24QOCVAJHKKX2A6KQORSW4IRCWPJH36EYA ntdll!0x7C928FEA: RtlpWaitForCriticalSection ntdll!0x7C91104B: RtlEnterCriticalSection d:\cvs\apexdc++\trunk\client\user.h(134): Identity::isHidden d:\cvs\apexdc++\trunk\windows\hubframe.cpp(677): HubFrame::removeUser d:\cvs\apexdc++\trunk\windows\hubframe.cpp(779): HubFrame::onSpeaker d:\cvs\apexdc++\trunk\windows\hubframe.h(74): HubFrame::ProcessWindowMessage d:\program files\microsoft visual studio 8\vc\atlmfc\include\atlwin.h(3078): ATL::CWindowImplBaseT<WTL::CMDIWindow=0x01504620,ATL::CWinTraits<1456406528=0x00000000,64> >::WindowProc USER32!0x7E368734: GetDC USER32!0x7E368816: GetDC USER32!0x7E3689CD: GetWindowLongW USER32!0x7E368A10: DispatchMessageW d:\cvs\apexdc++\includes\wtl\atlapp.h(584): WTL::CMessageLoop::Run d:\cvs\apexdc++\trunk\windows\main.cpp(431): Run 0x003C0286: ? ApexDC!0x0044E2A2: MainFrame::FileListQueue::`scalar deleting destructor' ApexDC!0x00469A57: [thunk]:MainFrame::`vector deleting destructor' ole32!0x775AE818: StgIsStorageILockBytes

since the waiting users list is kind of a upload queue it would be nice to be able to select a priority for every single one who is in the waiting queue just like for the downloads. it would also have to be persistent, so if a high priority user disconnects/reconnects from/to the hub he wouldnt have to wait to continue his download because hes on bottom of the waiting list. how about that?!

hmm, what do you consider as 'real'? is there any other way to give a certain user a higher priority in the waiting users list?