Release 2.6.0 #616
Merged
Release 2.6.0 #616
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Swedish translation: Correction of some misspellings * Swedish translation: Some more translations of english words into swedish (and *if* the word "Polylinje" exists at all in swedish then it should be spelled including a "j") * Swedish translation: Translated "marker" ==> "markör" (similar to the existing translation of "circle marker" ==> "cirkelmarkör") * Swedish translation: Replaced the word "Polylinje" with "Linje". It is questionable whether the word "Polylinje" exists at all but it is at least not a word that the average swedish end-user would be familiar with. No search result for the word "polylinje": https://svenska.se/tre/?sok=polylinje&pz=1 https://tyda.se/search/polylinje?lang%5B0%5D=en&lang%5B1%5D=sv
When the last button has more then 1 action, the corners displayed are wrong, because of the default leaflet.css. https://ibb.co/py4Pwv7
… (patch) Bug: If drag mode is enabled bevor edit mode was enabled, marker is not snapping to layers. https://jsfiddle.net/falkedesign/2jv64bh9/
* Update README.md typo globaldrawmodetoggled --> globaldragmodetoggled * Add snapping on circle border and L.PM.Utils to global
Co-authored-by: Alexey <a-lashkin@ya.ru>
* Update README.md typo globaldrawmodetoggled --> globaldragmodetoggled * Add output of the events to the Readme and created a demo event site. * Added "pm:enable" because "pm:disable" already exists * Removed "pm:raiseMarkers", is a old relict #79 * Update all availableEvents in LayerGroup * Fix inconsistent use of "pm:remove" on a layer * CircleMarker removed "contextmenu" listener * Disable programmatically enabled layers when removal mode is activated * Add event for language change * Added event "pm:globaldrawmodetoggled". With that new functions are added: getActiveShape(), globalDrawModeEnabled() * Add enable / disable functions of removal and drag mode to the Readme * Add CircleMarker shape to Readme * Added shape and workingLayer for snap event, to match the other events. Added shape names to the Edit Classes * Added consistent use of passed values while events * Fire "pm:markerdragend" if "pm:intersect" is also fired * Change event name "pm:langchanged" to "pm:langchange" * Add Developing steps * Added globalcutmode and event tests * Changed pm:centerplaced test * Changed pm:centerplaced test * Removed eslint errors
* Update README.md typo globaldrawmodetoggled --> globaldragmodetoggled * Add new option "allowSelfIntersectionEdit" -> Allow to change vertices they are connected to a intersecting line. Fixed Bug with cachedColor if layer is self-intersecting while enable edit mode Hurray first entry in Edit.Polygon 🎉 * Add tests * Remove .only in test
…) (patch) * Handle intersection on first marker at polygon Now the polygon can't be finished if clicking on the first marker when it intersects. The problem is, that the _finishShape is called from the first placed marker onclick event. So it never called _createVertex and it was never checked if the new latlng was intersected. If the parameter is true then the new vertex will added to the layer and checked if it intersects. * Added test
* Update README.md typo globaldrawmodetoggled --> globaldragmodetoggled * Fix Bug in Cut Mode. Prevent that a unnecessary layergroup is created * Add test and remove layergroup in Line.disable
* Update README.md typo globaldrawmodetoggled --> globaldragmodetoggled * Adding drag event to marker and circle while edit mode * Check if marker has dragging property * CircleMarker "pm:edit" was fired twice. 1. Dragging.js -> _dragMixinOnMouseUp -> _fireEdit 2. _dragMixinOnMouseUp -> "pm:dragend" -> _onMarkerDragEnd -> _fireEdit * Removed Pro event listener that causes that 'dragend' not fired
…ircle border (#603) (minor)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.