Opened 16 years ago
Closed 16 years ago
#608 closed enhancement (wontfix)
Move threshold should be made configurable
| Reported by: | Owned by: | framm | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | Cc: | schuetzm@… |
Description
The move threshold introduced in changeset 526 should be made configurable.
As it is now, it is very cumbersome to move an object only a slight amount (which for me is probably the majority of cases).
Attachments (0)
Change History (4)
comment:1 by , 16 years ago
follow-up: 3 comment:2 by , 16 years ago
| Priority: | critical → minor |
|---|---|
| Type: | defect → enhancement |
It is adjustable with edit.initial-move-threshold=x where x is a value in pixels. Default is 15.
Are you saying that this adjustment should be added to the GUI?
comment:3 by , 16 years ago
Replying to Daveemtb:
It is adjustable with edit.initial-move-threshold=x where x is a value in pixels. Default is 15.
Are you saying that this adjustment should be added to the GUI?
Yes. I would even suggest to switch it off by default.
The reason I set the priority to critical was that I didn't see any way to change the threshold (except by looking at the source code; now it is at least documented in the wiki) and it was almost unusable for making small changes. If you want to move a node by only 1 or 2 pixels, you first have to move it by 15 pixels and then back, but then you have no idea where your node originally was...
(Sorry it took so long to respond; seems I didn't get a mail notification from Trac).
comment:4 by , 16 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
would have to agree with this, though perhaps "critical" is a slight exageration!