0000322: Map scroll with keyboard keys behaves a bit differently then H3, leading to the impression that it's too fast sometimes

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000322

VCMI

GUI - Adventure Map

public

2009-12-25 03:33

2012-09-01 10:02

Reporter

Zamolxis

Assigned To

Priority

low

Severity

trivial

Reproducibility

always

Status

new

Resolution

open

Platform

OS Version

Product Version

0.75

Target Version

Fixed in Version

Summary

0000322: Map scroll with keyboard keys behaves a bit differently then H3, leading to the impression that it's too fast sometimes

Description

In H3, if we pressed CTRL and then an Arrow/Numpad key for a second, the map would scroll 1 tile. If we held the CTRL+Arrow/Numpad key for more than a second, only then the map would start continuously scrolling (so after a break of a fraction of a second, as if the system would check to see if we want just a short scroll or a long one).

In VCMI however, the continuous scrolling starts instantly. Which means that if we want to scroll just 1 tile, we'll have to hold CTRL, but then barely touch an Arrow/Numpad key. And even then sometimes I see the map jumps 2-3 tiles already. It's particularly noticed in lower resolutions, where fast scroll may suddenly move 30% of your visible AdvMap out of view (on high resolutions the impact is way smaller, hence the reason I didn't notice this yet).

Tags

No tags attached.

Attached Files

Relationships

Notes
(0002916) randomed (reporter) 2012-08-19 09:41	I think that the present implementation is perfect.

(0002973) Zamolxis (viewer) 2012-09-01 10:02 edited on: 2012-09-01 10:18	I think for the player it doesn't make much difference, which is why I created it from the start as Low priority. It's just a bit annoying as a tester, if I want to capture the best focus for a screenshot. I prolly wouldn't have reported this at all if it wasn't also different than the H3 behavior, and it's no big issue if it's never fixed. But there's also no harm in leaving it open, in case one day a coder will feel like trying his hand at this.

Issue History
Date Modified	Username	Field	Change
2009-12-25 03:33	Zamolxis	New Issue
2012-08-19 09:41	randomed	Note Added: 0002916
2012-09-01 10:02	Zamolxis	Note Added: 0002973
2012-09-01 10:18	Zamolxis	Note Edited: 0002973	View Revisions
2012-09-01 10:18	Zamolxis	Note Edited: 0002973	View Revisions

Site | Forums | Wiki | Slack | GitHub