I'm not sure what is the cause of this. I think I already had this bug report, but I don't know what is wrong.
Since Console itself performs exactly the same steps when it gets a scroll message from either keyboard or mouse, I don't know what could be wrong with the code itself.
The only difference is that mouse scroll usually scrolls 3 lines per one turn of the wheel, so Console gets 3 scroll messages. Maybe mouse driver adds a small pause between two messages, I really have no idea. Could you try setting the number of lines to scroll to 1 in your mouse driver settings and see what happens?
Also, I cannot reproduce this on three different computers (the oldest one is 6 years old P4) All of them use MS mice.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Even with the setting set to scroll one line at a time, it is slow.
Also when using "one page at a time" it is still slower than when using my keyboard shortcuts I use to scroll with.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As explained in the starting post, if I use my keyboard scrolling hotkeys, it's pretty fast. If I use the mouse to scroll, it is slow.
Or do you mean hold the scrolling hotkey modifier (e.g. ALT/SHIFT etc.) and then try scrolling with the mouse? Either case, I've tried, and scrolling is slow when using a mouse.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It still occurs with the build from Console-2.00b145-Beta.zip.
Oh, and, by using the scroll hotkey it doesn't occur, as explained earlier (which was what I meant in the first place with scrolling by using the keyboard, which caused confusion later on when you asked me about trying it by pressing and holding the scroll hotkey).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
FWIW: cmd does not observe wheel settings. Here is what I did:
1. (with "scroll 3 lines" setting) start cmd with 5000 buffer lines, scroll one click - three lines are scrolled
2. Exit
3. Change wheel setting to 10 lines
4. start cmd with 5000 buffer lines, scroll one click - three lines are scrolled
So, I'd say the "sluggish" effect is caused by the fact that you have to spin the wheel pretty "far" to scroll the same number of lines (remember: key repeat for Scroll buffer row up key is likely to be much faster than you can "spin" your wheel).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A little help in reproducing the bug in a noticeable way:
1. Open a text file in Notepad (in this example 'x.txt').
2. Open a Console2 window and execute the command 'type x.txt' so that its contents are shown.
3. Compare how responsive Notepad seems in comparison to Console2 when scrolling with the mouse.
Also, I should probably tell that sometimes the bug doesn't really seem noticeable. Nevertheless, it really is there.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure what is the cause of this. I think I already had this bug report, but I don't know what is wrong.
Since Console itself performs exactly the same steps when it gets a scroll message from either keyboard or mouse, I don't know what could be wrong with the code itself.
The only difference is that mouse scroll usually scrolls 3 lines per one turn of the wheel, so Console gets 3 scroll messages. Maybe mouse driver adds a small pause between two messages, I really have no idea. Could you try setting the number of lines to scroll to 1 in your mouse driver settings and see what happens?
Also, I cannot reproduce this on three different computers (the oldest one is 6 years old P4) All of them use MS mice.
Even with the setting set to scroll one line at a time, it is slow.
Also when using "one page at a time" it is still slower than when using my keyboard shortcuts I use to scroll with.
Can you try your mouse on a different computer or a different mouse on your computer?
I'm not sure if the slow(er) 2D performance of your video card could be the problem. Can you try this with a solid black background in Console?
I use Console without a background. Also with a Microsoft mouse scrolling is slow.
Are you thinking it could be the graphics driver?
I have no idea...
What happens if you press and hold the scroll hotkey? Is there any speed difference?
As explained in the starting post, if I use my keyboard scrolling hotkeys, it's pretty fast. If I use the mouse to scroll, it is slow.
Or do you mean hold the scrolling hotkey modifier (e.g. ALT/SHIFT etc.) and then try scrolling with the mouse? Either case, I've tried, and scrolling is slow when using a mouse.
Can you try this with the latest build?
--
Marko
It still occurs with the build from Console-2.00b145-Beta.zip.
Oh, and, by using the scroll hotkey it doesn't occur, as explained earlier (which was what I meant in the first place with scrolling by using the keyboard, which caused confusion later on when you asked me about trying it by pressing and holding the scroll hotkey).
FWIW: cmd does not observe wheel settings. Here is what I did:
1. (with "scroll 3 lines" setting) start cmd with 5000 buffer lines, scroll one click - three lines are scrolled
2. Exit
3. Change wheel setting to 10 lines
4. start cmd with 5000 buffer lines, scroll one click - three lines are scrolled
So, I'd say the "sluggish" effect is caused by the fact that you have to spin the wheel pretty "far" to scroll the same number of lines (remember: key repeat for Scroll buffer row up key is likely to be much faster than you can "spin" your wheel).
@akirill: No, it's not related to those facts.
A little help in reproducing the bug in a noticeable way:
1. Open a text file in Notepad (in this example 'x.txt').
2. Open a Console2 window and execute the command 'type x.txt' so that its contents are shown.
3. Compare how responsive Notepad seems in comparison to Console2 when scrolling with the mouse.
Also, I should probably tell that sometimes the bug doesn't really seem noticeable. Nevertheless, it really is there.