Skip to content
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

Scroll on edges screen not working properly #1591

Closed
DorpsGek opened this issue Dec 26, 2007 · 7 comments
Closed

Scroll on edges screen not working properly #1591

DorpsGek opened this issue Dec 26, 2007 · 7 comments
Labels
component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

StressMan opened the ticket and wrote:

I use the OpenTTD 0.6.0-Beta2 version for Win9x.

Well, I use OpenTTD on a laptop-computer under Win98SE.
It is a 800x600 screen, so I use the Full-Screen mode to view all that's possible.

If I place my mouse on the most left, right, under or upper position, I can't scroll (with the right mouse button) to the direction where my mouse is located:

For example: When I place the mouse on the most left position, I can scroll up/down/right (with the right mouse button pressed), but not to the left.
As I place the mouse on the most right position, I can scroll to the left/up/down, but not to the right.

As far I have tested, it appears only to be at full-screen, or if you use an 'other' resolution, which covers both sides of the screen (so you can't see the window-edges), but with the 'other' resolution it is not always (it may appear only when you are on the most left/right/upper of lower pixel-line.)

Tested versions of OpenTTD:

Version: OS: Result:

0.2.0 Win Present, only there is no full-screen option, adjust the screen resolution to the resolution your are using in Windows. You can then use the most left/right to try.
0.3.4 Win Present, see comment on 0.2.0
0.3.5 Win Present, in this version Fullscreen is available
0.3.6 Win Present
0.4.0.1 Win Present
0.4.0 Win Present
0.4.5 Win Present
0.4.7 Win Present
0.4.8 Win Present
0.5.0-RC3 Win Present
0.5.0-RC4 Win Present
0.5.0 Win Present
0.5.3 WinXP Present
0.6.0-Beta2 Win9x Present
0.6.0-Beta2 WinXP Present

As I haven't got Linux, MacOS, or other operatings systems, I can only test the Windows builds.

It has been tested on 3 systems, 2 WinXP and 1 Win98SE

If you need more information, please notice. I hope that I can help you as much I can.

Reported version: 0.6.0-beta1
Operating system: Windows


This issue was imported from FlySpray: https://bugs.openttd.org/task/1591
@DorpsGek
Copy link
Member Author

Rubidium wrote:

There's hardly anything that can be done about this 'issue'.

What happens is that the operating system, in this case Windows, moves the mouse in the window. OpenTTD 'catches' that and looks whether that location is different from the location where you started pressing. If that is the case OpenTTD will 'reset' the location of the mouse and move the window. When you are at the right edge of the window the operating system cannot move it to the right and will therefor not do it. It will also NOT send a message that he mouse moved to the right.

So basically there is no way for OpenTTD to know that you moved the mouse to the right, and if OpenTTD does not know it it cannot move it either.


This comment was imported from FlySpray: https://bugs.openttd.org/task/1591#comment3106

@DorpsGek
Copy link
Member Author

DorpsGek commented Jan 1, 2008

egladil wrote:

It behaves the same way on OS X. But this can hardly be called an OpenTTD bug because of the reasons Rubidium gave above. Also, I find it difficult to think of a situation where this would actually affect game play.


This comment was imported from FlySpray: https://bugs.openttd.org/task/1591#comment3144

@DorpsGek
Copy link
Member Author

DorpsGek commented Jan 2, 2008

StressMan wrote:

Thnx for the confirmation and the replies.

Well, I use it on a old laptop with a G-H joystick mouse (between the G and the H key).
Expecialy when I am fast scrolling with the mouse, I notice that I'm actualy first moving the mouse in a corner/edge before I press the right-mouse button (not on purpose, this because the speed I'm working (fast thinking, too slow clicking))

Also, when you are scrolling with the right-mouse button, it sometimes happens that you ain't pressing enough on the button, so that the cursor went to a corner/edge off screen (as if the button is no more pressed). When pressing hard enough on the button, that the scrolling ain't working properly (because you are on the edge off the screen).

I'm aware, that is not that important for everyone. They use most of the time a normal mouse.
Also if you are using a touchpad (as I use on another notebook)

Well, actualy I find it annoying (above the reason). Also the option to auto-scroll, it ain't working properly because I park the mouse cursor a lot of time in a corner to observe the screen, to think or whatelse. With the autoscroll enabled, the screen moves, which is anoying to me.


This comment was imported from FlySpray: https://bugs.openttd.org/task/1591#comment3149

@DorpsGek
Copy link
Member Author

DorpsGek commented Jan 3, 2008

Rubidium wrote:

As said before... the 'problem' does not lie at OpenTTD's side, but at a completely different level, being your operating system. OpenTTD does not receive any signals that you are moving the mouse 'outside' the window (moving it left of the left corner) because the operating system determines that this information does not need to be send to applications.

See the dilemma? I'd love to fix the issue for you, but I can't because OpenTTD does not know that you are moving the mouse because your operating system does not tell OpenTTD that the mouse is 'dragging' outside of the window.


This comment was imported from FlySpray: https://bugs.openttd.org/task/1591#comment3150

@DorpsGek
Copy link
Member Author

DorpsGek commented Jan 3, 2008

StressMan wrote:

I have given some reasons, where and why it can be nasty.
As reply to Emil Djupfeldt (egladil)
[i]Also, I find it difficult to think of a situation where this would actually affect game play.[/i]

I'm aware, that it is an OS-issue.
I can point to another game where the issue ain't be there (like Roller Coaster Tycoon 3, Locomotion)
Even the old TTDX hasn't the issue.
But this is proberly build with an kind of overlay, or in another way programmed.

You won't need to fix it for me, but I would let you know about the 'issue'. If it could be easely fixed (some option).
As told before, it ain't that easy...


This comment was imported from FlySpray: https://bugs.openttd.org/task/1591#comment3151

@DorpsGek
Copy link
Member Author

emjay wrote:

What about if there was a 1px "buffer" around the screen where you can't move your mouse (ottd moves the mouse back to 1px away from the absolute edge) then when you right click, the os should still send movement events.

You can still draw graphics under this "border" but just don't let the mouse move there.

Of course this will only work in fullscreen mode (otherwise, you wouldn't be able to move the mouse out of the window).

Sorry for resurrecting this thread after more than a year :S


This comment was imported from FlySpray: https://bugs.openttd.org/task/1591#comment5811

@DorpsGek
Copy link
Member Author

andythenorth closed the ticket.

Reason for closing: Won't fix

Flyspray clean up: issue is upstream, more than 5 years old, and it's not obvious what should be done with this next, so closing. If this offends, discuss with andythenorth in irc. Thanks.


This comment was imported from FlySpray: https://bugs.openttd.org/task/1591

@DorpsGek DorpsGek added component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) enhancement labels Apr 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)
Projects
None yet
Development

No branches or pull requests

1 participant