This seems to be the same in 7.56a.
Please provide a fix for this, as it forces me to go back to Explorer for the first time in 15 years!

Thank you!
Moderators: Hacker, petermad, Stefan2, white
Code: Select all
@echo off
if "%~1"=="" (
echo Please specify directory to create files in!
goto :EOF
)
pushd "%~1"
for /L %%i IN (1,1,70000) DO (
if %%i LSS 10 call :DO 0000%%i
if %%i LSS 100 if %%i GEQ 10 call :DO 000%%i
if %%i LSS 1000 if %%i GEQ 100 call :DO 00%%i
if %%i LSS 10000 if %%i GEQ 1000 call :DO 0%%i
if %%i LSS 100000 if %%i GEQ 10000 call :DO %%i
)
popd
goto :EOF
:DO
echo Creating %1
copy NUL %1 >NUL
goto :EOF
I was using Win7 64-bit. Forgot to mention it in the original post...Dalai wrote:I can confirm this in a limited way. I created 70k files using the following script:
and I can scroll to every file in this directory using the scroll bars just fine on WinXP. However, on Win7 the bug exists as described by dvdmaster no matter which TC version is used (tried 7.56a and 8.0 Beta 15 x86 and x64). So this could be a limitation of Win7 GUI elements used by TC.
Code: Select all
if (message.msg=wm_vscroll) and (items.count>32766) and
((message.wparamlo=sb_thumbposition) or
(message.wparamlo=sb_thumbtrack)) then begin
scrollinfo.cbsize:=sizeof(tscrollinfo);
scrollinfo.fmask:=SIF_TRACKPOS or SIF_POS;
GetScrollInfo(handle,SB_VERT,scrollinfo);
if message.wparamlo=sb_thumbtrack then
newposition:=scrollinfo.nTrackPos
else
newposition:=scrollinfo.nPos;
oldposition:=SendMessage(handle,lb_gettopindex,0,0);
if newposition<>oldposition then
SendMessage(handle,lb_settopindex,newposition,0);
exit;
end;
I wonder why Microsoft didn't implement their own suggestion in the listbox control...Note that the WM_VSCROLL message carries only 16 bits of scroll box position data. Thus, applications that rely solely on WM_VSCROLL (and WM_HSCROLL) for scroll position data have a practical maximum position value of 65,535.
But why does it work on WinXP and even Win2k (checked just now) but not on Win7? MS (re)introduced a bug?ghisler(Author) wrote:[...] so it's clearly a Windows bug which is still in Windows 7.