View Issue Details

IDProjectCategoryView StatusLast Update
0003497Dwarf FortressTechnical -- Input/Keybinding/Macrospublic2015-07-28 20:00
ReporterTrouserman Assigned ToToady One  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Fixed in Version0.40.01 
Summary0003497: incorrect string entry keybindings
Descriptioninterface.txt (0.31.16 distribution for OSX, likely others) contains the lines:

[BIND:STRING_A123:REPEAT_SLOW]
[KEY:}]
[BIND:STRING_A124:REPEAT_SLOW]
[KEY:?]

where it should read:

[BIND:STRING_A123:REPEAT_SLOW]
[KEY:{]
[BIND:STRING_A124:REPEAT_SLOW]
[KEY:|]

Resulting behavior is that typing a left brace or vertical bar in a text entry field produces nothing. Typing a question mark brings up help, and inserts a vertical bar. Disregarding the rather confusing (I would say erroneous) behavior that a single keystroke is interpreted to invoke two separate actions, it should insert a question mark, but the STRING_A124 binding apparently overrides the STRING_A063 binding. After the suggested changes, left brace and vertical bar keys insert the appropriate characters into the text field, while question mark brings up help and inserts a question mark.
Steps To ReproduceUse the affected characters { | ? in a text field, such as setting a custom nickname on the embark screen.
TagsNo tags attached.

Relationships

related to 0006558 resolvedToady One "Broken Unicode" warnings for some keybindings 
related to 0009031 resolvedToady One STRING_A123 and STRING_A125 are bound to the same key 

Activities

Trouserman

2014-07-08 06:49

reporter   ~0025015

As of 0.40.01 release, upper 128 characters have been rebound. Many have, like 124, been bound to the question mark key. Typing a question mark in a text entry still brings up help, but inserts character 159 (small script f) instead of a vertical bar. None of these should be bound to question mark.

lethosor

2015-07-28 19:54

manager   ~0032943

Last edited: 2015-07-28 19:59

The original issue here was fixed in 0.40.01 (assuming I understood your comment above), and the second was fixed in 0006558.
I opened a separate issue for the incorrect STRING_A123 keybinding.

Issue History

Date Modified Username Field Change
2010-11-02 01:48 Trouserman New Issue
2014-07-08 06:49 Trouserman Note Added: 0025015
2015-07-28 19:52 lethosor Relationship added related to 0006558
2015-07-28 19:54 lethosor Note Added: 0032943
2015-07-28 19:54 lethosor Status new => resolved
2015-07-28 19:54 lethosor Fixed in Version => 0.40.01
2015-07-28 19:54 lethosor Resolution open => fixed
2015-07-28 19:54 lethosor Assigned To => Toady One
2015-07-28 19:59 lethosor Note Edited: 0032943
2015-07-28 20:00 lethosor Relationship added related to 0009031