Max Dyckhoff wrote:
I use gvim 7.0 on Windows XP, and I always have multiple tabs open. I
use a custom tabline, but this bug is visible with the default tabline
as well.
When I am bored and thinking about what to code I often play around with
the mouse selecting text and dragging around inside gvim. Normally if
you select text and drag the cursor off the bottom of the window then
the text scrolls up, as you would expect. If you drag off the top of the
window, passing over the tabline, then gvim essentially freezes until
you release the mouse button. The text does not scroll in any direction,
and you can wave the cursor over the window as much as you like and the
same text selection will remain.
Without the tabline visible this behaviour does not happen, and the text
scrolls as expected.
It looks like whatever grabs the cursor to allow you to click on the
tabs to select them is grabbing the cursor when you pass over the
tabline and refuses to release it until you release the cursor.
I doubt there is a fix for this, so I suppose this email is serving
rather more like a bug report, I'm just not sure if there is a better
forum to announce this, and I'm sure I remembered someone saying bugs
should be reported here!
Cheers,
Max
--
Max Dyckhoff
AI Engineer
Bungie Studios
In console Vim on Linux I don't see any scroll, not even when the mouse
is dragged off the bottom. The visual selection only appears after
releasing the mouse button. (This doesn't affect me much, since I
usually use the keyboard to select text by means of the v V ^V
Normal-mode commands.)
In gvim I see this only in the top window of a tab (in other windows,
scrolling happens as soon as the mouse is dragged over the status line
of the window above the current one).
However, if the mouse is dragged quickly past the tabline and into the
toolbar/menubar/titlebar area, then scrolling happens, but not every
time. I'm not sure how to make absolutely sure that it will scroll.
Bugs can, IIUC, be reported directly to Bram. They can also be reported
on the maillists if there is a reason to warn the users about them.
Whether to report them on vim@ vim-dev@ vim-multibyte@ etc., depends on
the nature of the bug.
Best regards,
Tony.
