eshield: you don't need to be worried. As always, some workarounds appear - it doesn't mean are final solutions, because can break other intended stuff on code!
What I know is that this changes made it usable again, with W10 with update 1709 (at least for me, on 2 machines):
Code: Select all
--- src/video/sdl_v.cpp (revision 27927)
+++ src/video/sdl_v.cpp (working copy)
@@ -532,7 +532,7 @@
switch (ev.type) {
case SDL_MOUSEMOTION:
- if (_cursor.UpdateCursorPosition(ev.motion.x, ev.motion.y, true)) {
+ if (_cursor.UpdateCursorPosition(ev.motion.x, ev.motion.y, false)) {
SDL_CALL SDL_WarpMouse(_cursor.pos.x, _cursor.pos.y);
}
HandleMouseEvents();
Code: Select all
--- src/video/win32_v.cpp (revision 27927)
+++ src/video/win32_v.cpp (working copy)
@@ -747,7 +747,7 @@
SetTimer(hwnd, TID_POLLMOUSE, MOUSE_POLL_DELAY, (TIMERPROC)TrackMouseTimerProc);
}
- if (_cursor.UpdateCursorPosition(x, y, true)) {
+ if (_cursor.UpdateCursorPosition(x, y, false)) {
pt.x = _cursor.pos.x;
pt.y = _cursor.pos.y;
ClientToScreen(hwnd, &pt);
That was
tomb's workaround I think that this temporary solution applies to all releases or patchpacks, for players that are under W10 and got the 1709 update. Since this happened because a W10 update, maybe SDL change isn't needed... but on the allegro it's set as false by default. And this where my knowledges lack :S
BTPro created a version with the workaround, Vanilla compatible, because some players needed it:
link here -
(check Readme.txt file BUT please remember that's a workaround)
The
3298's approach, never tried it! The must have "reverse scrolling on" scared me as hell, because it's not the default ^^
If you're able to compile it, changes above will make it playable after the mentioned W10 update: Other locations about this "problem":
-
https://bugs.openttd.org/task/6629
-
https://www.reddit.com/r/openttd/commen ... _viewport/
-
https://www.reddit.com/r/openttd/commen ... ght_click/