New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mouse wheel only works on first console in split window #216

Open
sejjiin opened this Issue Jul 16, 2015 · 15 comments

Comments

Projects
7 participants
@sejjiin

sejjiin commented Jul 16, 2015

When splitting consoles, mouse wheel scrolling only works reliably on the first console. On console 2 and 3, it rarely works. I haven't been able to pin down what triggers it to start working, but when it does, it only works briefly. I'm using 150707 [64] on Windows 8.1.

I have the below Task set up as the default task for new consoles.

>cmd -cur_console:n

-cur_console:ns1T45Vd:%startupDir% cmd /k tail -f Log.log

cmd -cur_console:ns1T50Hd:%USERPROFILE%

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Jul 16, 2015

I think the key is a focus, where the text cursor is blinking...

@sejjiin

This comment has been minimized.

sejjiin commented Jul 16, 2015

It is focusing on hover (and the cursor is blinking), but will not scroll whether I click on the console first or not. Console 1 will scroll by simply hovering over it and scrolling the mouse wheel.

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Jul 16, 2015

Can you reproduce that with log files?
http://conemu.github.io/en/LogFiles.html

@SamHasler

This comment has been minimized.

SamHasler commented Jul 20, 2015

@sejjiin do you use KatMouse or some other "mouse follows focus" software? I was having issues with splits until I set KatMouse's classes tab as follows:

VirtualConsoleClass      Default
VirtualConsoleClassBack  Ignore
@sejjiin

This comment has been minimized.

sejjiin commented Jul 20, 2015

Thanks for the replies. I don't use KatMouse, but do use Synergy, which might be conflicting somehow? I'll see if I can reproduce with the Synergy service stopped and, if so, attach logs here.

@deltreey

This comment has been minimized.

deltreey commented Aug 10, 2015

@erquhart

This comment has been minimized.

erquhart commented Aug 25, 2015

I am now encountering this issue after upgrading to Windows 10. Using Windows 8.1 I never had an issue. I don't use KatMouse, Synergy or anything like them. Only the first split scrolls with mouse wheel - the others do not, regardless of focus. This is using the msysgit (Git for Windows 1.95.x) bash - other shells do not exhibit this behavior. The new version of Git for Windows (2.x) has way too many issues to make an upgrade worthwhile.

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Aug 30, 2015

Problem confirmed on Win10.

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Aug 31, 2015

Another Microsoft Bug!
https://msdn.microsoft.com/en-us/library/ms645617.aspx
LPARAM do not let you obtain screen coordinates anymore.

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Sep 2, 2015

Build 150813c (preview)

@VictorOscar

This comment has been minimized.

VictorOscar commented Jan 7, 2016

I'm seeing this in Build 151208 on Win8.1, but not on Win10. I also tried on Build 151224 with the same results. When testing on Win10, I'm going through Remote Desktop.

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Jan 7, 2016

LogFiles reproducing the problem with full-screen screenshots to be sure where mouse cursor is located when you scroll the wheel. StatusBar must be visible on screenshots.

@CollinChaffin

This comment has been minimized.

CollinChaffin commented Jun 18, 2018

FYI, I have identified and will be reporting to that author that if you are using x-mouse style apps like "x-mouse button control" (and possibly other x-mouse background-style mouse enhancers), THAT in my case was the cause of what you are describing - only my 1st pane in any split config scrolled, even with the mouse options all enabled in conemu. Simply right-clicking the xbutton and disabling instantly allowed ALL panes in conemu to begin scrolling properly.

EDIT: I opened an issue with XBMC author here:

https://forums.highrez.co.uk/viewtopic.php?f=6&t=3885

And of note as I also stated there - this issue is the same whether the mouse events enabled in conemu or not, as well as whether the panes (any of them other than #1) are active or background.

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Jun 18, 2018

Can you create LogFiles with screenshots? Mouse over first split and second split for example?

@Maximus5 Maximus5 added this to To Do in Inspection via automation Jun 18, 2018

@CollinChaffin

This comment has been minimized.

CollinChaffin commented Jun 18, 2018

I can report for those using XBMC (and other x-mouse type mouse enhancers) - I have performed additional testing which has confirmed a fix:

Change the mouse message type to "WPF Scrolling Msg" as shown here:

snag_6-17-2018_20-01-47

Any other mouse message type he uses (#1-4) render successful results but the WPF, when adjusted to 3 lines as shown above - shows un-noticeable difference in usability from any other window, so I could find no down-side in simply creating a new application profile in XBMC for the Conemu app and window class to simply always switch to the WPF method and it is working great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment