ok ill tell ya straight up it may not me mirc entire fault but ill see if any one else can reproduce it. in running windowblinds which may be a factor but i doubt it very much.

leave mirc connected to a sever in a midsized (3x people) half busy channel for 22 hours and try to scrolll up with a wheel mouse or the scroll buttons, or drag the scroll slider. it tries to resist scrolling. mirc has the default buffer line settings also

yeah same effect here and size of a channel doesnt seem to matter, noticed this since 6.x mirc came out, dunno if it affected it previously, tested it in 6.02 6.03 6.11 and 6.12 it all does the same thing eventually, however, if your take the mouse and grab the scrollbar and run it all the way to the top and then back down, it corrects itself.

im glad im not the only one. hopefully this will be fixed soon

search on it... I have posted it the first time including screenshot, a few others posted this bug too...

still have the bug, running win2k and mIRC 6.12

too lazy to search and i have never seen this posted..

ppl who are too lazy to help themselves openly usually dont get the right help. just so u know i am calling you lazy. But thats niether here nor there.

i just know i posted a bug that i have found. no need to search,,

Irony, I was having problems scrolling in this thread, found out my computer didn't like the system lag caused by Doqnach's animated avatar.

lol. i dont have a slightest problem with that

I had that until I changed my mouse drivers. mIRC doesn't seem to like some. Some people also might need to change the visual styles to no borders, I guess.

I already use "no borders" and have the latest mouse drivers...

but what does the mouse driver have to do with the visual appearnce of the scrollbar?
the problem is nog only scrolling with the mouse but also with pgup/pgdn

http://forums.mirc.com/showflat.php?Cat=...=true#Post29735

which also happends in 6.12 Win2k... but not as often...

I've posted about this bug before, but more focused on the mouse wheel (however, it also used to happen with PGUP/PGDN). Then, Khaled suggested changing the mouse drivers. I don't know the connection between the bug and these, but it completely disappeared right after I changed them.