Opened 8 years ago

Last modified 3 years ago

#3759 new defect

Camera doesn't scroll if cursor outside of window

Reported by: robooze Owned by:
Priority: Must Have Milestone: Backlog
Component: UI – In-game Keywords:
Cc: Patch:

Description (last modified by Freagarach)

The in-game screen doesn't move while moving the cursor over the right edge and top corners of the screen.

I am having this issue with the XIX version on Linux Kubuntu 14.04.

Change History (13)

comment:1 by robooze, 8 years ago

Component: Core engineUI & Simulation
Milestone: BacklogAlpha 20
Owner: set to robooze

comment:2 by robooze, 8 years ago

Owner: robooze removed

comment:3 by robooze, 8 years ago

Description: modified (diff)

comment:4 by mimo, 8 years ago

I had a similar problem some months ago when testing the switch to sdl2, but don't have it anymore. I've updated my ubuntu between these two events. So maybe the sdl2 version which come with 14.04 has not all the needed fixes ? can you check which version you have. On my kubuntu 15.10, i have 2.0.2+dfsg1-6ubuntu2

comment:5 by robooze, 8 years ago

This is what I have:

rc  libsdl1.2debian:i386                       1.2.15-8ubuntu1.1                       i386         Simple DirectMedia Layer
ii  libsdl2-2.0-0:i386                         2.0.2+dfsg1-3ubuntu1.1                  i386         Simple DirectMedia Layer

comment:6 by elexis, 8 years ago

If he uses alpha 19, then he uses SDL2.

To me it sounds like a logical behavior. If the mouse is not inside the window, then the window doesn't react to mouse events? (Might be useful though)

I'm using ubuntu and it has never scrolled in windowed mode here, unless finding the exact last pixel of the window - no matter if SDL 1.2 or 2. Anyone with a different experience?

comment:7 by elexis, 8 years ago

Summary: In-game screen blockedCamera doesn't scroll if cursor outside of window

comment:8 by Eric Ongerth, 8 years ago

I'm playing Alpha XIX (the opening screen says Build 17296 at lower left) and typically do not use Windowed mode but play in full-screen, using Alt-Tab if i need to go to other apps or desktop. (OS is Windows 10). I have found that only some edges of the game display are "active" for the purpose of allowing the mouse pointer position to move the view. Other edges give no reaction at all.

Also it seems as if the margins the game is using to determine this may be given in pixels rather than relative to screen size (percent) because on my 4K monitor it's a very narrow margin to cause the view to move. This would be no problem if moving the pointer all the way to the edge worked like it used to. However, all the way to the edge apparently does NOT activate moving the view. Instead I have to have it slightly inside the edge of the view, but only very slightly. It is too difficult of a target and I have had to revert to keyboard commands or minimap for most of my viewport moving.

This makes me wonder if the viewport is being calculated correctly (or reported correctly from some Windows API) -- at least for large monitors.

in reply to:  8 comment:9 by Lionkanzen, 8 years ago

Replying to eric o:

I'm playing Alpha XIX (the opening screen says Build 17296 at lower left) and typically do not use Windowed mode but play in full-screen, using Alt-Tab if i need to go to other apps or desktop. (OS is Windows 10). I have found that only some edges of the game display are "active" for the purpose of allowing the mouse pointer position to move the view. Other edges give no reaction at all.

Also it seems as if the margins the game is using to determine this may be given in pixels rather than relative to screen size (percent) because on my 4K monitor it's a very narrow margin to cause the view to move. This would be no problem if moving the pointer all the way to the edge worked like it used to. However, all the way to the edge apparently does NOT activate moving the view. Instead I have to have it slightly inside the edge of the view, but only very slightly. It is too difficult of a target and I have had to revert to keyboard commands or minimap for most of my viewport moving

.

This makes me wonder if the viewport is being calculated correctly (or reported correctly from some Windows API) -- at least for large monitors.

Can you take a screenshot using f2 and share here? The screenshots are saved in my documents > my games > 0ad > screenshots

comment:10 by elexis, 8 years ago

Milestone: Alpha 20Backlog

Backlogging due to lack of progress.

comment:11 by Eric, 7 years ago

I have 3 screens, (one on the bottom, that I play the game on) and two on top. (Alpha XX, on Mint 18.1) I was having a similar problem of when I tried going up, the camera view would not go up and the cursor left the game screen and up to my other monitor. When reading about this bug, I tried windowed mode, and found it was similar, but it would go up on the top edge of the windows mode (Above the map, at the very top edge of the top bar.) Interestingly, when I went back into normal mode, the game stopped letting my cursor go up past my gaming monitor screen. (Which is what I wanted, and made the game playable again.)

Just more info for troubleshooting, but thanks for such a great game.

comment:12 by Imarok, 5 years ago

Component: UI & SimulationIn-game UI

Move tickets to In-game UI as UI & Simulation got some sub components.

comment:13 by Freagarach, 3 years ago

Description: modified (diff)

#5629 for a more recent report.

Note: See TracTickets for help on using tickets.