You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: chriscf [Submitted to the original trac issue database at 2.21pm, Wednesday, 8th December 2010]
Trying to edit way 30996668 (though happened with adjacent objects too). Grabbed a corner, and the shading changed as if the nodes were in a different order. Sanity restored when the mouse button is released. Screenshots attached.
The text was updated successfully, but these errors were encountered:
Author: Richard [Added to the original trac issue at 4.53pm, Wednesday, 8th December 2010]
Yep, known issue - to speed up redraw when dragging a node in a way, we've recently started just redrawing the 'segments' either side, having drawn the whole way without these segments at the start of drag. This hugely improves performance when editing long ways.
That said, it does (for obvious reasons) also lead to these artefacts when the way is a area with a fill style. We may revert to the original behaviour for areas, or alternatively draw the stroke and fill separately (which would mean that the fill isn't redrawn as you drag, but that performance is maintained).
Reporter: chriscf
[Submitted to the original trac issue database at 2.21pm, Wednesday, 8th December 2010]
Trying to edit way 30996668 (though happened with adjacent objects too). Grabbed a corner, and the shading changed as if the nodes were in a different order. Sanity restored when the mouse button is released. Screenshots attached.
The text was updated successfully, but these errors were encountered: