Bing offset "bookmarks"

[malenki]

Things I miss at the saved Bing offsets:
*Possibility to make a saved offset the default offset being loaded when opening an imagery layer
*Possibility to easily edit saved offsets like renaming or changing the offset (yes, both is already possible with some workaround)
*Possibility to sort saved offsets alphabetically
*Possibility to reset offset (to 0) easily

[Upliner]

1) Having default layer offset sometimes was considered dangerous by Stöcker(he rejected at least one patch for wmsplugin that does this), so I don't think I should implement it.

2) "Offset bookmarks" tab at Imagery Preferences isn't easy? What more do you want?

[malenki]

Replying to Upliner:

1) Having default layer offset sometimes was considered dangerous by Stöcker(he rejected at least one patch for wmsplugin that does this), so I don't think I should implement it.

So when I live/map in a region where Bing has per default quite some offset every time I open the Bing-layer I have to apply a offset.
uncomfortable

With the same argument (dangerous) one could say every default offset predefined is dangerous since it could be wrong. Ergo everytime the user wants to use Bing he should set the offset manually. :)
A region where Bing isn't correct per default is around Kirklareli, Turkey: ​http://osm.org/go/x08zy499s-

2) "Offset bookmarks" tab at Imagery Preferences isn't easy? What more do you want?

Sorry, forgot about that one.
But still I'd like to be able to correct the offset of a bookmark. Yeah, I could edit the coordinates. With much practise I could guess right, I guess. :)
Deleting and creating the offset anew would be one of the mentioned workarounds.

[Upliner]

To correct bookmark you don't have to delete it, just type same name and it will be overwritten.

[A_Pirard]

Well, I think that *I* am the person who must decide, e. g. by calling it "default", if I want an offset to be automatically applied to that server of ours that exhibits a uniform 100 m offset all over its validity area.
The tricky part is when it comes to Bing or similar, because the offset is not uniform and it even depends on zoom level.
At least the zoom level should be coped with so that the offset changes when zoom changes.
One way to design that feature is to name the offset "nnnnn z=<offset>", select nnnnn and use the one with the offset nearest to setting.
Would there be a scheme to have the nearest "default x=<lat> y=<long>" apply to one place?
If the users works in some favorite places, that's great.
Clicking on a selected entry should deselect it (it is dangerous to be unable to cancel an offset).