Bay 12 Games Forum

Please login or register.

Login with username, password and session length
Advanced search  

Author Topic: Be able to change the cursor jump distance [interface]  (Read 461 times)

Silverionmox

  • Bay Watcher
    • View Profile
Be able to change the cursor jump distance [interface]
« on: May 26, 2012, 08:48:16 am »

Currently the cursor jumps 11 places when you press shift+arrow. Depending on what you want to design, customizing the distance ad hoc could be very helpful. Changing it in the game would be most practical (since it's nothing more than inputting a number), but making it changeable in the init would do.
Logged
Dwarf Fortress cured my savescumming.

NW_Kohaku

  • Bay Watcher
  • [ETHIC:SCIENCE_FOR_FUN: REQUIRED]
    • View Profile
Re: Be able to change the cursor jump distance [interface]
« Reply #1 on: May 26, 2012, 09:29:05 am »

Actually, 10.  You mark 11 spaces if you enter, shit-direction, enter because you get the tile you started on (tile 0, as it were) as well as the ten spaces you move.  Shift-move twice, and you get 21 tiles.
Logged
Personally, I like [DF] because after climbing the damned learning cliff, I'm too elitist to consider not liking it.
"And no Frankenstein-esque body part stitching?"
"Not yet"

Improved Farming
Class Warfare

Exponent

  • Bay Watcher
    • View Profile
Re: Be able to change the cursor jump distance [interface]
« Reply #2 on: May 26, 2012, 09:31:36 am »

Seconded.  I actually went so far as to debug the executable and discover which bits of code were adding 10 to the cursor and/or viewport and mod them to add 12 instead.

I've seen it mentioned before, but I'd also add to this suggestion the ability to have another modifier similar to the shift modifier that decreases the amount of viewport scroll.  So when the cursor is not visible, normal arrows move the screen by N (specified in an init, perhaps).  With Shift, it moves by M (which defaults in the init to N*2).  And with, say, Ctrl, it moves by L (which might default to 1, for precise placement of the viewport in preparation for using function key hotkey selection).  As it is, I often memory hack just to get my hotkeys set up exactly the way I want them.
Logged