{"action":"created","issue":{"url":"https://api.github.com/repos/osmandapp/Osmand/issues/580","labels_url":"https://api.github.com/repos/osmandapp/Osmand/issues/580/labels{/name}","comments_url":"https://api.github.com/repos/osmandapp/Osmand/issues/580/comments","events_url":"https://api.github.com/repos/osmandapp/Osmand/issues/580/events","html_url":"https://github.com/osmandapp/Osmand/pull/580","id":28468865,"number":580,"title":"distanceMeasurement_5 is an updated version of distanceMeasurement_4 (re...","user":{"login":"michc","id":1393278,"avatar_url":"https://avatars.githubusercontent.com/u/1393278?v=3","gravatar_id":"","url":"https://api.github.com/users/michc","html_url":"https://github.com/michc","followers_url":"https://api.github.com/users/michc/followers","following_url":"https://api.github.com/users/michc/following{/other_user}","gists_url":"https://api.github.com/users/michc/gists{/gist_id}","starred_url":"https://api.github.com/users/michc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/michc/subscriptions","organizations_url":"https://api.github.com/users/michc/orgs","repos_url":"https://api.github.com/users/michc/repos","events_url":"https://api.github.com/users/michc/events{/privacy}","received_events_url":"https://api.github.com/users/michc/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/osmandapp/Osmand/labels/Nice%20to%20Have","name":"Nice to Have","color":"fbca04"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2014-02-28T00:31:35Z","updated_at":"2015-11-30T01:34:35Z","closed_at":"2015-11-29T23:54:55Z","pull_request":{"url":"https://api.github.com/repos/osmandapp/Osmand/pulls/580","html_url":"https://github.com/osmandapp/Osmand/pull/580","diff_url":"https://github.com/osmandapp/Osmand/pull/580.diff","patch_url":"https://github.com/osmandapp/Osmand/pull/580.patch"},"body":"   distanceMeasurement_5 is an updated version of distanceMeasurement_4 (replaces it) which enhances the DistanceCalculator plugin.\r\n    \r\n    This release is based on Osmand master dated 27Feb14.\r\n    \r\n    In addition to distanceMeasurement_4:\r\n    \r\n    1. Fix loss of text notes linked to a gpx point when it is dragged to new location.\r\n    2. Added MagnificationButtonsPlugin to provide separate screen magnification buttons, on screen display of zomm and magnification levels and separate selection menus for directly setting zoom and magnification.\r\n    This plugin can be removed by omitting the MagnificationButtonPlugin,java file and removing the line in OsmandPlugin.java/initPlugins that installs the plugin.\r\n\r\nThe following modifications to the current DistanceCalculatorPlugin are provided:\r\n\r\n1. Text size magnification.\r\n2. Point and track magnification.\r\n3. Small change to measurement origin icon to differentiate end of track (needed for subtrack and partial length display).\r\n4. Add text box magnification linked to map magnification function.\r\n5. Add planning point selection area size modification function.\r\n6. Fix bug in GPX file saving: hangs if no tracks folder has been previously created.\r\n7. Add editable notes to gpx/planning points.\r\n8. Add selectable highlighting ofgpx/planning points with notes.\r\n9. Add list, select and display function for all gpx/planning points with notes.\r\n10. Add separate screen magnification buttons that can be enabled/hidden with option to select specific magnification from long click context menu.\r\n11. When Magnification buttons are visible, change long press on map zoom buttons to provide selection menu for any desired zoom level."},"comment":{"url":"https://api.github.com/repos/osmandapp/Osmand/issues/comments/160493744","html_url":"https://github.com/osmandapp/Osmand/pull/580#issuecomment-160493744","issue_url":"https://api.github.com/repos/osmandapp/Osmand/issues/580","id":160493744,"user":{"login":"michc","id":1393278,"avatar_url":"https://avatars.githubusercontent.com/u/1393278?v=3","gravatar_id":"","url":"https://api.github.com/users/michc","html_url":"https://github.com/michc","followers_url":"https://api.github.com/users/michc/followers","following_url":"https://api.github.com/users/michc/following{/other_user}","gists_url":"https://api.github.com/users/michc/gists{/gist_id}","starred_url":"https://api.github.com/users/michc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/michc/subscriptions","organizations_url":"https://api.github.com/users/michc/orgs","repos_url":"https://api.github.com/users/michc/repos","events_url":"https://api.github.com/users/michc/events{/privacy}","received_events_url":"https://api.github.com/users/michc/received_events","type":"User","site_admin":false},"created_at":"2015-11-30T01:34:35Z","updated_at":"2015-11-30T01:34:35Z","body":"The note functionality is currently useless. You can not enter any data,\ninstead some useless parameter is shown (speed? + ?) that can not be\nedited. I think it was abandoned in the middle of implementation. Also the\ndelete last point added does not work.\n\nThere are many different uses for a GPX editor but my original interest was\nthe planning aspect (hence Planning and Measurement). The \"plans\" I refer\nto are manually created tracks that do not necessarily have simple\nmathematical logic in determining the path taken. The path is created based\non the desire to travel to specific locations of interest and/or using\nspecific streets, etc. The sort of thing you do when sight seeing on foot\nin a town. Shortest distance and speed have no bearing on the path\nselected. Way points could be used but become clumsy when trying to choose\na path down alleyways, markets and streets of interest. An editor that can\nmove, add and delete points is essentiial.\n\nI looked at the possibility of making the application fully extensible by\nexternally provided plugins but came to the conclusion that defining an API\nwas too difficult, mainly because the structure of the application was not\nstable and was changing substantially in every release. Until/unless the\nframework is stable it will be difficult to write plugins. The design must\nbe based on the concept that external components can interact with the\ncritical elements.\n\nDrag and drop is simple and I have used it in my version without any\nproblems for 4 years. The biggest problem is related to screen size and\npoint selection radius. A large finger on a small screen can select several\npoints but making the selection area user changeable addresses this problem.\n\nAs I have other functionality in my branch I only merge (locally) with the\nmain branch every 6 - 12 months. I can provide a pull request to release\nV2.1 but the changes even since then have continued very rapidly. I can\npost screen shot on the User forum and can provide a fully functional apk\n(including other functionality) to an upload server or dropbox.\n\nOn Mon, Nov 30, 2015 at 11:45 AM, vshcherb <notifications@github.com> wrote:\n\n> We still plan to change how we edit the track and even more to put that\n> separate action the drawer. We hope it will be done in 2.3, but it is not\n> clear. Mainly the changes will be related to context menu and not to\n> drag/drop functionality. Addition of notes and points information, I'm not\n> sure we dropped, I've thought we finally enabled it. Anyway the measurement\n> plugin as itself, will be left and instead we will be working on fully GPX\n> editor.\n>\n> I think it will be interested for us if you share some screenshots and\n> open new pull-request, though I can't promise that we merge it 1 to 1. I\n> think it is very valuable and other people could build OsmAnd with your\n> extension (unfortunately proper extension mechanism is not developed in\n> OsmAnd via external dex-classes).\n>\n> Thanks!\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/osmandapp/Osmand/pull/580#issuecomment-160487739>.\n>\n"}}