Modify ↓
#5787 closed defect (fixed)
[patch] Display and read offset as one line
Reported by: | Zverikk | Owned by: | Upliner |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core imagery | Version: | latest |
Keywords: | Cc: |
Description
Now there's two input fields: east and north offsets. It is very unuseful for sharing. There should be one field, in any format.
For example, /(\d+[.,]\d+(?:E-?\d))[,; ]+(\d+[.,]\d+(?:E-?\d))/
Attachments (1)
Change History (6)
comment:1 by , 14 years ago
Summary: | Display and read offset as one line → Offset window usability improvements |
---|
comment:2 by , 14 years ago
Summary: | Offset window usability improvements → Display and read offset as one line |
---|
comment:3 by , 14 years ago
I've made a patch myself. It also fixes #6098.
Also it allows user to use ',' as decimal separator (automatically converted to '.') and makes it not consume arrow keys while editing the offset.
comment:4 by , 14 years ago
Summary: | Display and read offset as one line → [patch] Display and read offset as one line |
---|
by , 14 years ago
Attachment: | imagery-offset-dialog.patch added |
---|
Note:
See TracTickets
for help on using tickets.
Also, since the projection is fixed (and numbers are big enough), get rid of E-notation. Usual E0/E1 don't improve anything, just confuse people.