Bug report #4717
Rotation affects offset direction
Status: | Closed | ||
---|---|---|---|
Priority: | Low | ||
Assignee: | - | ||
Category: | Symbology | ||
Affected QGIS version: | master | Regression?: | No |
Operating System: | Easy fix?: | No | |
Pull Request or Patch supplied: | Yes | Resolution: | wontfix |
Crashes QGIS or corrupts data: | No | Copied to github as #: | 14598 |
Description
When a rotation is applied to a symbol, the offset is no longer orthogonal, but along rotated axes. Keeping it orthogonal seems a more sound choice to me.
History
#1
Updated by JD - about 13 years ago
- File 4717_master.diff
added
Fixed by removing _rotatedOffset() function which was applying the rotation value to the symbol's centre point. Patch attached.
Also fixed default arrow symbol which wasn't symmetrical.
#2
Updated by Giovanni Manghi about 13 years ago
- Pull Request or Patch supplied changed from No to Yes
#3
Updated by Marco Hugentobler about 13 years ago
- Assignee set to Martin Dobias
#4
Updated by Martin Dobias about 13 years ago
Please describe me your use case. For me the current handling seems correct: imagine that you have a symbol composed of several layers, some of them having an offset. When I start rotating the whole symbol, the offset direction must be rotated too - otherwise the symbol appearance would break. Or do you mean something else?
#5
Updated by Paolo Cavallini about 13 years ago
Quite convincing. However, in case of a single symbol, probably an user will want to use rotation and offset independently.
#6
Updated by Paolo Cavallini over 12 years ago
- Target version set to Version 2.0.0
#7
Updated by Martin Dobias almost 11 years ago
- Assignee deleted (
Martin Dobias) - Target version changed from Version 2.0.0 to Future Release - Nice to have
#8
Updated by Giovanni Manghi almost 8 years ago
- Regression? set to No
- Easy fix? set to No
#9
Updated by Paolo Cavallini almost 7 years ago
- Resolution set to wontfix
- Status changed from Open to Closed
- Priority changed from Normal to Low
Well, it's an edge case. Since nobody seems interested, we can assume the current behaviour is acceptable to users.